psa-systems/lets-chat
Watch
9
0
Fork
You've already forked lets-chat
 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions

Release v0.1.0 #440

Merged
nrupard merged 1 commit from release/v0.1.0 into main 2026-06-24 17:31:11 +02:00
Conversation 0 Commits 1 Files changed 1 +7 -6
nrupard commented 2026-06-24 17:23:56 +02:00
Owner
Copy link

First tagged release of lets-chat: v0.1.0, the seed version already in Cargo.toml.

Why no version bump

just create-release <bump> computes the next version FROM the current Cargo.toml value, so from the 0.1.0 seed it can only emit 0.2.0 / 0.1.1 / 1.0.0 - never 0.1.0. For the first tag the seed IS the target (per docs/releasing.md: "no tag has been cut ... the repo is at v0.1.0, the seed version"), so this release branch carries the curated CHANGELOG as its commit and leaves the version untouched. Subsequent releases use the recipe normally.

What's in it

CHANGELOG.md ## [v0.1.0] folds the Pre-release seed (snapshot 2026-05-30) together with the operator-action commits that landed after it, gathered via git log --grep='\[operator-action\]' over the full history:

  • Security: LC-22 (Bunyip SSO only, local auth retired), LC-152 (outbound SSRF guard + Web Push fix), LC-206-IMAGE-LIMITS (GIF decompression-bomb DoS), LC-210-BINARY-INTEGRITY (signed desktop updates).
  • Changed: LC-78-AVATAR-PROXY (default-on), retention sweep (default-off), LC-205 (email-ingress webhooks).
  • Added: LC-77 / LC-77-REPLY (email ingress + reply), LC-207 (avatar diagnostics), LC-393 (server-side STT), LC-396 (transcript summaries).

On merge

.forgejo/workflows/create-release.yml tags the merge commit v0.1.0 and creates the Forgejo Release (auto git log body). The v* tag then fires:

  • build-oci-image.yml -> pushes dev.a8n.run/a8n-tools-private/lets-chat:v0.1.0 (+ latest).
  • publish-release.yml -> desktop Linux/Windows binaries + signed latest.json to Generic Packages. Precondition: DESKTOP_UPDATE_SIGNING_KEY secret + DESKTOP_UPDATE_PUBLIC_KEY variable must be provisioned (per docs/desktop-update-signing.md) or the publish job fails closed.

Pairs with docker PR #139: once lets-chat:v0.1.0 is in the registry, the nc-01 lets-chat-psa pin moves off :latest to :v0.1.0.

First tagged release of lets-chat: **v0.1.0**, the seed version already in `Cargo.toml`. ## Why no version bump `just create-release <bump>` computes the next version FROM the current `Cargo.toml` value, so from the `0.1.0` seed it can only emit `0.2.0` / `0.1.1` / `1.0.0` - never `0.1.0`. For the first tag the seed IS the target (per `docs/releasing.md`: "no tag has been cut ... the repo is at v0.1.0, the seed version"), so this release branch carries the curated CHANGELOG as its commit and leaves the version untouched. Subsequent releases use the recipe normally. ## What's in it `CHANGELOG.md` `## [v0.1.0]` folds the Pre-release seed (snapshot 2026-05-30) together with the operator-action commits that landed after it, gathered via `git log --grep='\[operator-action\]'` over the full history: - **Security**: LC-22 (Bunyip SSO only, local auth retired), LC-152 (outbound SSRF guard + Web Push fix), LC-206-IMAGE-LIMITS (GIF decompression-bomb DoS), LC-210-BINARY-INTEGRITY (signed desktop updates). - **Changed**: LC-78-AVATAR-PROXY (default-on), retention sweep (default-off), LC-205 (email-ingress webhooks). - **Added**: LC-77 / LC-77-REPLY (email ingress + reply), LC-207 (avatar diagnostics), LC-393 (server-side STT), LC-396 (transcript summaries). ## On merge `.forgejo/workflows/create-release.yml` tags the merge commit `v0.1.0` and creates the Forgejo Release (auto `git log` body). The `v*` tag then fires: - `build-oci-image.yml` -> pushes `dev.a8n.run/a8n-tools-private/lets-chat:v0.1.0` (+ `latest`). - `publish-release.yml` -> desktop Linux/Windows binaries + signed `latest.json` to Generic Packages. **Precondition:** `DESKTOP_UPDATE_SIGNING_KEY` secret + `DESKTOP_UPDATE_PUBLIC_KEY` variable must be provisioned (per `docs/desktop-update-signing.md`) or the publish job fails closed. Pairs with docker PR #139: once `lets-chat:v0.1.0` is in the registry, the nc-01 `lets-chat-psa` pin moves off `:latest` to `:v0.1.0`.
Release v0.1.0
All checks were successful
check-secrets / Nosey parker (push) Successful in 6s
Details
check-secrets / TruffleHog (push) Successful in 9s
Details
check-secrets / Kingfisher (push) Successful in 10s
Details
check-secrets / Nosey parker (pull_request) Successful in 7s
Details
check-secrets / Kingfisher (pull_request) Successful in 9s
Details
check-secrets / TruffleHog (pull_request) Successful in 11s
Details
Check / clippy + fmt + tests (pull_request) Successful in 5m40s
Details
Create release / Create release from merged PR (pull_request) Successful in 6s
Details
2dcfd05670 
First tagged release. Cargo.toml workspace version is already the 0.1.0 seed, so this commit carries no version bump (the create-release recipe bumps FROM the current version and cannot emit the seed value for the first tag); the change is the curated CHANGELOG.

Folds the Pre-release seed (snapshot 2026-05-30) and the post-snapshot operator-action commits (LC-22 Bunyip-only auth, LC-206 image-decode limits, LC-210 signed desktop updates, LC-393 server-side STT, LC-396 transcript summaries) into a single ## [v0.1.0] section.

On merge, create-release.yml tags v0.1.0 + creates the Forgejo Release; build-oci-image.yml pushes lets-chat:v0.1.0 (+ latest); publish-release.yml ships the desktop artifacts.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: nrupard <natrsmith11@gmail.com>
nrupard deleted branch release/v0.1.0 2026-06-24 17:31:11 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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!440
No description provided.