Skip to content

chore: sync version to 2.0.0 - #56

Merged
trsdn merged 1 commit into
mainfrom
chore/sync-version-2.0.0
Aug 25, 2026
Merged

trsdn merged 1 commit into
mainfrom
chore/sync-version-2.0.0

Conversation

@trsdn

@trsdn trsdn commented Aug 25, 2026

Copy link
Copy Markdown
Owner

pyproject.toml stand auf 1.2.2, waehrend auf PyPI und als Git-Tag bereits 2.0.0 veroeffentlicht ist. Der Bump beim 2.0.0-Release wurde nie auf main nachgezogen.

Folge: Der version-bump-Workflow rechnete von der falschen Basis und schlug 1.2.3 vor (PR #55, geschlossen) - eine Rueckwaertsversion unterhalb der publizierten 2.0.0. Ein Release daraus waere fehlgeschlagen oder haette eine aeltere Version als latest gesetzt.

Setzt die Version auf den tatsaechlich veroeffentlichten Stand 2.0.0. Kein Release, kein Tag - reine Synchronisierung.

@github-actions

Copy link
Copy Markdown
Contributor

Dependency Review

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

Scanned Files

None

@github-actions

Copy link
Copy Markdown
Contributor

🔍 PR Analysis Results

PR: #56 | Commit: cff089920584b546893f099dfff49a2f3dd73863

🎨 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 81.81818181818181% 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 2026-08-25 05:55:55 UTC

@github-actions

Copy link
Copy Markdown
Contributor

🔍 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 81.8% 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: 2026-08-25 05:56:40 UTC

@github-actions

Copy link
Copy Markdown
Contributor

🔍 PR Quality Summary

CI Status

✅ Security: success
✅ Docs: success
✅ Tests: success
✅ Quality: success

Metrics

Metric Value Trend
📊 Coverage N/A -
🧪 Tests Test results unavailable -
⏱️ 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: 2026-08-25 05:57 UTC

@trsdn
trsdn merged commit d8083dd into main Aug 25, 2026
61 checks passed
@trsdn
trsdn deleted the chore/sync-version-2.0.0 branch August 25, 2026 05:58
@trsdn trsdn mentioned this pull request Aug 30, 2026
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant