release: prepare v0.2.0

[mohanagy]

Summary

• Finalizes the next unpublished release as 0.2.0.
• Synchronizes package.json and package-lock.json.
• Rolls all accumulated user-visible changes into the dated 0.2.0 changelog section rather than claiming unpublished 0.1.1 was released.
• Keeps documentation contracts valid both during development (Unreleased) and after release (the current dated section), and updates the preset compatibility version.

Security impact

• No runtime security behavior changes.
• The package will still publish only after reviewed development → main promotion through the OIDC-only workflow.

Validation

• npx vitest run for the affected release/documentation contracts
• npm test — 1,000 passed, 22 skipped
• npm run test:core — 392 passed, 22 skipped
• npm run test:coverage — 95.48% statements, 92.08% branches
• npm run lint
• npm run typecheck
• npm run build
• npm run smoke:cli
• npm run check:pack
• npm run test:package
• Current-head CI and review approval are required before merge.

Checklist

• Release PR base is development
• No false 0.1.1 release entry remains
• Release-promotion PR, GitHub Release, publish, provenance verification, and 0.1.0 deprecation remain post-merge steps

Tracks #6.

Summary by CodeRabbit

• New Features

  • Released version 0.2.0 with improved package metadata, verified publishing, and updated repository templates.
  • Added least-privilege continuous integration with secure trusted publishing.

• Bug Fixes

  • Improved fail-closed behavior for policy checks and upstream resource selection.
  • Strengthened configuration validation and secret redaction.
  • Prevented unintended credential injection in GitHub Docker presets.

• Documentation

  • Updated the documented package version to 0.2.0 and expanded release notes with the latest improvements.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: bc8aa9b9-2a20-4f2d-8811-9c1b4278e20f

📥 Commits

Reviewing files that changed from the base of the PR and between f04a48e and 0eeb28e.

📒 Files selected for processing (8)

• tests/fixtures/fake-upstream.mjs
• tests/identity-docs-contract.test.ts
• tests/package-contract.test.ts
• tests/preset-docs-contract.test.ts
• tests/profile-leases-docs-contract.test.ts
• tests/profile-runtime-isolation-docs-contract.test.ts
• tests/profile-state-docs-contract.test.ts
• tests/routing-context-docs-contract.test.ts

📝 Walkthrough

Walkthrough

The release is bumped from 0.1.1 to 0.2.0, with expanded changelog entries and updated package documentation. Release and documentation contract tests now validate the populated release section when Unreleased is empty.

Changes

0.2.0 release alignment

Layer / File(s)	Summary
Release metadata and changelog CHANGELOG.md, package.json, docs/presets-and-clients.md	Adds the 0.2.0 release notes and updates the documented package version.
Release version validation tests/release-version.test.ts	Updates release checks to 0.2.0 and validates its full release notes and issue references.
Documentation changelog fallback contracts tests/*-docs-contract.test.ts	Documentation contract tests use populated Unreleased content or fall back to the next release section.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related issues

• [Release] Ship v0.2.0 and deprecate unsafe v0.1.0 #6 — Directly covers the 0.2.0 release preparation, version updates, changelog changes, and release-contract tests.

Possibly related PRs

• mohanagy/miftah#45 — Updates release/version validation and changelog section selection alongside a package version bump.
• mohanagy/miftah#59 — Overlaps with the changelog fallback logic used by preset and profile documentation contract tests.
• mohanagy/miftah#61 — Aligns identity and related documentation contract tests with release-section changelog entries.

Poem

A bunny bumps the version bright,
From 0.1.1 to 0.2.0 tonight.
Changelog carrots neatly align,
Tests hop through each release sign.
Unreleased empty? No despair—
We nibble the next notes there!

---

Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

• Ignore

❌ Failed checks (1 error)

Check name	Status	Explanation	Resolution
Docstring Coverage	❌ Error	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title is concise and clearly summarizes the main change: preparing release v0.2.0.
Description check	✅ Passed	The description matches the template with Summary, Security impact, Validation, and Checklist sections, and includes concrete results for the main checks.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.2.0-prep

---

_{Comment @coderabbitai help to get the list of available commands.}