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
![](https://github.blog/wp-content/uploads/2023/09/screencapture-innovationgraph-github-2023-09-20-15_44_54-1.png?resize=400%2C212)
How researchers are using GitHub Innovation Graph data to estimate the impact of ChatGPT
An interview with economic researchers who are applying causal inference techniques to analyze the effect of generative AI tools on software development activity.
![](https://github.blog/wp-content/uploads/2024/01/Enterprise-DarkMode-1.png?resize=400%2C212)
GitHub Availability Report: June 2024
In June, we experienced two incidents that resulted in degraded performance across GitHub services.
![](https://github.blog/wp-content/uploads/2024/06/AI-DarkMode-4.png?resize=400%2C212)
Advancing responsible practices for open source AI
Outcomes from the Partnership on AI and GitHub workshop.