Bump version to 9.6.166 for Plinth 1.66 - #25
Merged
Conversation
The third component of the version now encodes the Plinth version the compiler targets (1.66 -> 166) rather than being an opaque marker, so that users can tell which plutus-tx a given uplc-ghc has to be used with. Nothing else in the version conveyed that, and the coupling is strict: uplc-ghc only compiles Plinth code against the plutus-tx it was built against, which plinth-test.cabal pins to ^>=1.66.0.0. Re-releases of the same Plinth version are distinguished by the fourth component (9.6.166.X for RELEASE=YES, 9.6.166.DATE otherwise), so the trailing release counter that the old 1501 carried in the third component is dropped. Also document the scheme in configure.ac, which recorded neither the meaning of 1501 nor that the minor is written with two digits -- a future Plinth 1.7 must map to 170, not 17, or the version silently goes backwards. Note that 166 is numerically below 1501. Nothing was ever published as 1501 (there are no tags yet), so no public version regresses; doing this before the first release keeps the numbering coherent from v1 onward. Since the version is part of the package unit-ids and keys cabal's store directory (ghc-9.6.166-plinth), this invalidates existing _build trees and any dependencies previously built against 9.6.1501. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 third component of the version now encodes the Plinth version the compiler targets (1.66 -> 166) rather than being an opaque marker, so that users can tell which plutus-tx a given uplc-ghc has to be used with. Nothing else in the version conveyed that, and the coupling is strict: uplc-ghc only compiles Plinth code against the plutus-tx it was built against, which plinth-test.cabal pins to ^>=1.66.0.0.
Re-releases of the same Plinth version are distinguished by the fourth component (9.6.166.X for RELEASE=YES, 9.6.166.DATE otherwise), so the trailing release counter that the old 1501 carried in the third component is dropped.
Also document the scheme in configure.ac, which recorded neither the meaning of 1501 nor that the minor is written with two digits -- a future Plinth 1.7 must map to 170, not 17, or the version silently goes backwards.
Note that 166 is numerically below 1501. Nothing was ever published as 1501 (there are no tags yet), so no public version regresses; doing this before the first release keeps the numbering coherent from v1 onward.
Since the version is part of the package unit-ids and keys cabal's store directory (ghc-9.6.166-plinth), this invalidates existing _build trees and any dependencies previously built against 9.6.1501.