Release 1.5.33

[btsouth]

Re-cuts the release after a bug was found in the 1.5.32 build.

Why 1.5.33 and not a re-tag

1.5.32 was tagged, signed, drafted, and its installers uploaded to the versioned download path, but the GitHub release was never published, so nobody received it. Tags are immutable, so this follows the repo's own precedent from 1.5.31 superseding the unpublished 1.5.30: bump the version, note what happened, and leave v1.5.32 in place as a marker.

What is different from 1.5.32

One fix, #319. The taskbar strip was cutting the last character off a reset, which is what the 1.5.32 build was rejected for: it rendered Monthly · 10d 1 and read as a countdown an hour out rather than as a line that had been cut.

Everything else in the 1.5.32 notes carries over unchanged.

Changes here

• Version to 1.5.33 in version.env, rust/Cargo.toml, apps/desktop-tauri/src-tauri/Cargo.toml, apps/desktop-tauri/package.json, and tauri.conf.json. Build number 134 to 135, Cargo.lock follows.
• The dated 1.5.32 section is re-dated 1.5.33, with a paragraph recording what happened to that tag, and the strip fix folded into its Fixed list. Unreleased is left empty.

Validation

scripts\local-check.ps1 -All -Version 1.5.33, 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	576 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, for a reason outside this diff: it shells out through the npm shim at %APPDATA%\npm\cmd, which is not a valid Win32 executable here, so CreateProcessW fails with error 193 before reaching anything Ceiling owns. Re-run with --skip tty_runner: 1021 passed, 0 failed. CI runs that job on a runner where the shim is intact.

The three release-doctor warnings are the usual "does not exist yet" set: no local v1.5.33 tag, no GitHub release, and a local assets directory belonging to another machine.

After merge

Tag v1.5.33 on the merge commit and push. release.yml builds from the tag, signs, packages, verifies, and opens a draft release plus the R2 upload. Publishing the draft stays manual.

Note

Release version 1.5.33 of the desktop app

Bumps version from 1.5.32 to 1.5.33 across all package manifests, build metadata, and the Tauri app config. The changelog consolidates 1.5.32 content into 1.5.33, adding a taskbar reset fix under the Fixed section.

^{Macroscope summarized c2dce8e.}

[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	c2dce8e	Commit Preview URL Branch Preview URL	Aug 16 2026, 08:37 PM

[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: 35 minutes

Limit details: You’ve used all 1 included review currently available under your plan. You completed 94 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour.

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: CHILL

Plan: Pro Plus

Run ID: 987a66bc-4e6a-46f7-8ae4-c079b9c62819

📥 Commits

Reviewing files that changed from the base of the PR and between 5c3c676 and c2dce8e.

⛔ 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

---

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

[github-actions]

Automated review

Found 1 issue:

1. Supersede note says nobody received 1.5.32, but the Store installer is public

   CHANGELOG.md:9 · disposition: advisory · confidence: high · severity: low · quick win

   The new 1.5.33 paragraph says 1.5.32 was tagged, signed, and drafted, that installers were uploaded to the versioned download path, and that no one received it. The GitHub release is gone, but https://downloads.ceiling.win/releases/v1.5.32/Ceiling-1.5.32-Store-Setup.exe (and its .sha256) return HTTP 200 with Cache-Control immutable. Anyone with that URL already has the 1.5.32 bits; the sentence is internally contradictory. Regular Setup.exe and portable.exe on that same path 404, so 'installers' is also broader than what the path actually holds.

   Prompt for AI agents

   In CHANGELOG.md around line 9: Rewrite the clause to what is true: the GitHub release was never published, so the in-app updater never offered 1.5.32, while the Store installer remains on the immutable R2 URL. Do not claim nobody could have obtained that build. Verify against the current code first; if no longer valid, skip with a brief reason. Keep the change minimal.

_{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.}