Skip to content

release: promote v0.5.2 to main - #307

Merged
mohanagy merged 4 commits into
mainfrom
development
Jul 29, 2026
Merged

release: promote v0.5.2 to main#307
mohanagy merged 4 commits into
mainfrom
development

Conversation

@mohanagy

Copy link
Copy Markdown
Owner

Summary

Promotes the reviewed development release candidate for @lubab/miftah@0.5.2 to main.

Included since v0.5.1:

This is a compatible pre-1.0 patch release. It does not claim that the external evaluator gates in #25, #88, #204, or #290 are complete.

Security impact

The release keeps fail-closed config discovery, owner-only file and directory requirements, secret-value redaction, audit behavior, Windows containment, and public API compatibility. The Console readiness check uses environment-variable names only; it does not return or persist secret values.

Validation

The exact #306 head passed:

  • npm test
  • npm run test:core
  • npm run test:coverage
  • npm run lint
  • npm run typecheck
  • npm run build
  • npm run smoke:cli
  • npm run check:pack
  • npm run test:package
  • current-head Linux, macOS, Windows, Linux quality, and Verify CI

CodeRabbit's one actionable release-contract finding was fixed and resolved. Its current-head re-review was rate-limited; an independent review approved the release patch, and the final follow-up only strengthened the requested test contract.

Tracks #305.

mohanagy added 4 commits July 29, 2026 22:25
Show aggregate discovered/ready/attention counts without exposing rejected paths, explain safe repair categories, and preserve trusted discovery containment. Includes regression contracts and all review fixes.

Closes #203.
* fix(console): resume valid sessions after reload

* fix(console): explain unlock rate limiting
* fix(setup): explain environment secret readiness

* fix: make secret readiness guidance truthful

* fix: keep readiness guidance visible

* fix: preserve environment readiness invariants

* fix: prevent stale readiness guidance
* release: prepare v0.5.2

* test: bind release notes to current patch

* test: scope release links to fixed section
@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

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: 37 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: 04828237-8647-4826-9c23-49ffaf07dfaa

📥 Commits

Reviewing files that changed from the base of the PR and between 447c4fc and 7c742c2.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (25)
  • CHANGELOG.md
  • README.md
  • docs/cli.md
  • docs/console-api.md
  • docs/presets-and-clients.md
  • docs/whats-new-in-0.5.md
  • package.json
  • src/cli/client-snippets.ts
  • src/cli/init.ts
  • src/cli/main.ts
  • src/cli/setup.ts
  • src/console/console-application-service.ts
  • src/console/console-assets.ts
  • src/console/console-config-catalog.ts
  • src/console/console-config-metadata.ts
  • src/console/console-server.ts
  • src/setup/setup-completion.ts
  • tests/client-snippets.test.ts
  • tests/console-application-service.test.ts
  • tests/console-dashboard-application-service.test.ts
  • tests/console-server.test.ts
  • tests/oauth-console-threat-model-docs-contract.test.ts
  • tests/release-version.test.ts
  • tests/setup-command.test.ts
  • tests/setup-completion.test.ts

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

@mohanagy

Copy link
Copy Markdown
Owner Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@mohanagy

Copy link
Copy Markdown
Owner Author

Release gate update for exact head 7c742c21ed60057d0520c4675e7060482ba5960a:

  • Independent review: APPROVE. It verified the promotion contains exactly fix(console): explain filtered configurations #302, fix(console): preserve valid sessions across reloads #303, fix(setup): explain environment secret readiness #304, and release: prepare v0.5.2 #306; the non-ancestral main/development histories are tree-identical before this release delta; versioning, security boundaries, release contracts, and external-validation wording are correct.
  • CodeRabbit: automatic promotion review was skipped by branch policy; the requested one-off review was rate-limited. This is documented, not represented as an approval.
  • Current-head pull-request CI: Linux quality, macOS 20/22/24, Ubuntu 20/22/24, Windows 20/22/24, and Verify are green.
  • The simultaneous development push run initially had one unchanged 5-second Windows timing miss. Its failed job and dependent Verify gate were rerun unchanged and are green. The pull-request run likewise reran one unchanged Linux timing miss and completed fully green. No timeout, coverage, containment, or test setting changed.

@mohanagy
mohanagy merged commit 07d111d into main Jul 29, 2026
41 of 45 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant