Repository navigation
build(deps): refresh tooling and prepare 0.2.4 - #21
Merged
Merged
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. |
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.
Prepare SweetLink 0.2.4 with the unreleased browser/HTTP dependency refresh and workspace build fixes, and update WebSocket types to 8.18.2 and Ultracite to 7.12.2. Both new patches satisfy the 24-hour release-age policy; pnpm remains at 11.28.2 until the next patch clears that policy.
The release notes preserve every existing changelog bullet and open an empty 0.2.5 Unreleased section. SweetLink ships an npm package and has no notarized macOS artifacts.
Validation: the documented release gates passed on AWS Crabbox (lint, typecheck, all 263 tests across 55 files, and build), as did shared/demo builds and both built CLI entrypoints. The initial Corepack system-directory permission error was resolved with a writable shim directory before rerunning the complete gate.
The packed npm artifact also passed clean installation, CLI/daemon help, version 0.2.4, and a real
devtools status --jsoncommand against a synthetic HTTP endpoint. Independent Codex review found no actionable P0–P2 findings.