Skip to content

Conversation

@ndeepak-baseten
Copy link
Contributor

@ndeepak-baseten ndeepak-baseten commented Oct 21, 2025

🚀 What

Add a workflow to trigger an RC release from GHA. This packages code already pushed into the branch in the distribution, ensuring package security and integrity. Also allows traceability.

Inputs:

  • branch name
  • desired rc version (looked up from pyproject.toml and uv.lock)

Other features:

  • Can be run by a set of allowlisted users.
  • Validates version for x.y.zrcN schema.
  • Validates expected rc is consistent in uv.lock and pyproject.toml
  • Allows one run at a time

💻 How

Add new GHA workflow. Mostly follows our post-commit workflow, but leaves out the git tag and release steps.

🔬 Testing

Individual steps work. Validated regex separately. Can test wofkflow after merge.

@ndeepak-baseten ndeepak-baseten changed the title Initial commit for rc release CI Create truss RC packages through GHA Oct 21, 2025
- name: Check user permissions
run: |
# Only allow specific users to trigger (from secret)
ALLOWED_USERS="${{ secrets.RC_RELEASE_ALLOWED_USERS }}"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mainly for security reasons. Can follow any prior best practice if available.

@@ -0,0 +1,65 @@
# .github/workflows/create-rc-release.yml
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively, I could add one more conditional to "Main - post-commit" to jump straight to package publishing. However, this workflow also runs validations for rc versions. Not heavily opinionated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant