Fixing the version artifact upload from release.yml - #233
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the GitHub Actions release workflow to persist the resolved release version as a build artifact, enabling downstream workflows (e.g., docker.yml) triggered via workflow_run to retrieve the version consistently from the PyPI Release run.
Changes:
- Writes the resolved version string to
version.txtin.github/workflows/release.yml. - Uploads
version.txtas therelease-versionartifact from thePyPI Releaseworkflow run.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
AayushTyagi1
approved these changes
Aug 13, 2026
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
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.
Related Issue
Resolves:
https://jira.issues.couchbase.com/browse/CBD-6781
https://jira.issues.couchbase.com/browse/DA-1987
What does this change do?
This is to ensure that the version artifacts are uploaded in the release.yml actions as well
Why is this change needed?
This is to ensure that the docker.yml is able to obtain the versions artifacts from release.yml actions
Evidence of Testing
Automated tests — commands run and results summary:
Environments tested (both are required):
Manual verification — MCP client used (Claude Desktop, Cursor, MCP Inspector, ...) and what was exercised. Screenshots or tool-call transcripts are very helpful:
Compatibility Considerations
Checklist
cb_mcp.corecontracts / managed MCP interfaces (or discussed first)