chore(release): bump runtime 0.4.1 + contract 0.7.3 (release-prep) - #51
Merged
Conversation
Prepares the first release under the new adapter names. Dependabot refreshed the runtime and contract dependency pins since v0.4.0 without a version bump; the changed-vs-bumped guard flags them, so this acknowledges those changes and lets a v* tag pass. Syncs the continuo-engine-contract pin (root + both adapters), image-requirements-<engine>.txt, template/requirements.lock, uv.lock, and the versioned image-tag examples in README.md / template/Dockerfile. Adapters stay at 0.2.0 (first publish under the new names). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Simone Carolini <simonecarolini.sc@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Release-prep version bumps so the first
v*tag under the new adapter names passes the changed-vs-bumped guard (checklist step 1 from #50).continuo-python-runtime0.4.0 → 0.4.1continuo-engine-contract0.7.2 → 0.7.3Dependabot refreshed both packages' dependency pins since
v0.4.0without a version bump;scripts/check_version_bumps.pycorrectly flags that, so this acknowledges the changes. Adapters stay at 0.2.0 (first publish under the newcontinuo-<engine>-adapternames — the guard is name-aware and doesn't require a bump for a renamed dist).Synced everywhere the versions must reach:
continuo-engine-contract==0.7.3pin in rootpyproject.toml+ both adaptersimage-requirements-postgres.txt/image-requirements-trino.txt(runtime → 0.4.1)template/requirements.lock(placeholder pin → 0.4.1)uv.lock(regenerated)README.mdandtemplate/Dockerfile(:v0.4.0→:v0.4.1)Verified
scripts/check_version_bumps.py→ exit 0 ("All packages changed since v0.4.0 were version-bumped").tests/test_image_requirements_sync.py(drift guard) andtests/test_template.py(version-tag guard) pass.Next after merge: register the two adapter trusted publishers, then cut
v0.4.1-test1→ realv0.4.1.🤖 Generated with Claude Code