feat(release): add two-tier staging/production release system #53
Conversation
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
Implement automatic staging releases and manual production releases: - Staging: Automatic on push to main (TestPyPI, npm @next, staging-* Docker) - Production: Manual workflow dispatch (PyPI, npm @latest, vX.Y.Z + latest Docker) Changes: - Add push trigger with path filters for automatic staging - Replace release_channel with release_environment input - Split PyPI publishing: TestPyPI (staging) vs PyPI (production) - Split npm publishing: @next tag (staging) vs @latest (production) - Conditional Docker tagging: staging-X.Y.Z vs vX.Y.Z + latest - Add install-staging.sh for testing prerelease binaries - Update RELEASE.md with two-tier documentation 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
…staging flag Instead of separate install.sh and install-staging.sh scripts: - Single install.sh handles both production and staging - Use --staging flag or STAGING=1 env var for prerelease installs - Eliminates code drift between scripts Usage: Production: curl -fsSL .../install.sh | bash Staging: curl -fsSL .../install.sh | bash -s -- --staging 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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
Implements automatic staging releases and manual production releases as per the staging release strategy plan.
Changes
mainthat touchescontrol-plane/,sdk/,VERSION, or the release workflow triggers a staging releaseproductionenvironment@next, Dockerstaging-X.Y.Z-rc.N@latest, DockervX.Y.Z+latestinstall-staging.sh- Installs to~/.agentfield-staging/binwithaf-stagingsymlinkVersion Flow
Prerequisites
TEST_PYPI_API_TOKENsecret to GitHub repository settingsTest plan
v0.1.19-rc.1@nexttag:npm view @agentfield/sdk@nextghcr.io/agent-field/agentfield-control-plane:staging-0.1.19-rc.1curl -fsSL https://raw.githubusercontent.com/Agent-Field/agentfield/main/scripts/install-staging.sh | bash🤖 Generated with Claude Code