ci: add CI + tag-driven release pipeline#1
Merged
Conversation
The engine had no automation: changes reached PyPI validated only on a maintainer's laptop. Adds: - .github/workflows/ci.yml — pytest on every push to main + PR. The connect-retry suite is fully mocked, so no Chrome is required. - .github/workflows/release.yml — identical to mithwire-mcp's: release-please maintains a release PR, and on merge the same run builds and publishes to TestPyPI then PyPI (non-prerelease, gated). workflow_dispatch does a TestPyPI-only .devNNNN dry run. - release-please config/manifest tracking 0.50.3 (bump-minor-pre-major) and a CHANGELOG seed. Co-authored-by: Cursor <cursoragent@cursor.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.
Summary
.github/workflows/ci.ymlrunspyteston every push to main + PR. The connect-retry suite is fully mocked, so no Chrome is required..github/workflows/release.yml: identical pipeline to mithwire-mcp — release-please maintains a release PR; on merge the same run builds and publishes to TestPyPI then PyPI (non-prerelease, gated by thepypienvironment).workflow_dispatchdoes a TestPyPI-only.devNNNNdry run.release-please-config.json/.release-please-manifest.jsontrack0.50.3withbump-minor-pre-major;CHANGELOG.mdseed.Notes
testpypienvironment already configured (workflowrelease.yml, envtestpypi).v0.50.3, release-please will NOT open a release PR until afeat/fixlands — expected.Test plan
releaseworkflow via workflow_dispatch → confirm0.50.3.devNNNNon TestPyPI.Made with Cursor