[noah-meierlabs]

Prepares a release of every package with unpublished changes.

package	npm now	new
chuchi	0.1.6	0.1.7
chuchi-utils	0.1.6	0.1.7
chuchi-core	0.1.5	0.1.6 (first JSR release, JSR was at 0.1.1 locally)
chuchi-legacy	1.1.0	1.1.1 (first JSR release)

• Versions: package.json and jsr.json are bumped together, because the publish job checks both against the tag.
• JSR exports now match package.json: chuchi adds ./api and ./cookies, chuchi-legacy adds ./dom/Context2d and ./dom/utils.
• Legacy return types: the dom utils in chuchi-legacy get explicit return types, which JSR requires for public functions. The generated .d.ts is unchanged.
• CHANGELOG.md lists the changes. Under chuchi 0.1.7 it notes the breaking cookie change: set now defaults to Path=/, and cookies set on another path must be removed with that path.
• publish.yaml no longer passes NPM_TOKEN. Trusted Publishing is set up for all four packages, and the token from 2024 is most likely revoked.

PR #11 (link click handling) is not part of chuchi 0.1.7 unless it's merged before the tag.

After merging

Push one tag per package. utils and core go first, since chuchi and legacy depend on them:

git tag utils@v0.1.7 && git tag core@v0.1.6 && git push origin utils@v0.1.7 core@v0.1.6
git tag chuchi@v0.1.7 && git tag legacy@v1.1.1 && git push origin chuchi@v0.1.7 legacy@v1.1.1

Testing

build, check-fmt, check, lint pass, and check-jsr simulates @chuchi/utils@0.1.7, @chuchi/core@0.1.6, @chuchi/chuchi@0.1.7 and @chuchi/legacy@1.1.1 successfully.

🤖 Generated with Claude Code