Skip to content

update the tree hash of Compiler.jl stdlib v0.1.0#131938

Closed
aviatesk wants to merge 1 commit intoJuliaRegistries:masterfrom
aviatesk:avi/fix-Compiler-0.1
Closed

update the tree hash of Compiler.jl stdlib v0.1.0#131938
aviatesk wants to merge 1 commit intoJuliaRegistries:masterfrom
aviatesk:avi/fix-Compiler-0.1

Conversation

@aviatesk
Copy link
Contributor

I have modified the implementation of the Compiler.jl stdlib so that it can be installed on v1.10, and updated the tree hash for installation from General.

The Compiler.jl stdlib follows a special versioning policy and, for various reasons, is currently operated to have only v0.1.0 version. Therefore, instead of releasing a patch version, we are making a special accommodation by updating the tree hash on the General side.

I apologize for any recent inconvenience regarding the Compiler.jl stdlib, but such accommodations should not occur in the future.

I have modified the implementation of the Compiler.jl stdlib so that it
can be installed on v1.10, and updated the tree hash for installation
from General.

The Compiler.jl stdlib follows a special versioning policy and,
for various reasons, is currently operated to have only v0.1.0 version.
Therefore, instead of releasing a patch version, we are making a
special accommodation by updating the tree hash on the General side.

I apologize for any recent inconvenience regarding the Compiler.jl
stdlib, but such accommodations should not occur in the future.
@StefanKarpinski
Copy link
Contributor

StefanKarpinski commented May 29, 2025

Isn't this exactly what we discussed as not being allowed? My problem was not with using the version number 0.0.0, it was with changing the tree hash that any version number maps to.

@aviatesk
Copy link
Contributor Author

Yes, you are right. I also understand we shouldn't do this in general.

The only reason why I did this is that, if we prepare v0.1.1 for BaseCompiler.jl, it means we also need to bump the version in JuliaLang/julia. This causes a problem that we can't use the previons compiler implementations won't be available from packages using Compiler@0.1.1.
So I think it's still ideally better to just have a single version for this package.

That said, I also understand my approach might seem a bit arbitrary. If there's strong opposition, I'll accept the problem mentioned above and release v0.1.1 as usual.

@aviatesk
Copy link
Contributor Author

As Stefan pointed out, we will proceed with Compiler@0.1.1, and this will be replaced by #132990.

@aviatesk aviatesk closed this Jun 16, 2025
@aviatesk aviatesk deleted the avi/fix-Compiler-0.1 branch June 16, 2025 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants