chore(deps): refresh the stale lockfile - #9
Merged
Merged
Conversation
`@std/testing`'s entry was missing its `jsr:@std/async` dependency, so a frozen install rejected the lockfile. This predates the release workflow — the same failure reproduces on d9fc4c7 — but nothing caught it, because the old publish workflow ran `npx jsr publish` without ever installing from the lock. The new release job runs `deno ci`, which is frozen, so it surfaced there first. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
🎉 This PR is included in version 0.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Summary
Unblocks the Release job on main, which failed at
deno ciwith:@std/testing's lock entry was missing itsjsr:@std/asyncdependency — a one-line omission.This predates the release workflow. The same frozen install fails on
d9fc4c7, before any of #8's commits. It went unnoticed because the oldpublish.ymlrannpx jsr publishand never installed from the lock; the new release job runsdeno ci, which is frozen, so it was the first thing to check.Also fixed outside this PR: the missing tag baseline
The repo had zero git tags, so semantic-release would have treated its first run as an initial release and published 1.0.0, not the 0.4.0 that #8's
feat:commit implies.I've pushed a
0.3.0tag atd9fc4c7— the commit whosedeno.jsonsays0.3.0, matching JSR's current latest. With that baseline in place, semantic-release analyses commits since 0.3.0, findsfeat: make less, sass, and stylus optional, and cuts 0.4.0.No change was needed for the merge commit itself: merging #8 with a merge commit preserved both underlying commits on main, so the
feat:commit is still there to be analysed.Testing
deno install --frozenpasses. Full suite green — 6 passed, 0 failed.