Release v0.2.0 #581

Merged
longjacksonle merged 1 commit from release/v0.2.0 into main 2026-07-23 05:41:44 +02:00

Automated release PR for v0.2.0, cutting the second tagged release from the current main (LC-617).

This is the first real exercise of the tag/publish machinery since the v0.1.0 seed: on merge, create-release.yml tags v0.2.0 and creates the Forgejo Release (body = auto git log since v0.1.0), build-oci-image.yml builds and publishes the v0.2.0 OCI image, and publish-release.yml cross-builds and uploads the desktop artifacts + signed latest.json.

Changes in the branch:

  • Workspace version bumped 0.1.0 -> 0.2.0 in Cargo.toml, with the two workspace-crate entries in Cargo.lock synced so a non---locked build does not re-dirty the lock.
  • CHANGELOG.md gains a curated ## [v0.2.0] section, folded from the [operator-action] markers in git log v0.1.0..HEAD per docs/releasing.md. Operator-visible highlights: session tokens hashed at rest (LC-514, one-shot re-hash on first startup, rotate pre-deploy backups), always-on security response headers (LC-504, reconcile with any fronting proxy), and the Tenor -> Giphy GIF migration (LC-505, swap LETS_CHAT_TENOR_* for LETS_CHAT_GIPHY_*).

Deploy note (LC-617): production (chat.psa.systems, nc-01) is still pinned to :v0.1.0 and staging (chat.a8n.systems, c-01) tracks :latest; both are repulled + restarted after this tag builds, then the Bunyip -> Let's Chat SSO is retested on both.

Automated release PR for **v0.2.0**, cutting the second tagged release from the current `main` (LC-617). This is the first real exercise of the tag/publish machinery since the v0.1.0 seed: on merge, `create-release.yml` tags `v0.2.0` and creates the Forgejo Release (body = auto `git log` since v0.1.0), `build-oci-image.yml` builds and publishes the `v0.2.0` OCI image, and `publish-release.yml` cross-builds and uploads the desktop artifacts + signed `latest.json`. Changes in the branch: - Workspace version bumped `0.1.0` -> `0.2.0` in `Cargo.toml`, with the two workspace-crate entries in `Cargo.lock` synced so a non-`--locked` build does not re-dirty the lock. - `CHANGELOG.md` gains a curated `## [v0.2.0]` section, folded from the `[operator-action]` markers in `git log v0.1.0..HEAD` per `docs/releasing.md`. Operator-visible highlights: session tokens hashed at rest (LC-514, one-shot re-hash on first startup, rotate pre-deploy backups), always-on security response headers (LC-504, reconcile with any fronting proxy), and the Tenor -> Giphy GIF migration (LC-505, swap `LETS_CHAT_TENOR_*` for `LETS_CHAT_GIPHY_*`). Deploy note (LC-617): production (`chat.psa.systems`, nc-01) is still pinned to `:v0.1.0` and staging (`chat.a8n.systems`, c-01) tracks `:latest`; both are repulled + restarted after this tag builds, then the Bunyip -> Let's Chat SSO is retested on both.
Release v0.2.0
All checks were successful
check-secrets / Nosey parker (push) Successful in 4s
check-secrets / TruffleHog (push) Successful in 4s
check-secrets / Kingfisher (push) Successful in 6s
check-secrets / Kingfisher (pull_request) Successful in 5s
check-secrets / TruffleHog (pull_request) Successful in 6s
check-secrets / Nosey parker (pull_request) Successful in 7s
Check / clippy + fmt + tests (pull_request) Successful in 6m46s
Create release / Create release from merged PR (pull_request) Successful in 5s
aa755a5545
Cut the second tagged release from main after ~508 commits on top of the v0.1.0 seed.

Bumps the workspace version 0.1.0 -> 0.2.0 (Cargo.toml + the two workspace-crate entries in Cargo.lock so a non-locked build does not re-dirty the lock) and curates a CHANGELOG.md [v0.2.0] section from the [operator-action] markers in git log v0.1.0..HEAD: session-token hashing at rest (LC-514) and always-on security response headers (LC-504) under Security; the Tenor to Giphy GIF migration (LC-505) plus the STT/LLM data-flow notes (LC-496, LC-486, LC-484, LC-483) under Changed; LiveKit stage audio (LC-512) under Added; and the retired LETS_CHAT_TENOR_* vars under Deprecated.

On merge, create-release.yml tags v0.2.0 and build-oci-image.yml publishes the image; publish-release.yml ships the desktop artifacts.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: longjacksonle <longjacksonle@gmail.com>
longjacksonle deleted branch release/v0.2.0 2026-07-23 05:41:44 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
psa-systems/lets-chat!581
No description provided.