Skip to content

Conversation

@BrandonStalnaker
Copy link
Collaborator

Background

  • We no longer want to use semantic-release in our release process. This workflow allows us to set the release version manually and follow our branch protection rules by creating a release branch, doing the necessary changes for each release, and then creating a PR.

@BrandonStalnaker BrandonStalnaker self-assigned this Jan 16, 2026
@BrandonStalnaker BrandonStalnaker requested a review from a team as a code owner January 16, 2026 19:05
Copy link
Contributor

@nickolas-dimitrakas nickolas-dimitrakas left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Collaborator

@jamesnrokt jamesnrokt left a comment

Choose a reason for hiding this comment

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

It's probably worth pausing this and aligning across more of our repositories and systems unless you're seeing this as a temporary bandaid?

@BrandonStalnaker
Copy link
Collaborator Author

@jamesnrokt It certainly is a short term fix for our current release woes but in general I think it's a good path forward for us in that everything is gated behind a pull request which follows the new branch protection rules. We aren't allowed access to the keys that would allow us to upload the frameworks manually (I can send you the gChat link confirming this if you'd like) so this is kinda the only way forward with our other restraints.

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.

4 participants