Skip to content

[failproofai-fp-cloud-cli-stable-release-78a2f6] Cut fp-cloud-cli 0.0.3 stable - #1005

Merged
NiveditJain merged 1 commit into
mainfrom
claude/fp-cloud-cli-stable-release-78a2f6
Nov 16, 2026
Merged

NiveditJain merged 1 commit into
mainfrom
claude/fp-cloud-cli-stable-release-78a2f6

Conversation

@NiveditJain

@NiveditJain NiveditJain commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

Cuts fp-cloud-cli 0.0.3 stable.

  • fp-cloud-cli/fp_cli/_version.py: 0.0.3b1 → 0.0.3
  • fp-cloud-cli/CHANGELOG.md: the 0.0.3b1 stub becomes the 0.0.3 section, carrying the full diff from 0.0.2 (browser fp login, the restored look, the wider typer range). It is the GitHub Release body.
  • Root CHANGELOG.md entry.

Nothing landed in fp-cloud-cli/ after the fp-cloud-cli-v0.0.3b0 tag except the bump commit, so 0.0.3 is the code 0.0.3b0 shipped.

Checked

  • scripts/python-version.py resolve → version=0.0.3, scheme=stable, next_version=0.0.4b0, tag=fp-cloud-cli-v0.0.3
  • scripts/changelog-section.py fp-cloud-cli/CHANGELOG.md 0.0.3 returns the section
  • PyPI answers 404 for 0.0.3
  • pytest tests/ in fp-cloud-cli: 1744 passed, 1 skipped
  • uv build produces fp_cloud_cli-0.0.3-py3-none-any.whl

After merge

Dispatch publish-fp-cloud-cli.yml on main. Its bump job then opens 0.0.4b0.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • New Features
    • fp-cloud-cli 0.0.3 is now available as a stable release. Install it with pipx install fp-cloud-cli without the --pre flag.
    • Sign in through a browser, with terminal and email-code alternatives available.
  • Documentation
    • Release notes clarify that the PyPI release does not change the npm version, which remains 1.0.14-beta.0.
    • The CLI release notes describe updated visuals and sign-in options.

The 0.0.3b1 line the bump job opened after 0.0.3b0 had nothing land against
it. Cut it stable so publish-fp-cloud-cli.yml releases 0.0.3, the code 0.0.3b0
shipped; its bump job then opens 0.0.4b0 on main.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Thanks @NiveditJain for your contribution to Failproof AI! 🙌

We'd love to discuss your PR and welcome you to our community.

Discord: https://discord.befailproof.ai/
Reddit: https://www.reddit.com/r/failproofai/

@coderabbitai

coderabbitai Bot commented Nov 16, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The CLI version changes from 0.0.3b1 to 0.0.3. The root and CLI changelogs document the stable release, including the CLI’s release notes and the npm version distinction.

Changes: Stable fp-cloud-cli release

Layer / File(s) Summary
Version and release notes
fp-cloud-cli/fp_cli/_version.py, fp-cloud-cli/CHANGELOG.md, CHANGELOG.md
The package version changes to 0.0.3. The changelogs document the stable release, its features and dependency range, and the npm version distinction. The CLI changelog replaces the prior prerelease entry.

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Other

Suggested reviewers: chhhee10, siddarthaa

Merge Risk: Minimal · up to 41d62

This cuts the stable 0.0.3 release of the CLI by updating the version and release notes. No concrete merge risk was found.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the main change: cutting fp-cloud-cli 0.0.3 as a stable release. The changeset bumps the version in _version.py from 0.0.3b1 to 0.0.3, turns the changelog stub into a 0.0.3 section, an…
Description check Passed The description covers the purpose (cutting the 0.0.3 stable release), the file-level changes, verification steps, and post-merge actions. It does not follow the repository template: it has no 'Type o…
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.
Full details: Title check

Explanation

The title names the main change: cutting fp-cloud-cli 0.0.3 as a stable release. The changeset bumps the version in _version.py from 0.0.3b1 to 0.0.3, turns the changelog stub into a 0.0.3 section, and adds a root changelog entry. The bracketed prefix is a branch-style identifier, but the rest of the title is specific and accurate.

Full details: Description check

Explanation

