Gem Rebuilds only on Version Bump
Until now, whenever you pushed a modified gemspec to a repository that is gem enabled, we rebuilt it, no questions asked. This was convenient if you needed to fix a…
Until now, whenever you pushed a modified gemspec to a repository that is gem enabled, we rebuilt it, no questions asked. This was convenient if you needed to fix a broken gem version, but had the very undesirable side effect of making it very easy to accidentally overwrite a good gem release with a broken development version.
We recently changed the system so that only gemspec pushes that contain a bumped version will be built. This will prevent accidental gem clobbering and we can now guarantee that when you release a specific gem version, that version will never change. The downside is that if you botch a release, you’ll need to bump the version in order to get a fix out. This is a small price to pay to ensure that good gems don’t get overwritten by bad gems.
Written by
Related posts
GitHub availability report: June 2026
In June, we experienced six incidents that resulted in degraded performance across GitHub services.
Q1 2026 Innovation Graph update: Open source collaboration is accelerating worldwide
New Innovation Graph data shows global developer communities growing faster than ever, with collaboration reaching new highs across many economies.
GitHub joins coalition advocating for fixes to California AI Transparency Act to protect open source
We’re calling for targeted amendments to resolve conflicts with open source licensing and align with international transparency frameworks while preserving regulatory intent.