Repository navigation
feat: rolling releases on every merge to main - #7
Merged
Merged
Conversation
Versions come from git tags via hatch-vcs. The release workflow runs CI, computes the next version from Conventional Commit subjects, publishes to PyPI with trusted publishing, then tags and creates a GitHub release. CI no longer runs separately on pushes to main.
shrijayan
force-pushed
the
feat/rolling-releases
branch
from
October 22, 2026 09:34
550b1e2 to
cde99da
Compare
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.
Every merge to
mainthat changessrc/,spec/orpyproject.tomlnow:vX.Y.Ztag (scripts/next_version.py),pypi),The version is no longer hard-coded:
hatch-vcsderives it from tags, andopencode.__version__reads the installed metadata.Merging this PR triggers the first release, 0.1.0. Before merging, register the PyPI pending publisher (project
opencode-python-sdk, workflowrelease.yml, environmentpypi). If it isn't registered, the publish job fails and nothing is tagged.