Skip to content

chore(dev-deps): adopt juniper 0.17.0 - #47

Merged
KyleJune merged 1 commit into
mainfrom
chore/adopt-juniper-0.17.0
Sep 24, 2026
Merged

KyleJune merged 1 commit into
mainfrom
chore/adopt-juniper-0.17.0

Conversation

@KyleJune

Copy link
Copy Markdown
Member

Summary

Moves every @udibo/juniper range in this repo from ^0.16.0 to ^0.17.0. The udibo monorepo is adopting juniper 0.17.0, and src/ is one of its workspace members, so a ^0.16.0 range here would leave a second jsr:@udibo/juniper@0.16 entry in its lock.

This PR is titled chore(dev-deps):, not chore(deps):, on purpose. .releaserc.json cuts a patch for chore(deps) and build(deps), and a chore(deps) squash-merge would publish a release. The published package does not change: juniper is imported only by src/react/_test_setup.ts, and the publish.exclude glob **/_test_* keeps that file out of the JSR payload. main has no commits after the 0.6.0 release commit, so merging this PR under this title should not cut a release. Keep the title when squash-merging.

Juniper 0.17.0

Juniper 0.17.0 (udibo/juniper#162, for juniper issue 157) keeps HTML documents private by default. When a loader, an action or a thrown error sets cache headers on a document, public, s-maxage and a field-named private become private, CDN cache fields become no-store, and an Expires sent without Cache-Control is dropped. A route opts out with c.set("publicDocument", true) in its middleware.

None of the juniper apps here (examples/juniper/app-with-own-auth, examples/juniper/app-with-external-auth, templates/juniper) set Cache-Control, Expires, s-maxage, Surrogate-Control or a CDN cache field. No page sets a public policy, so none of them behave differently.

Changes

  • src/deno.json: juniper ^0.17.0. It is a test-only import, as described above.
  • examples/juniper/app-with-own-auth, examples/juniper/app-with-external-auth, templates/juniper: juniper ^0.17.0.
  • deno.lock: only the juniper entries changed. They now resolve to 0.17.0.
  • smoke-consumer/deno.lock: rewritten by deno task check. Besides juniper 0.17, it picks up drift that was already on main: the linked @udibo/oauth2 moves from 0.5.0 to 0.6.0.

Testing

These were run from the repo root on this commit:

  • deno task check: pass
  • deno task test --parallel --reporter=dot: 225 passed (2611 steps)
  • deno task test:all: all 9 suites pass (package, scripts, 5 examples, 2 templates)

Closes

Nothing. This is a dependency alignment for the udibo monorepo, which points its submodule at this branch in a companion PR.

🤖 Generated with Claude Code

Move every @udibo/juniper range to ^0.17.0 so the udibo monorepo,
where src/ is a workspace member, carries no second juniper 0.16 lock
entry. Juniper is a test-only import of the published package and a
runtime dependency of the unpublished examples and template, none of
which set a cache header.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@KyleJune
KyleJune merged commit b70f2ed into main Sep 24, 2026
6 checks passed
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 0.7.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant