Release 2.1.0 - #91
Merged
Merged
Conversation
This reverts commit a7ece06. 2.0.1 was bumped in the repository but never published: RubyGems goes 2.0.0, 1.1.0, 1.0.0, 0.7.4. The number stood for a release that does not exist.
Minor, not a patch: required_ruby_version moves from >= 3.1.0 to >= 3.3, so this will not install on Ruby 3.1 or 3.2. Nothing in the API or the shipped assets changed, which is why it is not a major -- for a caller already on Ruby 3.3+ the upgrade from 2.0.0 is a no-op. Also in this release: spec.files became a whitelist, so the package drops from 21 files to 12. Everything removed is inert for consumers -- screen/screen.png, package.json, Rakefile, Gemfile, .gitignore, CODE_OF_CONDUCT.md, the gemspec itself, the CI workflow and tasks/test.rake. Nothing requirable left the package. npm package version bumped to match.
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
1 participant
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.
Two commits: revert the unpublished
2.0.1bump, then release2.1.0.Why the
2.0.1bump is reverteda7ece06set the version to 2.0.1, but 2.0.1 was never pushed. RubyGems goes 2.0.0, 1.1.0, 1.0.0, 0.7.4 — the number stood for a release that does not exist, so the next tag would have been reachable from aversion.rbthat never matched anything shipped.Why 2.1.0 and not 2.0.1 or 3.0.0
The only consumer-visible change since 2.0.0 is in the gemspec:
Also in this release
spec.filesbecame a whitelist, so the package drops from 21 files to 12. What left:screen/screen.png,package.json,Rakefile,Gemfile,.gitignore,CODE_OF_CONDUCT.md, the gemspec itself,.github/workflows/ci.yml,tasks/test.rake. None of it is requirable or used at runtime — the gem now ships onlylib,app,config, README and LICENSE.The npm package version is bumped to match.
Built locally
active_admin_datetimepicker-2.1.0.gem, contents verified — 12 files, no specs, no screenshots, no build artifacts.