change the Compiler.jl stdlib version to 0.1.0#58420
Merged
Conversation
In JuliaRegistries/General#130304 I proposed naming the placeholder version of the Compiler stdlib "v0.0.0" and made changes accordingly. However, after further discussions around adjusting Pkg.jl (c.f. JuliaLang/Pkg.jl#4233), we decided to call it "v0.1.0" instead since the idea may sound to be an abuse of semver and that versioning wouldn't be able to handle cases when any changes to the implementation of that special version are needed in the future. As a result, this commit changes the version of the Compiler.jl stdlib implementation maintained in the base from v0.0.0 to v0.1.0. Since BaseCompiler.jl is a very internal, special package that doesn’t yet follow proper versioning, there’s no need to worry about ecosystem impact from this change.
Member
|
Shouldn't the version in Base be 1.0-dev, while the special version in |
aviatesk
added a commit
that referenced
this pull request
Jun 16, 2025
In JuliaRegistries/General#130304 I proposed naming the placeholder version of the Compiler stdlib "v0.0.0" and made changes accordingly. However, after further discussions around adjusting Pkg.jl (c.f. JuliaLang/Pkg.jl#4233), we decided to call it "v0.1.0" instead since the idea may sound to be an abuse of semver and that versioning wouldn't be able to handle cases when any changes to the implementation of that special version are needed in the future. As a result, this commit changes the version of the Compiler.jl stdlib implementation maintained in the base from v0.0.0 to v0.1.0. Since BaseCompiler.jl is a very internal, special package that doesn’t yet follow proper versioning, there’s no need to worry about ecosystem impact from this change.
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.
In JuliaRegistries/General#130304 I proposed naming the placeholder version of the Compiler stdlib "v0.0.0" and made changes accordingly. However, after further discussions around adjusting Pkg.jl (c.f. JuliaLang/Pkg.jl#4233), we decided to call it "v0.1.0" instead since the idea may sound to be an abuse of semver and that versioning wouldn't be able to handle cases when any changes to the implementation of that special version are needed in the future.
As a result, this commit changes the version of the Compiler.jl stdlib implementation maintained in the base from v0.0.0 to v0.1.0.
Since BaseCompiler.jl is a very internal, special package that doesn’t yet follow proper versioning, there’s no need to worry about ecosystem impact from this change.