Refresh deno.lock for the webcrypto-deltic republish - #50
Closed
lann wants to merge 1 commit into
Closed
Conversation
The webcrypto sibling republished @polymorph/webcrypto-deltic@0.0.0 with its deltic runtime imported from raw.githubusercontent.com at pre-58b2404 instead of depending on jsr:@deltic/runtime. deno install --frozen — the deltic-setup gate — fails loudly against the stale lockfile, breaking exam-deltic (and CI) on every branch. This refresh records the sibling's new module graph and unbreaks the exam; the endpoint exam passes against it (5/5). The convergence question the republish opens — a second deltic runtime copy riding inside the sibling's closure, invisible to the jsr:@deltic/* pin-drift gate — is filed separately.
Collaborator
Author
|
Retracting: the diagnosis was wrong, and this lockfile 'refresh' would have actively broken main. There was no sibling republish — @polymorph/webcrypto-deltic is consumed from the local .deps checkout (it is not on JSR at all). The raw-URL imports came from MY worktree's stale .deps/webcrypto checkout: it was cloned before #46 bumped WEBCRYPTO_PIN to the JSR-consuming sibling revision (a0c924d), and never refreshed after switching to a post-#46 branch. Re-running scripts/setup.sh converges the checkout, and main's committed deno.lock matches it exactly — the frozen-install gate and the identity gate both did their jobs correctly at every step. The lock in this PR recorded the stale checkout's graph and must not land. |
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.
@polymorph/webcrypto-deltic@0.0.0was republished (sibling motion today) with its deltic runtime imported fromraw.githubusercontent.comatpre-58b2404instead of depending onjsr:@deltic/runtime@0.1.0-pre.ga67ee83.deno install --frozen— thedeltic-setupgate — fails loudly against the stale lockfile, which breaksexam-deltic(and therefore CI) on every branch, independent of any change in this repository.This refreshes the lockfile to the sibling's new module graph. The endpoint exam passes against it (5/5 scenarios).
What the republish opens — a second deltic runtime copy riding inside the sibling's closure, which the
jsr:@deltic/*pin-drift gate inexam-delticcannot see — is a real convergence question, but not one this lockfile refresh decides. Filed as a follow-up issue.