Skip to content

Kura 0.1.0 — adopt June 0.1.0

Latest
Latest

Choose a tag to compare

View all tags
@linyiru linyiru released this 10 Jul 06:01
v0.0.68
ec0e538
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

All published @kurajs/* packages move to 0.1.0, adopting the June 0.1.0 line.

What changed

  • Adopts June 0.1.0. @kurajs/docs now peers @junejs/core at >=0.1.0 <0.2.0 (was <0.1.0). June shipped @junejs/core and @junejs/server 0.1.0; @junejs/cli 0.0.51 depends on >=0.1.0, so the whole June runtime resolves to the 0.1.0 line. A Kura project must now run June 0.1.x.
  • Coordinated version bump. Every published package moves to 0.1.0 together, so the Kura line tracks June's. Internal @kurajs peer/dep ceilings were widened <0.1.0 → <0.2.0, and changesets' onlyUpdatePeerDependentsWhenOutOfRange is enabled so an in-range peer bump no longer forces a spurious major.
  • No API changes. June 0.1.0 is additive at Kura's import surface — every subpath Kura uses (route, config, agent, i18n, outlet, islands-client) still exists. The suite is green on it: all package builds, 302 tests, an examples/docs build, and a running dev server serving HTML / .md / i18n / /search / /mcp.

Published to npm (with provenance)

@kurajs/core · @kurajs/search · @kurajs/tokenizers · @kurajs/ctrlk · @kurajs/transformers · @kurajs/docs · @kurajs/cli — all 0.1.0, published via OIDC trusted publishing with signed provenance.

Upgrading

npm install @kurajs/docs@0.1.0 @kurajs/cli@0.1.0

Ensure June resolves to 0.1.x (the default with @junejs/cli ≥ 0.0.51). No code changes are required.

Per-package changelogs: see each package's CHANGELOG.md. create-kura is unchanged at 0.0.17.

Assets 2
Loading