feat: automated GitHub Actions release workflow for PyPI publishing#314
Merged
Conversation
dtehan-td
added a commit
to dtehan-td/teradata-mcp-server
that referenced
this pull request
Jun 8, 2026
…eradata#314) * updating the version number * Automating push to pypi
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.
Summary
.github/workflows/release.yml— a GitHub Actions workflow that automates the full release pipeline: build, GitHub Release creation, TestPyPI publish + smoke test, approval gate, and production PyPI publishdocs/developer_guide/DEVELOPER_GUIDE.mdto document the automated workflow, one-time GitHub setup (secrets, environments), VPN requirement, and the approval processRelease pipeline
Triggered by pushing a version tag (
v*.*.*) or manually via the Actions UI "Run workflow" button. Releases are not created on every commit — the tag push is the explicit release trigger.One-time setup required
Before this workflow can run, a repo admin needs to:
TEST_PYPI_TOKENandPYPI_TOKENsecrets under Settings → Secrets and variables → Actionstest-pypiandpypienvironments under Settings → Environments, with Required reviewers configured onpypiSee the updated Developer Guide for full setup instructions.
Test plan
release.ymlsyntax is valid (GitHub Actions workflow linter)TEST_PYPI_TOKENandPYPI_TOKENsecrets to repo settingstest-pypiandpypienvironments with required reviewer onpypiv0.2.3) and verify the workflow runs end-to-end