release: cut stable 0.0.11 by NiveditJain · Pull Request #460 · FailproofAI/failproofai

NiveditJain · 2026-06-26T08:47:11Z

Stable release: `0.0.11`

Cuts the first stable release of the 0.0.11 line, on a luv-cut-X.Y.Z branch per the repo's release convention (block-version-bumps reserves version edits for cut branches). This PR only prepares main; the npm publish happens when the GitHub Release v0.0.11 is created (see How publishing works).

Changes

package.json: 0.0.11-beta.13 → 0.0.11. Dropping the -beta suffix makes publish.yml publish under the latest dist-tag instead of beta.
CHANGELOG.md: consolidate every 0.0.11-beta.* entry into a single ## 0.0.11 — 2026-06-26 section, preserving all 104 bullets and their original PR references. Grouped as:
Category Bullets
Breaking 2
Features 39
Fixes 35
Dependencies 8
Tests 1
Docs 19
The per-beta sections (beta.0–beta.12) are removed; ## 0.0.10 and older history are untouched.

Sanity check (all CI gates run locally, green)

Gate	Result
frozen-lockfile install	✅ no drift
quality — lint	✅ 0 errors (5 pre-existing `no-img-element` warnings)
quality — tsc `--noEmit`	✅ clean
quality — version-consistency	✅ no-op (no `packages/`)
test — unit	✅ 1895 passed / 104 files
build (`bun run build`)	✅ Next.js + dist bundles + standalone prune
docs — `validate:mdx`	✅ 300 pages parse cleanly
test-e2e	✅ 298 passed / 13 files

failproofai --version (fresh CLI build) reports 0.0.11.

How publishing works (for the merger)

Publishing is driven by GitHub Releases, not by merging this PR (.github/workflows/publish.yml):

Merge this PR so main is at 0.0.11.
Create a GitHub Release tagged v0.0.11.
publish.yml publishes 0.0.11 to npm under latest, publishes the alias packages, then auto-bumps main to 0.0.12-beta.0 with a [skip ci] commit.

Supersedes #459 (same change, opened on luv-459 before the cut-branch convention was applied).

🤖 Generated with Claude Code

Summary by CodeRabbit

Chores
- Updated the package version from 0.0.11-beta.13 to 0.0.11.

Promote the 0.0.11-beta line to the first stable 0.0.11 release: - package.json 0.0.11-beta.13 -> 0.0.11 (drops the -beta suffix so publish.yml publishes under the `latest` dist-tag, not `beta`). - Consolidate every 0.0.11-beta.* CHANGELOG entry into a single `## 0.0.11 — 2026-06-26` section (Breaking / Features / Fixes / Dependencies / Tests / Docs), preserving all 104 bullets and their PR references. The individual per-beta sections are removed. Done on a luv-cut-0.0.11 branch per the repo's release convention (block-version-bumps reserves version edits for luv-cut-X.Y.Z). Sanity-checked against all CI gates locally: lint (0 errors), tsc, 1895 unit tests, build, validate:mdx (300 pages), 298 e2e tests, and a frozen-lockfile install — all green. Publishing to npm happens when the GitHub Release v0.0.11 is created; publish.yml then auto-bumps main to 0.0.12-beta.0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TD26MQ8M3gyaTLN2cwufTf

coderabbitai · 2026-06-26T08:47:26Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3d8aae31-2c03-40c6-a00e-27e0649e4ca5

📥 Commits

Reviewing files that changed from the base of the PR and between cff2578 and b4eef09.

📒 Files selected for processing (2)

CHANGELOG.md
package.json

📝 Walkthrough

Walkthrough

package.json updates the package version from 0.0.11-beta.13 to 0.0.11.

Changes

Package Version Update

Layer / File(s)	Summary
Version bump `package.json`	`package.json` changes the published version string from the beta tag to the stable release.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I hopped by moonlight, soft and bright,
With a version nibble tucked just right.
From beta whiskers to stable cheer,
This little hop makes release day near.
🐇✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title concisely and accurately summarizes the main change: cutting the stable 0.0.11 release.
Description check	✅ Passed	The description is detailed and on-topic, covering purpose, changes, and validation, though it doesn't follow the template exactly.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

