chore: roll the version back to 0.1.0 for the first release - #8
Merged
Conversation
The package is not registered — General has no `Versions.toml` for it and the repository has no tags — so 0.1.1 was never released and nothing depends on it. The open registration (JuliaRegistries/General#166832) is titled "New package: ExperimentalAPI v0.1.1", which would make the first published version 0.1.1 with no 0.1.0 behind it. The bump came from #4, a documentation-only change made before any release existed. Safe here in a way it usually is not: with nothing in the registry there is no version whose content this inverts, which is the failure mode a rollback normally carries. AutoRegister and VersionCheck are both disabled on this repository, so merging this triggers no registration. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
📚 Docs preview: https://codes.sota-shimozono.com/ExperimentalAPI.jl/previews/PR8/ (updates on each push to this PR) |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
The package is not registered: General has no
Versions.tomlfor it (404) and this repository has no tags. So0.1.1was never released, and nothing depends on it.The open registration JuliaRegistries/General#166832 is titled New package: ExperimentalAPI v0.1.1 — which would publish a first version with no
0.1.0behind it. The bump came from #4, a documentation-only change made before any release existed.Why this rollback is safe, when a rollback usually is not
Rolling a version back normally means a lower number carrying newer content, and once both are in a registry that is a permanent lie rather than an untidiness. Here there is no registered version to invert against — the registry has nothing at all for this package.
AutoRegisterandVersionCheckare bothdisabled_manuallyon this repository, so merging this triggers no registration.Not done here
Re-registering. The open General PR still says v0.1.1 and is unaffected by this merge; whether to close it and re-trigger for v0.1.0 is a separate, outward-facing decision.
🤖 Generated with Claude Code