The description covers the purpose (cutting the 0.0.3 stable release), the file-level changes, verification steps, and post-merge actions. It does not follow the repository template: it has no 'Type of Change' section and no template checklist (npm run lint, npx tsc --noEmit, npm run test:run, npm run build). The template targets the JavaScript toolchain, and this PR is a Python release, so those items may not apply. The author should still state the change type or explain why the template checklist is not used.

Resolution

Optional: add the 'Type of Change' selection (this PR is a release bump, so none of the listed types fits cleanly; the author can note that). Also state whether the template checklist applies to this Python package or explain why it is omitted.

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

A rabbit checks the version line,
And finds the stable digits shine.
The changelog notes the release day,
While npm keeps its own display.
Then hops away through fields of green.

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 019d3d99-650d-4051-8889-5dc1af541f58
Commits

Reviewing files that changed from the base of the PR and between 78129c3 and 41d623d.

Files selected for processing: 3

  • CHANGELOG.md
  • fp-cloud-cli/CHANGELOG.md
  • fp-cloud-cli/fp_cli/_version.py

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.

@hermes-exosphere

hermes-exosphere commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

pr-autopilot finished reviewing commit 41d623d: approved. The results are in the review and the summary.

@hermes-exosphere hermes-exosphere left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved at the repository maintainer’s request. CI checks passed or were skipped. This approval does not represent an independent code review or local test run.

@NiveditJain
NiveditJain merged commit 48cd8e7 into main Nov 16, 2026
31 checks passed

@hermes-exosphere hermes-exosphere left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. Stable versioning, release notes, packaging, and installed CLI checks passed.

What the PR says it does

Claim Evidence
verified Prepare an installable stable fp-cloud-cli 0.0.3 release. Fresh build produced the 0.0.3 wheel and source archive. Installed CLI and wheel metadata report 0.0.3.
verified The stable release retains the code shipped in 0.0.3b0. Comparison with fp-cloud-cli-v0.0.3b0 shows only CHANGELOG.md and _version.py differ within fp-cloud-cli.
verified Release notes include browser login, restored presentation, and the wider Typer range. Changelog extraction returned the stable section. Installed CLI login fixtures and help screens passed; wheel metadata declares typer>=0.13,<0.30.
verified Add the root changelog entry without changing the npm version. Root changelog includes #1005; package.json remains 1.0.14-beta.0.
verified The release pipeline resolves the stable tag and next development version. Resolver returned scheme=stable, is_prerelease=false, next_version=0.0.4b0, and tag=fp-cloud-cli-v0.0.3. Bump scripts successfully opened 0.0.4b0 on temporary copies.
verified PyPI has not already taken version 0.0.3. GET https://pypi.org/pypi/fp-cloud-cli/0.0.3/json returned HTTP 404.
untested After publication, a default pipx install receives this release and the workflow opens 0.0.4b0 on main. Local artifacts and scripts passed, but publication and remote jobs cannot be exercised without credentials; 0.0.3 is not yet published.

Notes

  • No blocking regression found. The working tree remains clean.
  • Real Cloud authentication, PyPI publication, and the GitHub post-release jobs remain untested because credentials are unavailable.
What was run
  • git diff origin/main...HEAD
  • git diff --name-status fp-cloud-cli-v0.0.3b0..HEAD -- fp-cloud-cli
  • git log --format='%h %s' fp-cloud-cli-v0.0.2..HEAD -- fp-cloud-cli
  • . /kit/bin/kit-env.sh; check fp-cli
  • bunx vitest run tests/ci/python-version-pipeline.test.ts
  • cd fp-cloud-cli && uv build --out-dir /out/kit/review-build
  • python3 scripts/python-version.py resolve fp-cloud-cli/fp_cli/_version.py fp-cloud-cli
  • python3 scripts/changelog-section.py fp-cloud-cli/CHANGELOG.md 0.0.3
  • curl -sS --max-time 20 https://pypi.org/pypi/fp-cloud-cli/0.0.3/json
  • fp-smoke
  • python3 /out/kit/review-fp-cli.py
  • python3 fp-cloud-cli/tests/fake_cloud_smoke.py --fp /tmp/kit/venv-fp/bin/fp --artifacts /out/kit/review-fp-cloud-smoke
  • python3 /out/kit/review-fp-login.py
  • python3 scripts/python-version.py write /out/kit/review-next-version.py 0.0.4b0
  • python3 scripts/changelog-open.py /out/kit/review-next-changelog.md 0.0.4b0 0.0.3 2026-11-16
  • Playwright screenshot of captured CLI output → /out/screenshots/fp-cloud-cli-0.0.3.png
  • git status --short

