Skip to content

delete Compiler.jl versions v0.0.1~v0.0.3 and register v0.0.0 only#130304

Merged
DilumAluthge merged 2 commits intoJuliaRegistries:masterfrom
aviatesk:avi/yank-Compiler-stdlib
May 7, 2025
Merged

delete Compiler.jl versions v0.0.1~v0.0.3 and register v0.0.0 only#130304
DilumAluthge merged 2 commits intoJuliaRegistries:masterfrom
aviatesk:avi/yank-Compiler-stdlib

Conversation

@aviatesk
Copy link
Copy Markdown
Contributor

@aviatesk aviatesk commented May 5, 2025

The management policy for the Compiler.jl stdlib is being changed, so this modification is required accordingly.
For more details, see JuliaLang/julia#57520 (comment).

@GunnarFarneback
Copy link
Copy Markdown
Contributor

I don't have enough insights about what could or should be done in this case but I will object that the title is misleading. This is not yanking but deletion. Yanking is a specific term which means adding a yanked = true field in Versions.toml, which means that the version can still be instantiated but no longer is considered by the Pkg resolver.

@aviatesk aviatesk changed the title yank Compiler.jl version from 0.0.1~0.0.3 and register v0.0.0 only delete Compiler.jl versions v0.0.1~v0.0.3 and register v0.0.0 only May 5, 2025
@aviatesk
Copy link
Copy Markdown
Contributor Author

aviatesk commented May 5, 2025

Thanks, I changed the title.

@aviatesk aviatesk force-pushed the avi/yank-Compiler-stdlib branch from edfe379 to 4a6619f Compare May 5, 2025 06:58
@aviatesk aviatesk force-pushed the avi/yank-Compiler-stdlib branch from 4a6619f to 8765729 Compare May 6, 2025 04:11
@DilumAluthge
Copy link
Copy Markdown
Member

I discussed this on Slack with @aviatesk and Kristoffer.

@DilumAluthge DilumAluthge merged commit 1f8fba8 into JuliaRegistries:master May 7, 2025
9 checks passed
aviatesk added a commit to aviatesk/General that referenced this pull request May 14, 2025
In JuliaRegistries#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 removes. v0.0.0 and releasing 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.
KristofferC pushed a commit that referenced this pull request May 14, 2025
In #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 removes. v0.0.0 and releasing 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.
aviatesk added a commit to JuliaLang/julia that referenced this pull request May 15, 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.
aviatesk added a commit to JuliaLang/julia that referenced this pull request May 15, 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.
aviatesk added a commit to JuliaLang/julia 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants