docs: move (since vNEXT) tags out of markdown headings - #697
Merged
Conversation
Moves the (since vNEXT) tags out of four section headings -- the workspace-workflow.md load-types section plus three gotchas.md entries from #695, #692 and #681 -- onto each section's first body line, so the heading anchor slugs stay stable when the placeholder resolves at release. Same fix pattern as PR #691; the serve --config-dir heading is changed byte-identically to that branch so the two merge cleanly in either order.
padak
added a commit
that referenced
this pull request
Aug 25, 2026
CONTRIBUTING.md release step 4 keeps version tags off headings: resolving the placeholder changes the generated anchor slug and breaks inbound links. PR #697 did this pass, but #694 and #696 landed their headings around the same time and fell outside its grep. - gotchas.md: two headings, tag moved to the section's first body line - sync-workflow.md: heading reworded to 'Migrating a legacy sync tree', with the version stated on a body line No inbound links reference the affected anchors (verified by grep).
This was referenced Aug 25, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
CONTRIBUTING.md forbids version tags in markdown headings: the anchor slug is derived from the full heading text, so when the release PR resolves
vNEXTto the real version, the slug changes and every inbound link to that section silently breaks (this bit 0.90.0).What
Moves the
(since vNEXT, ...)tag from four headings onto each section's first body line as*(since vNEXT, ...)*, matching the pattern PR #691 applied to gotchas.md:plugins/kbagent/skills/kbagent/references/workspace-workflow.md-- "Load types: clone / copy / view" (workspace load: use zero-copy CLONE when eligible, guard huge COPYs, fix fire-and-forget timeout #687)plugins/kbagent/skills/kbagent/references/gotchas.md-- three headings introduced by feat(notification): write path — create/delete/replace-recipient subscriptions (#690) #695, feat(workspace): zero-copy CLONE by default, large-COPY guard, fire-and-forget timeout fix #692 and serve: honor the root-level --config-dir, and fix two stale permissions comments #681 (found viagrep -rn '^##.*vNEXT' plugins/)The
serve --config-dirheading fix is byte-identical to the one on the open PR #691 branch, so the two merge cleanly in either order.Verified: no
^##.*vNEXTheadings remain anywhere underplugins/, and no inbound links reference the changed anchor slugs.Docs-only: no version bump, no changelog entry (per the release process -- feature/docs PRs never bump).