Nectenda/nectenda
Watch
1
0
Fork
You've already forked nectenda
 0
Code Issues 1 Pull requests Projects 5 Releases Packages Wiki Activity Actions

NEC-109: Two places still count the toolchain pin sites, and both are wrong #174

Merged
nectenda-agent merged 1 commit from worktree-nec-109-two-places-still-count-the-toolchain-pin into main 2026-09-25 17:12:51 +01:00
Conversation 0 Commits 1 Files changed 3 +39 -7
nectenda-agent commented 2026-09-25 16:58:57 +01:00
Collaborator
Copy link

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

CLAUDE.md and the toolchain rule's description in renovate.json both said node-version is pinned in three workflows; it is five (ci, deploy-site, checkpoint-soak, release-note, and the obsidian-e2e composite action). Both now say 'node-version in every workflow that sets up Node', the wording deploy/UPGRADES.md has used since NEC-107, and the Dockerfile counts go too, so the passage people read to find every site a toolchain bump must reach cannot go stale when a workflow or stage is added. The toolchain group matches by manager, not filename, so coverage was never affected. renovate.json validates with the current renovate-config-validator; only the description string changed.

Spec: docs/changes/NEC-109-toolchain-pin-count/spec.md

Changelog

NONE

Task: NEC-109 — https://projectron.nerchure.com/tasks/109 CLAUDE.md and the toolchain rule's description in renovate.json both said node-version is pinned in three workflows; it is five (ci, deploy-site, checkpoint-soak, release-note, and the obsidian-e2e composite action). Both now say 'node-version in every workflow that sets up Node', the wording deploy/UPGRADES.md has used since NEC-107, and the Dockerfile counts go too, so the passage people read to find every site a toolchain bump must reach cannot go stale when a workflow or stage is added. The toolchain group matches by manager, not filename, so coverage was never affected. renovate.json validates with the current renovate-config-validator; only the description string changed. Spec: `docs/changes/NEC-109-toolchain-pin-count/spec.md` ## Changelog NONE
Stop counting the toolchain pin sites
All checks were successful
Release note / release-note (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 5m14s
Details
CI / e2e (pull_request) Successful in 5m30s
Details
CI / promote (pull_request) Has been skipped
Details
2f7f933182 
CLAUDE.md and the toolchain rule in renovate.json both said node-version
is pinned in three workflows; it is five. Describe the sites the way
deploy/UPGRADES.md already does since NEC-107 — "every workflow that sets
up Node" — so the sentence cannot go stale when a workflow is added. The
Dockerfile counts are right today but drop for the same reason.

Task: NEC-109

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DYWLyKb3EA6tME9gDG6ybF
cruelacid force-pushed worktree-nec-109-two-places-still-count-the-toolchain-pin from 2f7f933182
All checks were successful
Release note / release-note (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 5m14s
Details
CI / e2e (pull_request) Successful in 5m30s
Details
CI / promote (pull_request) Has been skipped
Details
to 61137b12f1
All checks were successful
Release note / release-note (pull_request) Successful in 12s
Details
CI / build (pull_request) Successful in 4m33s
Details
CI / e2e (pull_request) Successful in 5m12s
Details
CI / promote (pull_request) Has been skipped
Details
CI / build (push) Successful in 4m45s
Details
CI / e2e (push) Successful in 5m10s
Details
CI / promote (push) Successful in 30s
Details
2026-09-25 17:06:50 +01:00 Compare
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
area:docs
docs/

  
area:identity
packages/identity

  
area:ops
deploy/, CI, hosting

  
area:plugin
packages/plugin

  
area:server
packages/server

  
channel:community
Obsidian forum, Obsidian Discord, Reddit

  
channel:direct
Cold outreach to named firms

  
channel:owned
nectenda.com pages, the feedback board

  
channel:press
Hacker News, newsletters, outlets, YouTube creators

  
channel:social
Bluesky, Mastodon, X, YouTube accounts

  
e2ee-constrained
End-to-end encryption changes the shape of the answer

  
gate:at-ga
Held until Gates A-C close and terms/privacy leave DRAFT

  
gate:pre-ga
Safe to do before the launch gates close

  
marketing
Reach and positioning; work published off nectenda.com

  
parity
Relay feature-parity programme

  
relay:absent
4 - Not supported, not requested, not planned at Relay

  
relay:planned
2 - On Relay's roadmap (Active/Planned) or has an open PR

  
relay:requested
3 - Asked for by Relay users or under 'Considering'; not committed

  
relay:supported
1 - Relay ships this today

  
risk:additive
New message type, table or column; backward compatible

  
risk:contract
Changes something existing accounts or stored data depend on

  
risk:none
Client-only; the server is untouched

  
usability
How the product is understood and learned, not what it does

No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
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!174
No description provided.