Release v0.2.0 #581
Loading…
Reference in a new issue
No description provided.
Delete branch "release/v0.2.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.ymltagsv0.2.0and creates the Forgejo Release (body = autogit logsince v0.1.0),build-oci-image.ymlbuilds and publishes thev0.2.0OCI image, andpublish-release.ymlcross-builds and uploads the desktop artifacts + signedlatest.json.Changes in the branch:
0.1.0->0.2.0inCargo.toml, with the two workspace-crate entries inCargo.locksynced so a non---lockedbuild does not re-dirty the lock.CHANGELOG.mdgains a curated## [v0.2.0]section, folded from the[operator-action]markers ingit log v0.1.0..HEADperdocs/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, swapLETS_CHAT_TENOR_*forLETS_CHAT_GIPHY_*).Deploy note (LC-617): production (
chat.psa.systems, nc-01) is still pinned to:v0.1.0and 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.