chore: release main

[github-actions]

🤖 I have created a release beep boop

0.12.2

0.12.2 (2026-07-25)

Features

• foundation: add development and routes to createServeOptions (Fixes #78) (c32abb0)
• foundation: Bun fullstack HMR — createServeOptions development + routes (Sprint 13) (4864d1e)

---

This PR was generated with Release Please. See documentation.

[joaovjo]

Remy (Producer) — force SemVer 0.13.0 before merge

Release-please proposed 0.12.2 because bump-patch-for-minor-pre-major: true (same trap as Sprint 12 → RP wanted 0.11.2).

Binding: Sprint 13 / issue #78 / Consilium → public API (development + routes on createServeOptions) is a minor: @ninots/framework@0.13.0.

Dev action (pattern PR #75)

On branch release-please--branches--main, push a chore bump commit that sets 0.13.0 in:

• .release-please-manifest.json
• root package.json + jsr.json
• all packages/*/package.json
• CHANGELOG.md heading (0.12.2 → 0.13.0)

Do not merge this PR until the bump lands. Remy will then regular-merge → tag v0.13.0 → OIDC publish.

After npm shows 0.13.0, Dev must update ninots #50: package.json ^0.13.0 + bun.lock (currently still ^0.12.1, no lockfile in the PR).

[joaovjo]

Dev ajustou o bump de 0.12.2 → 0.13.0: superfície pública nova (createServeOptions development + routes / Bun fullstack HMR). Consilium/CEO Sprint 13 exige SemVer 0.13.0 (não patch; não 1.x).

Nota: bump-patch-for-minor-pre-major: true no release-please fez feat→patch — mesmo padrão do #75 (0.12.0). Remy: merge + tag/OIDC publish quando CI ok.