Fix automated gem publishing workflow#11
Merged
Conversation
- Remove invalid gem-name parameter from rubygems/release-gem action - Add custom rake release task for CI environment - Fix RDoc title to use correct gem name - Include all files from previous automated publishing branch 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <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
2 participants
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
gem-nameparameter fromrubygems/release-gem@v1actionrake releasetask that works in CI environmentsdk-reforgeChanges
gem-nameparameterrake releasetask that builds and pushes gemTest plan
rake releasetask exists and is availableThis supersedes PR #10 and fixes the workflow issues.
🤖 Generated with Claude Code