Skip to content

Fix release script skipping version bump for lockfile-only changes#3969

Open
Christian-Sidak wants to merge 1 commit intomodelcontextprotocol:mainfrom
Christian-Sidak:fix/release-lockfile-changes
Open

Fix release script skipping version bump for lockfile-only changes#3969
Christian-Sidak wants to merge 1 commit intomodelcontextprotocol:mainfrom
Christian-Sidak:fix/release-lockfile-changes

Conversation

@Christian-Sidak
Copy link
Copy Markdown

Summary

  • has_changes() in scripts/release.py only considered .py and .ts files when deciding whether a package needs a version bump. Packages with only lockfile changes (e.g. uv.lock from dependabot) were silently skipped, leaving stale versions in pyproject.toml.
  • Removed the file-suffix filter so any changed file in a package directory triggers the CalVer version bump.
  • Added scripts/test_release.py with unit tests for has_changes(), including a regression test for the lockfile-only scenario.

Closes #3870

Test plan

  • python scripts/test_release.py passes (4 tests: no changes, .py change, lockfile-only change, .toml change)
  • Verify next release correctly bumps packages that only have lockfile diffs

has_changes() filtered changed files to only .py and .ts suffixes,
so packages with only lockfile updates (e.g. uv.lock from dependabot)
were never version-bumped. Remove the suffix filter so any file change
in a package directory triggers the CalVer bump.

Closes modelcontextprotocol#3870

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.

Release script skips version bump for packages with only lockfile changes

1 participant