Raise the hosted plugin floor to 0.5.2, and record that 0.4.1 never was #333

Merged
cruelacid merged 1 commit from worktree-nec-202-floor-0-5-2 into main 2026-10-30 22:53:24 +00:00
Owner

The hosted service has its first outside user, and both of their desktops run 0.5.2. A 0.6.0 floor would stop their sync today, so the floor moves to 0.5.2 instead. Every current connection runs 0.5.2, and the main run of ff8bc752 last tested the production server against it. docs/releasing.md records this as a third exception to the four-week rule, with the reading it rested on. The 0.6.0 raise waits until 27 November at the earliest.

The 0.4.1 floor recorded on 2 October was never applied: eu1's env and the running container both still said 0.3.0. This corrects the docs that claimed 0.4.1 (releasing.md, sync-limitations.md, deploy/SETUP.md, deploy/shard/nectenda.env.example). releasing.md now says to read the running container's env after any raise.

With CI's previous-release pass now on 0.6.0, the 0.5.2 floor is admitted but not tested. NEC-369 tracks that.

The production env change is applied by hand on eu1. This PR changes only the record.

Verified locally: deploy vitest, 223/223. That includes the floor-consistency test, which caught the env example and a present-tense 0.4.1 sentence before the push.

Task: NEC-202

Changelog

NONE

🤖 Generated with Claude Code

https://claude.ai/code/session_01P5JXvAgQ27c4dMFDB2Wu5B

The hosted service has its first outside user, and both of their desktops run 0.5.2. A 0.6.0 floor would stop their sync today, so the floor moves to 0.5.2 instead. Every current connection runs 0.5.2, and the `main` run of ff8bc752 last tested the production server against it. `docs/releasing.md` records this as a third exception to the four-week rule, with the reading it rested on. The 0.6.0 raise waits until 27 November at the earliest. The 0.4.1 floor recorded on 2 October was never applied: eu1's env and the running container both still said 0.3.0. This corrects the docs that claimed 0.4.1 (`releasing.md`, `sync-limitations.md`, `deploy/SETUP.md`, `deploy/shard/nectenda.env.example`). `releasing.md` now says to read the running container's env after any raise. With CI's previous-release pass now on 0.6.0, the 0.5.2 floor is admitted but not tested. NEC-369 tracks that. The production env change is applied by hand on eu1. This PR changes only the record. Verified locally: `deploy` vitest, 223/223. That includes the floor-consistency test, which caught the env example and a present-tense 0.4.1 sentence before the push. Task: NEC-202 ## Changelog NONE 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01P5JXvAgQ27c4dMFDB2Wu5B
Raise the hosted plugin floor to 0.5.2, and record that 0.4.1 never was
All checks were successful
Release note / release-note (pull_request) Successful in 19s
CI / build (pull_request) Successful in 6m2s
CI / e2e (pull_request) Successful in 15m17s
CI / promote (pull_request) Has been skipped
CI / build (push) Successful in 6m28s
CI / e2e (push) Successful in 15m18s
CI / promote (push) Successful in 32s
c427941a57
The hosted service has its first outside user, on 0.5.2. A 0.6.0 floor
would stop their sync today, so the floor goes to 0.5.2: what every
connection runs, and what the production server was last tested against.
That is a third exception to the four weeks, decided by the user and
recorded with the reading it rested on. The 0.6.0 raise waits until
27 November at the earliest.

The 0.4.1 floor recorded on 2 October was never applied. The hosts'
env and the running container still said 0.3.0, so the docs claiming
0.4.1 are corrected, and releasing.md now says to read the running
container's environment after a raise. With N-1 now 0.6.0, the floor is
admitted but untested, which is NEC-369.

Task: NEC-202

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01P5JXvAgQ27c4dMFDB2Wu5B
Sign in to join this conversation.
No reviewers
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
Nectenda/nectenda!333
No description provided.