* fix: reliable cli_audit telemetry + point docs links at /introduction Separate PR (the 0.0.11 release PR #460 is already merged). Two changes: 1. The `failproofai audit` CLI dropped its telemetry on exit. src/audit/cli.ts emitted cli_audit_started/completed/failed fire-and-forget (void trackHookEvent), then die()->process.exit(1) (failed path) and process.exit(0) (empty-history path) killed the in-flight fetch before it landed — those events never reached PostHog. Now await the two exit-adjacent events before exiting, matching bin/failproofai.mjs's track() helper; cli_audit_started stays fire-and-forget since the multi-second scan keeps the process alive. New __tests__/audit/audit-cli-telemetry.test.ts asserts each path emits its event and that the exit-adjacent events are awaited before process.exit. 2. "Docs" landing links pointed at a bare root that doesn't resolve to a page. Point the failproofai --help LINKS banner, the dev/start launch banner, the dashboard "Reach Us" Documentation entry, and the README docs badge (English + 14 translations) at https://docs.befailproof.ai/introduction. Deep page links (e.g. /built-in-policies) are unchanged. All gates green locally: lint (0 errors), tsc, 1898 unit tests, build, validate:mdx (300 pages), 298 e2e tests. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TD26MQ8M3gyaTLN2cwufTf * fix: close the telemetry gaps found by the audit (auth CLI, server audit run, +) Follow-up to the cli_audit fix, addressing the rest of the telemetry audit: - Auth CLI (src/auth/cli.ts): same fire-and-forget bug as cli_audit — the terminal login/logout/whoami/otp events were dropped when the process exited. Now awaited (mid-flow events stay fire-and-forget behind interactive prompts). - Server-side audit run (POST /api/audit/run): ran runAudit() detached with NO telemetry. Now emits audit_run_started/completed/failed/rejected mirroring the CLI funnel; dashboard now emits the missing audit_rerun_succeeded too. - postinstall: track the build-missing failure (package_install_failed) awaited before exit(1) — previously invisible. - captureClientEvent: add keepalive:true so unload-time events aren't dropped. - login-verify: track validation-400s + add email/source for parity with login-request. - Property gaps: node_version on package_installed, drop duplicate version on first_install, subcommand+exit_code on cli_auth_invoked. - Deliberately left the hook hot-path error events fire-and-forget (awaiting them would add telemetry latency to every tool call). Tests: new __tests__/auth/auth-cli-telemetry.test.ts; extended audit-run-route, client-telemetry, and postinstall tests. All gates green: lint, tsc, 1905 unit, build, validate:mdx (300), 298 e2e. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TD26MQ8M3gyaTLN2cwufTf --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

NiveditJain mentioned this pull request Jun 26, 2026
release: promote 0.0.11-beta.13 to stable 0.0.11 #459
Closed

NiveditJain merged commit 2d3e16a into mainJun 26, 2026
12 checks passed

NiveditJain mentioned this pull request Jun 26, 2026
fix: reliable cli_audit telemetry + docs links → /introduction #461
Merged

coderabbitaiBot mentioned this pull request Jul 14, 2026
[failproofai-506] Release stable 0.0.13 #506
Merged

coderabbitaiBot mentioned this pull request Aug 4, 2026
[release-pipeline] Restrict stable releases to a maintainer allowlist #651
Merged

Navigation Menu

Uh oh!

release: cut stable 0.0.11 - #460

release: cut stable 0.0.11#460
NiveditJain merged 1 commit into
mainfrom
luv-cut-0.0.11

NiveditJain commented Jun 26, 2026•
edited by coderabbitai Bot
Loading

Uh oh!

coderabbitaiBot commented Jun 26, 2026•
edited
Loading

Walkthrough

Changes

Estimated code review effort

Poem

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Category	Bullets
Breaking	2
Features	39
Fixes	35
Dependencies	8
Tests	1
Docs	19

Uh oh!

Conversation

NiveditJain commented Jun 26, 2026• edited by coderabbitai BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Stable release: 0.0.11

Changes

Sanity check (all CI gates run locally, green)

How publishing works (for the merger)

Summary by CodeRabbit

Uh oh!

coderabbitaiBot commented Jun 26, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Poem

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

NiveditJain commented Jun 26, 2026•
edited by coderabbitai Bot
Loading

Stable release: `0.0.11`

coderabbitaiBot commented Jun 26, 2026•
edited
Loading