Refresh the released tooling note - #50
Merged
Merged
Conversation
Route current pins to the installation manifest and retain the previous pair as dated history so the planning note does not contradict the released local default.
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 direct-compilation note still presented the previous package pair as current after the 0.4.0 tooling update. Route current pins to the installation manifest, record the released pair and successful prebuild, and preserve the earlier pair as dated history.
This changes documentation only. The runtime pins, workspace image, and installed tooling are unchanged.
Validation: pinned
script/checkpassed, andgit diff --checkpassed. The linked container CI and prebuild results belong to the released tooling revision; no fresh Codespace consumption is claimed.