chore(release): log the shipped work and bump the desktop app to 0.1.1#269
Merged
Conversation
The last four promotions to main added iOS channel management, bot-creation parity, four desktop connector fixes, and the landing-page client section — none of which reached CHANGELOG.md. Meanwhile desktop-v0.1.0 is tagged at the CI-workflow commit, so the published .dmg predates every one of those desktop fixes, including the one where a restarted connector dropped its --config. That matters more than usual now that the README and the landing page put "Download for macOS" front and center. - CHANGELOG: fill in [Unreleased] with Added / Fixed sections covering the work, marking the desktop-only entries so it's clear what a desktop-v0.1.1 tag would carry. - Bump apps/macos to 0.1.1 across package.json, tauri.conf.json, Cargo.toml and Cargo.lock (verified with cargo metadata --locked). Tagging desktop-v0.1.1 stays a separate, deliberate step after this lands. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #268. Two release-hygiene gaps found while checking whether that promotion had a corresponding release — it didn't.
Gap 1 —
CHANGELOG.mdwas never updated[Unreleased]only held the earlier security/config-default changes. Nothing from the last four promotions was recorded: iOS channel management, bot-creation parity across web/macOS/iOS, the four desktop connector fixes, or the landing-page client section.This PR fills in
AddedandFixedsections covering that work, and marks the desktop-only entries (desktop) so it's obvious what adesktop-v0.1.1tag would actually carry.Gap 2 — the published
.dmgpredates every desktop fixdesktop-v0.1.0(pre-release, 2026-07-18) is tagged at6be78a38— the commit that added the release workflow. I verified each desktop commit against that tag:desktop-v0.1.0?3fcbcbe5onboarding creates workspace dirs (zero-prep)02a5fe17resolve opencode adapter before minting a token27872bfbcarry--configon every connector restart4209abdf"Open in …" split button with app tilesSo anyone downloading today gets a build missing all four — including
27872bfb, where a restarted connector daemon came back without its config file and silently lost its workspace roots. That's worse now that #267 put Download for macOS in the README header and the landing-page hero.This PR bumps
apps/macosto 0.1.1 acrosspackage.json,tauri.conf.json,Cargo.tomlandCargo.lock(lockfile consistency verified withcargo metadata --locked).Not in scope
desktop-v0.1.1triggers a public build and release, so it stays a separate deliberate step after this lands onmain.packages/cheers-acp-connector-rs/— thefix(connector)commit changed gateway-sideserver/src/domain/connector_config.rs.connector-v0.1.28is still current; no connector release needed.🤖 Generated with Claude Code