Skip to content

chore: bump version to v1.2.0#33

Merged
trsdn merged 2 commits into
mainfrom
version-bump/v1.2.0
Dec 8, 2025
Merged

chore: bump version to v1.2.0#33
trsdn merged 2 commits into
mainfrom
version-bump/v1.2.0

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Sep 17, 2025

🚀 Automated Version Bump: v1.2.0

This PR automatically bumps the version based on conventional commits since the last release.

📊 Release Summary

  • Version Type: minor
  • New Version: v1.2.0
  • Commits Included: 96
  • Generated: 2025-11-24 09:29:57 UTC

📝 Changelog Preview

✨ Features

  • add comprehensive test coverage with 24 new test cases
  • add working CI-CD maintenance workflow with simpler logic
  • add ultra-simple CI/CD maintenance workflow
  • add simplified CI/CD maintenance workflow v2
  • implement comprehensive PR feedback and issue reporting system
  • ... and 2 more features

🐛 Bug Fixes

  • revert workflows from path-based to branch-based filtering
  • resolve YAML syntax error in pr-feedback.yml multiline Python script
  • add proper GitHub Actions expression syntax for hashFiles function
  • correct hashFiles syntax in docs.yml workflow conditional
  • resolve flake8 E501 line too long in server.py
  • ... and 17 more fixes

🎯 What Happens Next

  1. Review: Maintainers review this automated version bump
  2. Merge: When merged, a git tag v1.2.0 will be created
  3. Release: The tag will trigger the automated release workflow
  4. Publish: Package will be published to PyPI automatically

✅ Pre-Release Checklist

  • Version number looks correct
  • Changelog entries are accurate
  • No breaking changes in patch/minor releases
  • All CI checks pass

This PR was created automatically by the version bump workflow. The release will be fully automated upon merge.

@github-actions github-actions Bot requested a review from trsdn as a code owner September 17, 2025 22:41
@github-actions github-actions Bot added release Release-related pull requests and issues automated Automatically generated content labels Sep 17, 2025
@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Sep 17, 2025

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@trsdn trsdn requested a review from Copilot September 18, 2025 08:36
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR bumps the project version from v1.1.0 to v1.2.0 as part of an automated release process based on conventional commits. The changes include version updates and configuration formatting improvements.

  • Updates project version to v1.2.0 in pyproject.toml
  • Reformats pyproject.toml configuration arrays to use multi-line format for better readability
  • Adds placeholder changelog entries and test workflow comments

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
pyproject.toml Updates version to 1.2.0 and reformats configuration arrays to multi-line format
README.md Adds test workflow comment
CHANGELOG.md Adds placeholder changelog entry with date placeholder

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Comment thread CHANGELOG.md
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]
## [] - $(date +%Y-%m-%d)
Copy link

Copilot AI Sep 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changelog entry has an empty version number in brackets and uses a shell command $(date +%Y-%m-%d) that won't be executed in markdown. This should be replaced with the actual version number '1.2.0' and a proper date format.

Suggested change
## [] - $(date +%Y-%m-%d)
## [1.2.0] - 2024-06-10

Copilot uses AI. Check for mistakes.
@github-actions github-actions Bot force-pushed the version-bump/v1.2.0 branch 2 times, most recently from 6714e6a to 18f6fb0 Compare September 29, 2025 09:26
@github-actions github-actions Bot force-pushed the version-bump/v1.2.0 branch from 18f6fb0 to d9437a3 Compare October 6, 2025 09:27
@github-actions github-actions Bot force-pushed the version-bump/v1.2.0 branch 2 times, most recently from 6ad6dc9 to cca8396 Compare October 20, 2025 09:27
@github-actions github-actions Bot force-pushed the version-bump/v1.2.0 branch from cca8396 to 3ec866e Compare October 27, 2025 09:28
@github-actions github-actions Bot force-pushed the version-bump/v1.2.0 branch 2 times, most recently from fb36a73 to a0c6d00 Compare November 10, 2025 09:28
@github-actions github-actions Bot force-pushed the version-bump/v1.2.0 branch from a0c6d00 to f1abb9d Compare November 17, 2025 09:29
This minor version bump includes:
- 96 commits since last release
- Automated changelog generation
- Version update in pyproject.toml

Release will be triggered automatically when this PR is merged.
@github-actions github-actions Bot force-pushed the version-bump/v1.2.0 branch from f1abb9d to 27b1509 Compare November 24, 2025 09:29
@trsdn trsdn merged commit bea8a16 into main Dec 8, 2025
@trsdn trsdn deleted the version-bump/v1.2.0 branch December 8, 2025 11:50
@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Dec 8, 2025

🔍 PR Analysis Results

PR: #33 | Commit: f94a7bd33bf0ef44f320887b0161be232d0ef3de

🎨 Code Formatting

All files properly formatted

🔧 Code Linting

No linting issues found

📝 Type Checking

Type checking issues found

Click to see type issues
usage: mypy [-h] [-v] [-V] [more options; see below]
            [-m MODULE] [-p PACKAGE] [-c PROGRAM_TEXT] [files ...]
mypy: error: unrecognized arguments: --json-report mypy_report.json

Fix: Add proper type annotations and resolve type errors

🔒 Security Analysis

No security issues detected

📊 Test Coverage Analysis

Coverage 80.48289738430583% meets 80% requirement

🧹 Dead Code Analysis

Dead code analysis completed

📋 Summary

⚠️ Found 1 issue(s) that should be addressed:

  • 📝 Types: Issues found

🔧 Quick Fix Commands:

# Fix formatting and auto-fixable linting issues
ruff format .
ruff check . --fix

# Run tests with coverage
pytest tests/unit/ --cov=markitdown_mcp --cov-report=term-missing

# Check security
bandit -r markitdown_mcp/

This analysis was automatically generated by the PR feedback workflow.
Report generated at 2025-12-08 11:51:08 UTC

@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Dec 8, 2025

🔍 PR Quality Summary

CI Status

⚪ Security: pending
⏭️ Docs: skipped
⚪ Quality: pending
⚪ Tests: pending

Metrics

Metric Value Trend
📊 Coverage N/A -
🧪 Tests Test results pending -
⏱️ Performance No performance data -

Quality Checks

  • Format & Lint: Ruff formatting and linting
  • Type Safety: MyPy strict type checking
  • Security: Bandit, Safety, GitLeaks scanning
  • MCP Protocol: Tool schema validation
  • Documentation: Docstring coverage (80%+)

MCP Tools

  • convert_file - Convert individual files to Markdown
  • convert_directory - Batch convert directories
  • list_supported_formats - Query supported file types

🤖 Auto-generated by CI • Last updated: 2025-12-08 11:52 UTC

@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Dec 8, 2025

🔍 CI Quality Gates Summary

Overall Status: ✅ All Passed

Check Status Details Action Required
🎨 Format ✅ Passed ruff format check None
🔧 Lint ✅ Passed ruff linting None
📝 Types ✅ Passed mypy type checking None
🧪 Tests ✅ Passed Unit tests None
📊 Coverage 80.5% Minimum: 80% None
🔌 MCP ✅ Valid Protocol compliance None
🔒 Security ✅ Clean Dependency audit None

🔗 Quick Links

🛠️ Quick Fix Commands

# Fix most issues automatically
ruff format .
ruff check . --fix

# Run tests locally
pytest tests/unit/ --cov=markitdown_mcp

# Check types
mypy markitdown_mcp

Last updated: 2025-12-08 11:53:09 UTC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automatically generated content release Release-related pull requests and issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants