Repository navigation
Use the shared release workflow from RoleModel/actions - #2
Merged
Merged
Conversation
Replaces the bump, GitHub release, and gem publish workflows with one caller of RoleModel/actions/.github/workflows/release.yml@v3. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.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
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.
Replaces
bump_version.yml,release.yml, andpublish-package.ymlwith a singlerelease.ymlthat callsRoleModel/actions/.github/workflows/release.yml@v3, following the example in that repo's README.Gemfile.lockandCHANGELOG.md, then commits, tags, and pushes with the Version Manager App token.v*tag push creates the GitHub release and publishes the gem.Before merging
The RubyGems trusted publisher has to point at the reusable workflow: workflow filename
release.yml, Workflow Repository OwnerRoleModel, Workflow Repository Nameactions. Otherwise the publish job fails. You can fix the config and re-run that job; the tag and GitHub release will already exist.🤖 Generated with Claude Code