Release 1.5.32

[tsouth89]

Cuts 1.5.32 from the three PRs that landed today (#315, #316, #317) plus the work already sitting in Unreleased.

Changes

• Version bumped to 1.5.32 in version.env, rust/Cargo.toml, apps/desktop-tauri/src-tauri/Cargo.toml, apps/desktop-tauri/package.json, and tauri.conf.json. Build number 133 to 134, Cargo.lock follows.
• Unreleased moved into a dated 1.5.32 - 2026-08-16 section with a summary line. Unreleased is left in place and empty.

Validation

scripts\local-check.ps1 -All -Version 1.5.32, run step by step:

Step	Result
Rust format	pass
Shared Rust clippy	pass
Tauri Rust clippy	pass
Shared Rust tests	1021 passed, see note
Tauri Rust tests	567 passed
Frontend tests	635 passed, 83 files
Frontend build	pass
Store submission preparation	pass
Release doctor	pass, 3 warnings

Note on the shared Rust suite. cli::tty_runner::tests::test_run_sends_script_through_pty fails on this machine only, and not for any reason in this diff. It shells out through the npm shim at %APPDATA%\npm\cmd, which is not a valid Win32 executable on this box, so CreateProcessW returns error 193 before the test reaches anything Ceiling owns. The suite was re-run with --skip tty_runner: 1021 passed, 0 failed. CI runs this job on its own runner where the shim is intact.

The three release-doctor warnings are all "does not exist yet" and clear when the tag is pushed: no local v1.5.32 tag, no GitHub release v1.5.32, and a local assets directory that belongs to a different machine.

After merge

Tag v1.5.32 on the merge commit and push it. release.yml then builds from the tag, signs through Azure, packages and verifies the installer, and opens a draft GitHub release plus the R2 upload. Publishing that draft stays a manual step.

Note

Release version 1.5.32

Bumps version identifiers across all package manifests and build config to 1.5.32, with build number incremented to 134. Updates CHANGELOG.md with Added, Security, Fixed, and Internal notes for the release.

^{Macroscope summarized bb5b64e.}

Summary by CodeRabbit

• New Features

  • Added provider outage badges and app-aware floating-bar selection.
  • Added activity heatmaps to Charts.
  • Added spend anomaly warnings.
  • Updated the release to version 1.5.32.

• Bug Fixes

  • Improved provider parsing, account selection, session discovery, locking, localization, theming, and unavailable-state handling.
  • Improved price and chart cache reliability, credential handling, and CLI log cleanup.

• Security

  • Restricted loopback access in production webview builds.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: caf7e713-d138-44bc-a2fb-08657eb2a92e

📥 Commits

Reviewing files that changed from the base of the PR and between 7c9eb1c and b01ad48.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (6)

• CHANGELOG.md
• apps/desktop-tauri/package.json
• apps/desktop-tauri/src-tauri/Cargo.toml
• apps/desktop-tauri/src-tauri/tauri.conf.json
• rust/Cargo.toml
• version.env

Included review availability: 0 reviews are currently available. Based on recent review activity, included reviews refill at 1 per hour.

---

📝 Walkthrough

Walkthrough

The release updates Ceiling to version 1.5.32 and build 134. The changelog records new features, fixes, and the release-only webview CSP behavior.

Changes

Ceiling 1.5.32 release preparation

Layer / File(s)	Summary
Version metadata apps/desktop-tauri/package.json, apps/desktop-tauri/src-tauri/Cargo.toml, apps/desktop-tauri/src-tauri/tauri.conf.json, rust/Cargo.toml, version.env	Updates package and application versions to 1.5.32 and the build number to 134.
Release notes CHANGELOG.md	Documents the 1.5.32 features, fixes, release webview CSP behavior, and dated release entry.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to b01ad

This change updates release metadata and notes for version 1.5.32; no actionable merge-blocking risk remains after normal checks and review.

Possibly related PRs

• tsouth89/ceiling#292: Updates the same release metadata files and changelog for a preceding release.
• tsouth89/ceiling#242: Uses the same release-preparation pattern.
• tsouth89/ceiling#181: Updates the same version metadata and changelog files.

Suggested reviewers: finesssee

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the 1.5.32 release, which matches the primary version and changelog updates.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/1.5.32

---

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

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	ceiling	bb5b64e	Commit Preview URL Branch Preview URL	Aug 16 2026, 06:19 PM

[github-actions]

Automated review

New in this pass: 1 issue.

1. Spend warning notes omit opt-in and Codex/Claude-only scope

   CHANGELOG.md:13 · disposition: fix-if-quick · confidence: high · severity: medium · quick win

   The 1.5.32 intro and Added bullet describe a warning that fires when today's spend runs far above the recent norm and needs no budget. spend_anomaly_alerts_enabled defaults to false, and check_spend_anomaly also requires show_notifications, so a default install after this update never toasts. The same Added section already says the outage badge is off by default under Notifications; this bullet does not. Separately, local_usage_provider_ids keeps only codex and claude, so a Grok-only or Grok-heavy spike never enters the baseline or today's total even after the setting is turned on, while the heatmap bullet in the same notes names Grok as in-scope local spend.

   Prompt for AI agents

   In CHANGELOG.md around line 13: In the spend-warning bullet (and the intro if it still implies the warning just happens), state that it is off by default under Notifications and that it reads only local Codex and Claude logs. Do not change the stored default: false is a real user-settable choice and cannot be distinguished from the shipped off state. Verify against the current code first; if no longer valid, skip with a brief reason. Keep the change minimal.

Resolved since the previous pass: 1.

_{For coding agents: fix BLOCK and FIX IF QUICK findings now; everything else is tracked or informational; never exceed one CodeRev fix round per PR.}

_{Advisory. Findings generated by grok-subscription and muse-spark-1.2-contributor, each filtered through a 3-vote refutation panel with the changed code in evidence.}