Repository navigation
Publish only the versions RubyGems lacks - #8
Merged
Merged
Conversation
The release workflow pushed both gems unconditionally, so a run for a version already on RubyGems failed on its refusal to overwrite. That is the normal case when a release is published by workflow_dispatch (from an environment that cannot push tags) and its tag is pushed afterwards to create the GitHub release: the tag's run would attach the gems and then go red. Each gem is now pushed only when RubyGems does not list its version, the check solid_agent's release workflow already makes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0124DWuS48dmwj6duguc2wmh
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
The release workflow pushed both gems unconditionally, so any run for a version already on RubyGems failed on RubyGems' refusal to overwrite it.
That is the normal case when a release is published by Run workflow (
workflow_dispatch, for an environment that cannot push tags) and its tag is pushed afterwards to create the GitHub release: the tag's run attaches the gems, then goes red.Each gem is now pushed only when
gem list --remote --exact --alldoes not list its version, the same check solid_agent's release workflow already makes. The core is still published before the adapter that depends on it.This prepares the 0.3.2 release: main already carries 0.3.2 for both gems and its changelog, and RubyGems has 0.3.1.
Test plan
mainpublishes both gems at 0.3.2🤖 Generated with Claude Code
https://claude.ai/code/session_0124DWuS48dmwj6duguc2wmh
Generated by Claude Code