Reviewed commit 41d623d with gpt-6.1-sol. A person merges.

pr-autopilot · Codex in a locked-down container · traced by failproofai

@hermes-exosphere

Copy link
Copy Markdown
Contributor

pr-autopilot review

Verdict Approved
Head 41d623d
Round 1
Ran failproofai kit: the PR's stack booted in 45s
Tests 9 passed · 0 failed · 1 could not run
Findings 0 open · 0 resolved

Approve. Stable versioning, release notes, packaging, and installed CLI checks passed.

What this changes

  • Promotes fp-cloud-cli from 0.0.3b1 to stable 0.0.3.
  • Replaces the beta changelog stub with stable release notes.
  • Adds a root changelog entry; npm remains at 1.0.14-beta.0.

What was run against this PR

Result Test How Evidence
✅ pass Python CLI suite tests check fp-cli: 1744 passed, 1 skipped; locked dependency sync succeeded.
✅ pass Python release pipeline contracts tests bunx vitest run tests/ci/python-version-pipeline.test.ts: 74 passed.
✅ pass Stable distribution artifacts build uv build produced fp_cloud_cli-0.0.3-py3-none-any.whl and its source archive. Wheel inspection confirmed version, 51 Python modules, LICENSE, and Typer dependency range.
✅ pass Installed CLI smoke CLI 37 installed-CLI invocations passed, including all 30 command help screens, plain/JSON version, signed-out whoami, logout, and usage-error exit 2.
✅ pass Cloud fixture integration CLI fake_cloud_smoke.py drove 33 installed-CLI invocations against a local HTTP fixture; email login, cookie/key routing, and paused SSE approvals passed.
✅ pass Terminal login flows CLI Six installed-CLI pseudo-terminal flows passed against a local HTTP fixture: approval, Tab back to browser, Tab to email, unsupported-browser fallback, denial, and cancellation. Requests sent cli_version='fp 0.0.3' and kind='session'; successful credentials were saved with mode 0600.
✅ pass Release preflight and local bump CLI Version resolution, stable changelog extraction, PyPI HTTP 404, and next-version/changelog operations on temporary copies succeeded.
✅ pass Release source parity other Git comparisons confirmed executable code matches the beta tag and npm remains unchanged.
⏸️ could not run Initial smoke harnesses CLI fp-smoke cannot parse the existing boxed Commands panel. An initial reviewer script also expected an incorrect whoami JSON key. Corrected direct checks passed using the documented logged_in contract; neither issue is a PR regression.
✅ pass CLI output screenshot other Playwright captured the installed CLI output at /out/screenshots/fp-cloud-cli-0.0.3.png.

What the PR says it does

Claim Evidence
verified Prepare an installable stable fp-cloud-cli 0.0.3 release. Fresh build produced the 0.0.3 wheel and source archive. Installed CLI and wheel metadata report 0.0.3.
verified The stable release retains the code shipped in 0.0.3b0. Comparison with fp-cloud-cli-v0.0.3b0 shows only CHANGELOG.md and _version.py differ within fp-cloud-cli.
verified Release notes include browser login, restored presentation, and the wider Typer range. Changelog extraction returned the stable section. Installed CLI login fixtures and help screens passed; wheel metadata declares typer>=0.13,<0.30.
verified Add the root changelog entry without changing the npm version. Root changelog includes #1005; package.json remains 1.0.14-beta.0.
verified The release pipeline resolves the stable tag and next development version. Resolver returned scheme=stable, is_prerelease=false, next_version=0.0.4b0, and tag=fp-cloud-cli-v0.0.3. Bump scripts successfully opened 0.0.4b0 on temporary copies.
verified PyPI has not already taken version 0.0.3. GET https://pypi.org/pypi/fp-cloud-cli/0.0.3/json returned HTTP 404.
untested After publication, a default pipx install receives this release and the workflow opens 0.0.4b0 on main. Local artifacts and scripts passed, but publication and remote jobs cannot be exercised without credentials; 0.0.3 is not yet published.

Findings

No open findings.

Rounds

Round Reviewed Commits in this round Verdict
1 41d623d 41d623d Approved

Rewritten after every review, not posted again. Reviewed 41d623d with gpt-6.1-sol. A person merges.

pr-autopilot · Codex in a locked-down container · traced by failproofai

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.

2 participants