Skip to content

docs: sync version references across README, RELEASE, and CHANGELOG#238

Open
cobusgreyling wants to merge 1 commit into
mainfrom
docs/version-doc-drift
Open

docs: sync version references across README, RELEASE, and CHANGELOG#238
cobusgreyling wants to merge 1 commit into
mainfrom
docs/version-doc-drift

Conversation

@cobusgreyling

Copy link
Copy Markdown
Owner

Summary

Fixes version/doc drift between shipped npm packages and repo documentation.

  • README: loop-audit v1.6, loop-init v1.3, link to Discussion Community week — loop-worktree npm, MCP quickstart, tool appendices #219, "All npm CLIs" wording
  • docs/RELEASE.md: expand from 6 → 8 packages (loop-worktree, goal-audit), current tag examples and verify commands
  • loop-audit CHANGELOG: add 1.6.0 (governance scoring) and 1.5.3 (contributor CTA) entries
  • loop-audit README: signals section v1.6+
  • loop-audit package-lock.json: sync to 1.6.0
  • RELEASE_NOTES_DRAFT.md: loop-audit 1.6.0, CI Sweeper story, updated package table
  • STATE.md: link to RELEASE.md instead of hardcoded tag list

Test plan

  • Grep confirms no stale v1.5 / v1.2 / six public references in docs
  • tools/loop-audit/package-lock.json version matches package.json (1.6.0)

Align docs with shipped npm versions (loop-audit 1.6.0, loop-init 1.3.3),
add loop-worktree and goal-audit to the release playbook, and refresh
RELEASE_NOTES_DRAFT with governance scoring and CI Sweeper story.
@github-actions

github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Thanks @cobusgreyling for contributing a docs improvement — visible, reviewable PRs like this grow the reference for everyone.

What happens next

  • Maintainer aims for same-day review on story, adopter, and scoped docs/example PRs (CONTRIBUTING.md).
  • good first issue PRs: comment on the linked issue so we can assign and close on merge.

More ways to help

— loop-engineering maintainers

@github-actions

github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Loop Readiness Audit

Score: 100/100 (L3)

Strong loop readiness — good candidate for L3 with explicit gates.

No suggestions — looking good.

Posted by audit.yml · loop-audit docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant