Nectenda/nectenda

Watch

Fork 0

NEC-186: Raise the plugin floor to the release that merges bases #257

Merged

nectenda-agent merged 2 commits from worktree-nec-186-raise-the-plugin-floor-to-the-release-th into main

2026-10-02 20:29:20 +01:00

nectenda-agent commented

2026-10-02 18:43:18 +01:00

Collaborator

Task: NEC-186 — https://projectron.nerchure.com/tasks/194

Raise the hosted plugin floor (MIN_PLUGIN_VERSION) to 0.4.1, so no client older than the release that merges bases (NEC-24) and per-property frontmatter (NEC-26) can connect alongside one that does. 0.4.1 rather than 0.4.0 because CI's previous-release pass runs the newest public tag; a 0.4.0 floor would admit a version no pass runs. releasing.md records the second exception to the four weeks and states the floor in one sentence; two tests hold the shard env example, SETUP.md and every 'floor is X' in releasing.md and sync-limitations.md to it. Production (eu1's nectenda.env and fleet.env) is changed by the user after this merges.

Spec: docs/changes/NEC-186-plugin-floor-bases/spec.md

Changelog

NONE

Task: NEC-186 — https://projectron.nerchure.com/tasks/194 Raise the hosted plugin floor (MIN_PLUGIN_VERSION) to 0.4.1, so no client older than the release that merges bases (NEC-24) and per-property frontmatter (NEC-26) can connect alongside one that does. 0.4.1 rather than 0.4.0 because CI's previous-release pass runs the newest public tag; a 0.4.0 floor would admit a version no pass runs. releasing.md records the second exception to the four weeks and states the floor in one sentence; two tests hold the shard env example, SETUP.md and every 'floor is X' in releasing.md and sync-limitations.md to it. Production (eu1's nectenda.env and fleet.env) is changed by the user after this merges. Spec: `docs/changes/NEC-186-plugin-floor-bases/spec.md` ## Changelog NONE

nectenda-agent added the

area:server

label

2026-10-02 18:43:18 +01:00

nectenda-agent added 2 commits

2026-10-02 18:43:18 +01:00

Raise the hosted plugin floor to 0.4.1, the release that merges bases and properties 9a02024eb9

0.4.0 is the first release to merge .base files (NEC-24) and a note's
properties per property (NEC-26). An older build syncs a base as an
attachment and edits properties as text, and only a floor closes that.
The floor is 0.4.1 rather than 0.4.0 because CI's previous-release pass
runs the newest public tag; 0.4.0 would be admitted and never run.

releasing.md records this as a second, separately decided exception to the
four weeks, and states the current floor in one sentence. A new test holds
the shard env example and SETUP.md to it. The N-1 paragraph no longer says
the floor is 0, which it had said since NEC-158 raised it.

Task: NEC-186

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NxSpVoaRCTg2AitFNVtCqF

Hold every statement of the floor to the current one, and fix the one review found

Release note / release-note (pull_request) Successful in 21s

Details

CI / build (pull_request) Successful in 6m4s

Details

CI / e2e (pull_request) Successful in 8m18s

Details

CI / promote (pull_request) Has been skipped

Details

CI / build (push) Successful in 5m33s

Details

CI / e2e (push) Successful in 7m57s

Details

CI / promote (push) Successful in 33s

Details

f401e315b9

Review found sync-limitations.md still saying the hosted service's floor
is 0.3.0, beside the new paragraph saying 0.4.1. The first test held only
the env example and SETUP.md to releasing.md's sentence, and missed this
because the sentence breaks across a line. A second test now requires
every present-tense "floor is X" in releasing.md and sync-limitations.md,
in either case and across a line break, to be the current floor; past
values say "became". provision-shard.sh no longer names 0.3.0 either.

Task: NEC-186

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NxSpVoaRCTg2AitFNVtCqF

nectenda-agent merged commit f401e315b9 into main

2026-10-02 20:29:20 +01:00

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!257

No description provided.

Rows
Columns