Skip to content

Releases

Repo Standards 11.0.1

Choose a tag to compare

@github-actions github-actions released this 11 Nov 18:54
6f7da1f

Exact update: nothing is needed beyond reviewing and committing the update.

Fixes

  • Fixed contextual update continuation from completed CLI 10 adoptions using supported lock/v1 records. CLI 11 now preserves status and accepts the remaining contextual answers through completion instead of failing with STATE_INTEGRITY. Status after an abandoned update also retains its explanation and in-place recovery guidance. (#500; fixes #498)

No breaking changes or additional action outside adoption. The existing supported-format and integrity checks remain in force.

This patch follows the release decision on #498. Contextual published-update acceptance follow-up #499 is separate from this release.

Verification: Release and public acceptance run 43068921911 validated the released commit on Linux and macOS under Node.js 24 and 26, then passed public npm/bootstrap installation, the one-command update from CLI 11.0.0 with ready-to-commit status, and standalone authoring-skill installation in all four OS/Node cells. All four retained adopter-action lines match the release-note opening. Fresh Linux direct-tag installation of the unchanged adoption-entry skill and dated skills.sh directory/find observations passed. v8.0.0 remains its first containing tag. No fresh macOS adoption-entry installation was collected because no authorized exercise facility is available; this limitation is separate from the successful macOS CLI/update/author checks above, under the recorded 11.0.1 scope decision. #483 remains with triage. No new real-agent journey is required by #498.

Repo Standards 11.0.0

Choose a tag to compare

@github-actions github-actions released this 10 Nov 21:34
df652b5

Exact update: nothing is needed beyond reviewing and committing the update.

What changed

Choose where checks run independently of the hosting platform. Profiles offer check-locations from github, runner, and self-reported; declarations can filter on those locations. Select one with --checks or the answers-file checks value. Platform and location filters compose before discovery, scope, installation, rules, checks, and fixes.

The selected location is retained through inspection identities, confirmation, adoption records, script requests, offline reapplication, status, and updates. A sole offered location is automatic; profiles omitting the key offer github. Supported recorded choices carry forward, while a headless update stops before writes if its choice is no longer offered.

check now preserves process-group inspection failures and their diagnostics instead of losing them during result rendering. When the required ps tool is missing, the diagnostic retains the remedy to install it and rerun the command (#491, #492).

Release validation also includes bounded browser-fixture teardown, fixing the macOS Node 26 failure and stall that stopped the first unpublished release attempt (#486, #489).

Breaking changes and migration

  • Format-aware consumers must accept state v8, lock v2, scope-history v7, run v8, inspection/status v10, check v3, answers v2, and adopt v3. Regenerate answers templates for the new protocol.
  • Supported previous committed records remain readable. Legacy selections without checks retain github behavior; the next completed adoption records it explicitly.
  • Finish or abandon an earlier active run with the pinned CLI that started it before inspecting with CLI 11.
  • Standards authors using the optional check-locations keys must require a compatible CLI with an open-ended minimum of >=11.0.0.

There is no additional adopter action outside adoption for this release. The opening action is the pre-dispatch prediction from CLI 11 inspection of the committed CLI 10.0.1/public learning-source v3.0.0 work baseline; published acceptance must confirm the completed update reports the same action.

Parent contract: #480, implemented by #481. Repo Canon's declarations and adopter updates are separate follow-up work.

Verification (2026-11-10): Release and public verification ran in workflow 42890777238. All four Linux/macOS × Node.js 24/26 validation and public CLI/author-skill acceptance cells passed, including one-command 10.0.1 → 11.0.0 updates ready to commit; every derived adopter-action line matches the opening. npm integrity, the resolved tag and all four assets match the workflow bundle. Fresh Linux adoption-entry skill installation passed; fresh macOS adoption-entry installation was not collected under the run-specific scope recorded in #483.

Repo Standards 10.0.1

Choose a tag to compare

@github-actions github-actions released this 08 Nov 20:19
bcbb749

Exact update: nothing is needed beyond reviewing and committing the update.

Fixes

  • Allow adoption in projects with initialized, recursively clean submodules at their recorded commits. Preserve submodule boundaries; initialization and repair remain manual (#475, #477).
  • Reject records missing their required format markers and clarify readiness through recorded change-set paths.
  • Refresh the packaged usage guides, authoring references, and npm metadata.

No breaking changes or actions outside adoption are required. This patch contains the fix for #475; no separate parent specification or new real-agent journey applies.

Verification: Release and public acceptance workflow run 42512111593 passed on Linux and macOS under Node.js 24 and 26. All four public CLI installation/update gates and standalone authoring-skill checks passed; their derived adopter-action lines match the opening above.

Repository Standards 10.0.0

Choose a tag to compare

@github-actions github-actions released this 22 Oct 21:50
8ae21e7

Exact update: nothing is needed beyond reviewing and committing the update.

Actions outside adoption

The line above is the one the CLI derives for updating the public learning
source's committed 9.0.0 adoption. inspect and adopt derive the line for
your own project. To update a committed 9.0.0 adoption, run the 10.0.0 CLI's
adopt in the project, such as
npx --yes @lutzseverino/repo-standards@10.0.0 adopt --json. Check each item
below only if it applies to you:

  • Unfinished 9.0.0 run. Finish it (resume) or end it (abandon) with
    the pinned 9.0.0 CLI before you update. 10.0.0 stops on an active
    repo-standards/run/v6 record with RETIRED_RUN.
  • Changes an abandoned 9.0.0 run left uncommitted. Finish them with
    9.0.0, whose adopt adopts again in place, or commit or discard them through
    your normal workflow, before you update. 10.0.0 does not adopt again in place
    over another CLI's run. Archived 9.0.0 run reports in Git's
    repo-standards-reports/ directory stay where they are and no longer block
    the update.
  • Hand-made .repo-standards/.gitattributes. An unrecorded file at that
    path blocks the update with STATE_INTEGRITY, and is left untouched. It
    already blocks on 9.0.0. Remove it, and the update writes the owned file.
  • Scripts that read product formats. Accept the new identifiers listed
    under Breaking changes.
  • Hand-written Impact/Migration on adoption pull requests. Drop them. The
    adoption record (status --summary) now ends with ## Impact and
    ## Migration itself.
  • Source authors. A source that uses adopter-action, a profile's
    platforms, a declaration's platform, or optional: true must raise
    requires.repo-standards to >=10.0.0. Earlier CLIs reject these fields
    with UNKNOWN_FIELD.

Repository Standards 10.0.0 delivers the Repository Standards side of
#281: updates fast
and low-churn enough that frequent releases don't burden adopters. There is no
stability promise. Every release, breaking ones included, must update from the
previous release in one adopt without hand edits, and published acceptance
now checks that path with the public learning source. See the
release policy.

What changed

  • Recorded answers carry forward
    (#327,
    #338). An update
    reuses a recorded answer when nothing it depends on has changed:

    • a scope answer, when the guidance, rules and fresh discovery draft are
      identical and its paths still exist;
    • a remote-setup deferral, while the same probe still reports not ready;
    • an assessment, when the rules and scoped files are unchanged since the
      last complete adoption, including after the run's fixes.

    Any other answer comes back prefilled and still missing. A confirmation, a
    fix: overwrite answer and a declined-overwrite deferral are never reused.
    status, run records and the adoption record list every reused answer
    (ADR 0024).

  • adopt starts when nothing is open
    (#328,
    #340). This
    applies with or without an answers file. When the fresh inspection needs no
    confirmation and has no open question, blocker or resolve answer, adopt
    starts the run in the same invocation. A stale inspection answer no longer
    stops a start that needs no confirmation. Terminal sessions still ask before
    every start
    (ADR 0025).

  • adopt --headless
    (#329,
    #341). This
    updates an established adoption without asking anyone. It uses the recorded
    source, profile and platform, and the newest stable release or
    --standards-version. It answers only with reused answers and defers every
    remote setup, ready or not. It exits 0 when complete. Otherwise it exits 1
    with its open questions, either before any write or with the run active, for
    adopt --answers to finish. It rejects a source, --answers, --profile
    and --platform (exit 2).

  • Update action
    (#330,
    #342).
    action.yml at the repository root is an opt-in composite GitHub action. It
    keeps one rolling update pull request current. When an update needs agent
    work, it opens one rolling issue instead. It takes a token input (a GitHub
    App token is recommended, with GITHUB_TOKEN as the fallback) and an
    optional agent-command. It always moves both pins to the newest releases.
    10.0.0 is the first release tag that contains it. Pin it by that tag's full
    commit SHA
    (automated updates,
    ADR 0026).

  • What adopters must do
    (#331,
    #343). The CLI
    derives one adopter-action line from each update. The line names the update
    class, the contextual work the run asks for, and pending remote setup. It
    appears in inspect (adopterAction) and in the adoption record's new
    ## Impact / ## Migration sections (status --json impact). A source
    can add one plain-text adopter-action line in standards.yaml, only for
    actions outside adoption. outdated lists that author-written line for each
    newer standards release (adopterActions).

  • Hosting platform inside each profile
    (#300,
    #344). A profile
    may list platforms, which defaults to [github], and a declaration may set
    platform. adopt, inspect and start take --platform. A
    single-platform profile selects its platform without asking. Otherwise
    adopt proposes the platform of the origin remote. The platform is recorded
    in the selection and the lock; a lock written by an earlier CLI reads as
    github. It also appears in summaries and the check line, and in
    operation and discovery script input. GitHub remains the only supported
    platform. New diagnostics: UNKNOWN_PLATFORM, PLATFORM_REQUIRED,
    UNSUPPORTED_PLATFORM, EMPTY_PLATFORMS
    (ADR 0027).

  • Optional discovery declarations may have no scope
    (#325,
    #335). A
    discovery declaration marked optional: true can be confirmed with
    "noScope": true. No scope is different from an empty scope: the
    declaration installs no rules and runs no checks or fixes. scope/v2 keeps
    its version
    (ADR 0023).

  • Generated product state
    (#323,
    #324). Every
    installation now records .repo-standards/.gitattributes, which contains
    ** linguist-generated. GitHub collapses .repo-standards/ diffs and leaves
    them out of language statistics. The first 10.0.0 run on a 9.0.0 adoption
    adds this file.

  • Release reads through Postern
    (#299,
    #339). Source
    releases and exact tags are read through the pinned
    @lutzseverino/postern 1.0.0, a new runtime dependency. Release lists now
    read every page, so outdated and discovery find a stable release beyond
    the first 100 entries.

  • Terminal scope fix
    (#336,
    #348). Omitting a
    drafted file that does not exist no longer creates an exclusion without
    evidence (INVALID_SCOPE).

  • Release gate and policy
    (#332,
    #355). Published
    acceptance adopts the newest public learning-source release with the newest
    earlier stable CLI and commits that baseline. It then requires one
    unanswered adopt --json of the released CLI to complete ready to commit.
    The README and usage documentation state the release policy.

  • Documentation. Optional author-input keys may keep their format version
    (#337,
    #351). The
    installation examples name learning-source release v3.0.0.

Breaking changes

  • adopt without an answers file is no longer read-only (#340).
    • Impact: when nothing is open, adopt --json starts the run and writes
      to the project. adopt/v2 and answers/v1 keep their question shapes.
    • Migration: callers that used the template as a read-only preview use
      inspect --json instead.
  • Raised formats (#338, #340, #...
Read more

Repository Standards 9.0.0

Choose a tag to compare

@github-actions github-actions released this 19 Oct 11:07
cdcb9bc

Repository Standards 9.0.0 implements #312 in #320: recover a stopped adoption run in the same checkout, preserving its work. This major release changes successful abandon exit status.

What changed

  • Correct scope in place. For SCOPE_INCOMPLETE, ASSESSMENT_SCOPE or ASSESSMENT_BLOCKED, adopt exposes the discovered declarations' scope:<declaration> answers with the confirmed scope. Change the relevant answer and invoke adopt --answers <file> again; terminal users can choose to change scope from the incomplete-run menu. The CLI archives the old run with abandoned: true and a REPLACED: reason, inspects the same selection with the revised scope, asks for the new inspection identity, and starts a replacement run over the preserved changes. This is a new run: the active run's confirmed scope is never amended. Agents may correct this Git-recoverable scope answer without another approval.
  • Adopt again after abandonment. abandon archives the saved installation and last observation alongside the report. A later adopt in that checkout, or matching inspect/start, can adopt over exactly those recorded changes. The runtime is retained, repeat-safe fixes rerun, and preserved contextual work needs renewed assessments within the new scope. The replacement's change set and adoption record cover all changes relative to the first run's starting HEAD, preserving installation/agent attribution; replaced-run evidence remains in the archive. An update reads its previous complete adoption from that starting commit. status, check and rules diagnostics now point to recovery when abandoned candidate product state is incomplete.
  • Defer a declined overwrite. After a maintainer declines a fix's confirmation-required overwrite, answer defer to fix:<declaration>/<id>, choose defer in the terminal's overwrite/defer/stop prompt, or use resume --defer. The whole fix is deferred for that run and the remaining fixes continue. Deferral and its reason appear in durable state, status and the adoption record's Operations table. Every later run invokes the fix again, initially without overwrite permission. This reuses the existing deferral record and changes no script request/result format. Confirmation of a remote overwrite still belongs to the maintainer.
  • Documented recovery contract. ADR 0022 amends ADR 0009. The glossary, architecture, adoption/inspection guides and assessment/script protocols describe replacement runs and preserved changes. Regression tests cover answers-file and terminal recovery, initial adoption and updates, evidence attribution, rejection of unrecorded changes, deferral and exit statuses.

Breaking changes

  • Scripts and CI checking abandon exit status: successful abandon and abandon --json now exit 0, previously 1. Update wrappers and assertions to accept 0 as successful abandonment and keep treating 1 as refusal/failure, such as NO_ACTIVE_RUN or a live author process. Remove inversions or special cases that treated exit 1 as successful abandonment. The returned report still has outcome: "incomplete" and abandoned: true: abandonment succeeds without asserting successful adoption. Use those fields when distinguishing abandonment from completed adoption; do not map exit 0 to adoption completion.
  • Agents and maintainers using abandon-and-restart: replace the old instruction to abandon, commit/discard and start in a fresh clone with scope-answer recovery in the current checkout. For the three scope stops above, edit the returned scope:<declaration> answer, rerun adopt --answers <file>, review the fresh inspection and provide its identity, then reassess preserved contextual work. If already abandoned under this release, run adopt in the same checkout to inspect and start again over the preserved work. Keep the same exact CLI, source, standards version and profile, unchanged HEAD/index, verified installation and recorded uncommitted state. New unrecorded changes still block with DIRTY_PROJECT; stop and tell the maintainer rather than silently taking them into the run. Fixes execute again, so account for their repeat-safe rerun. Restoring each offending path remains an option for ASSESSMENT_SCOPE when the original scope is correct.
  • Automation reading fix questions and deferrals: accept the additional defer answer and terminal choice, and display/report deferred entries for declined fixes as well as unready remote setup. Do not interpret a deferred fix as executed successfully or permanently waived. Use resume --defer alone, without --retry, --assessment or --confirmed, only at a confirmation-required fix stop after the maintainer declines. Continue requiring the inspection identity for confirmed overwrites.

Upgrade and recovery limits

  • Exact CLI pins, installed product skills and copied standalone bootstraps do not update automatically. Finish or reconcile an existing 8.1.0 run with its pinned CLI before changing versions; 9.0.0 does not take over a run pinned to another CLI. From a clean, committed project, acquire npx --yes @lutzseverino/repo-standards@9.0.0 adopt --json; retain the current standards tag if updating only the CLI. Follow the returned inspection and confirmation steps and review the resulting uncommitted, unstaged changes. In the product checkout, acquire the candidate externally as the adoption guide documents.
  • Recovery requires the new archived installation/observation context. A pre-9.0.0 abandonment did not save it; a run abandoned before installation completed, or missing/damaged saved context, cannot use this recovery path. Reconcile preserved changes through the project's normal workflow and use a fresh inspection from a clean, committed checkout when recovery prerequisites are unavailable. Choosing another CLI, source, standards version or profile also requires the ordinary clean start.
  • No persistent record-format conversion or source/script protocol migration is introduced. Stable Node.js 24 and 26 remain supported. The package, standalone authoring guide, bootstrap examples, current-CLI documentation and both standalone skill installation commands now name 9.0.0 / v9.0.0. The adoption entry skill's historical first containing public tag remains v8.0.0.

Repository Standards 8.1.0

Choose a tag to compare

@github-actions github-actions released this 19 Oct 07:15
bff7b18

Repository Standards 8.1.0 is a minor release implementing #310, #311 and #315, plus a repository reviewer fix. No breaking migration is required.

What changed

  • Recover a run after undoing an out-of-scope change (#317, #310). Restoring a file or boundary directory to its state before the earliest interval that changed it reconciles its scope or check-mutation violation. Remove a file or directory the run added, or restore edited content and directory state, then follow the printed continuation/retry steps. The same run can continue without abandonment. Unrestored paths still block; an operation that writes them again fails again. Historical intervals retain their original changes and violations. Contextual changedPaths now reflects net agent changes: a path restored to its pre-run state has nothing to attribute, while a still-changed path needs assessment. Recovery messages name the paths and restoration action; all offending assessment paths are reported together. Confirmed scope and exact-content protections are unchanged.
  • Fewer maintainer round trips for adopting agents (#314, #311; ADR 0021). The README and entry skill use npx --yes and adopt --json, avoiding npm and terminal prompts. Agents select the proposed newest stable standards release unless the request names another, choose a profile from descriptions and repository evidence, settle concrete scope membership with reasons, review the inspection and start, confirm reviewed discarded edits recoverable from Git, defer remote setup that is not ready, and retry interrupted/incomplete repeat-safe work as directed. Record decisions, reasons, discarded-edit diffs/current content, deferrals and retries in the handoff. Ask when the profile remains unsettled and before a fix overwrites a remote setting. Abandonment still needs the maintainer's instruction. Leave project files unedited before start; a new run still requires clean, committed Git state. Completion still leaves reviewed changes uncommitted and unstaged. Record the ready-to-commit verdict before committing, since it describes uncommitted changes. Human terminal choices remain human choices.
  • Checks can distinguish adoption runs from standalone checking (#316, #315). Every check's repo-standards/operation/v2 stdin request gains top-level invocation: "run" for adoption/update execution, including checks-only continuation after an accepted assessment and resume --retry; "check" when invoked by repo-standards check, including its contextual-check route. Fixes and remote readiness probes do not receive the field. Authors can use it to apply scope-membership rules only during a run while keeping other rules active between runs. This does not expand frozen scope, change check mutation enforcement, or automatically change a source's scripts.

Release documentation and repository maintenance

  • Reviewer completion detection (#313). The repository's configured reviewer regex matches the Code Review completion row, avoiding another task row's completion timestamp/SHA. This is a repository development configuration change, not behavior installed into adopting projects by the CLI.
  • Matching release material. Package, authoring skill acquisition guide, CLI examples and installation commands name 8.1.0. Both standalone skill commands target v8.1.0. The adoption entry skill's first containing public tag is v8.0.0, verified to contain its two files; the README, installation guide and release procedure no longer describe it as unreleased. Direct skill installation remains separate from npm installation and adoption.

Impact and migration

  • Adopting agents: follow the running CLI's instructions and record your Git-recoverable decisions in the handoff. --confirmed for discarded edits now means the agent reviewed and confirmed them; it still binds the inspected identity. A remote-setting overwrite requires the maintainer's confirmation. Keep review artifacts outside the project, preserve the clean-tree start requirement, and hand completed changes back uncommitted and unstaged. For a scope violation, undo each named path in place and follow the recovery instructions; changing the confirmed scope still requires a new run.
  • Script/source authors: ignore request fields your script does not use. Read invocation only for checks. Older CLIs omit it; handle absence explicitly, for example const invocation = request.invocation ?? "run"; to preserve adoption checks with older clients. If the script requires the field to function correctly, declare and test a CLI compatibility minimum of >=8.1.0 instead. Keep run-only scope coverage conditional on invocation === "run", and continue ordinary content checks for "check". No source, result, assessment or persistent-state format conversion is introduced.
  • Existing projects: exact CLI pins, installed system skills and copied standalone bootstraps do not update automatically. Finish or abandon an active run with its pinned CLI before changing versions. From a clean, committed project, use npx --yes @lutzseverino/repo-standards@8.1.0 adopt --json; retain the current standards tag to update only the CLI, and review the resulting changes. Replace copied bootstraps and independently installed skills deliberately with matching release material. In the product checkout, acquire the candidate externally as documented.
  • Stable Node.js 24 and 26 remain supported; contributor/publisher defaults remain pinned Node.js 24 and pnpm. No command-default or report-format migration is required.

Repository Standards 8.0.0

Choose a tag to compare

@github-actions github-actions released this 18 Oct 22:12
eecf6b1

Repository Standards 8.0.0 is a major release. Plain outdated now prints Markdown; scripts parsing JSON must pass --json. This release implements #278, #288, and #307, alongside the fixes below.

What changed

  • Readable update reports (#304, #278). Plain outdated prints deterministic Markdown with a Pins table and, where needed, Unknown results. It shows pinned/latest versions, availability, newer-release counts and lookup freshness. It adds no lookup or mutation beyond the existing command. Explicit --json retains the existing repo-standards/outdated/v1 report, error behavior, pin enforcement and cache semantics.
  • Standalone adoption entry skill (#289, #288; #308, #307). First containing tag: v8.0.0. adopt-repository-standards is independently installable from this release's skills tree. Its one-sentence body invokes adopt for the user-named standards source, with Repo Canon as fallback, and follows printed instructions. The README Installation prompt uses the same single-pointer approach. The CLI owns all agent instructions, including maintainer decisions and final review. Adoption does not automatically install the entry skill. The name, target and compatibility link are product-reserved.
  • Explicit agent blockers and handoff (#308, #307). New-run NO_COMMIT and DIRTY_PROJECT reports tell agents to stop and notify the maintainer, including answers templates and selection-question reports. Agents must not reconcile or commit pending maintainer work. Active runs continue with expected adoption changes. Completion explicitly prohibits agent commits and hands uncommitted, unstaged changes to the maintainer for review. Ordinary assessments remain the agent's judgment; specific maintainer decisions and conditional confirmation remain intact. Human terminal completion still supports the usual review-and-commit workflow.
  • Reliable self-adoption commands (#305, #294). When adopting in the product's matching-version checkout, printed commands acquire the exact candidate in an external directory with npm scripts disabled and invoke it with --project, avoiding npm's resolution of an unbuilt local package. Continuation and recovery reuse the matching runtime once available. Documentation covers the same external-install route.
  • Project-root rules output (#301, #270). Human-readable rules . headings, coverage and empty results name the project root as .. JSON keeps its existing empty project-relative root path and schema.

Release tooling and repository maintenance

  • Release recovery (#295). The read-only recovery helper recognizes all four Linux/macOS × Node.js 24/26 validation jobs and requires every cell to pass; it retains the historical two-job layout without letting legacy names hide incomplete matrix validation.
  • Public-installation acceptance (#303, #266). Shared propagation polling now allows ten minutes, preserving the ten-second interval and bounded, single-publication acceptance flow.
  • Portable tests (#297, #296; #302, #283; #306, #287). Execution-outcome fixtures allow prerequisite probes to reach the intended operation; committed-evidence guards accept exact source-authored executable scalar values while still rejecting unrelated machine-location leaks; info-exclude fixtures supply their own bytes instead of relying on Git templates, including shared worktree Git directories. Production timeouts and evidence formats remain unchanged.
  • Repository standards updates (#293, #298). The product repository adopted Repo Canon v0.14.1 and then v0.15.0, updating its contribution guidance, review and factory workflow rules, installed skills and retained adoption evidence. These are repository development conventions, not standards automatically applied to consumers by the CLI release.

Impact and migration

  • JSON consumers: replace repo-standards outdated with repo-standards outdated --json. This flag already worked in earlier releases; the JSON schema is unchanged. The installed repository-standards skill already uses it.
  • Standards authors: do not declare a skill named adopt-repository-standards, or overlap its product-owned target/link paths. Rename and relocate any conflicting author skill before using this CLI. Independently installed entry skills use the verified v8.0.0 release-tag route documented in installation; installation is separate from npm and from adoption.
  • Adopting agents: use the one-line entry pointer and follow the running CLI's instructions. On a dirty or uncommitted new project, stop and notify the maintainer. On completion, leave changes uncommitted and unstaged for maintainer review. This preserves the clean-tree start requirement without applying it to active-run work.
  • Existing projects: exact CLI pins, installed system skills and copied standalone bootstraps do not update automatically. Finish or abandon an active run before changing CLI versions. From a clean, committed project, run npx @lutzseverino/repo-standards@8.0.0 adopt, choose the current standards tag to change only the CLI, and review the completed changes. Replace standalone bootstrap copies and independently installed authoring skills deliberately with matching release material. Inside the product checkout, acquire and invoke the candidate externally as documented rather than running npx in that checkout.
  • Stable Node.js 24 and 26 remain supported; the default contributor/publisher baseline remains Node.js 24. No source-format, answers-file, report-schema or committed-state-format migration is introduced. Source operation prerequisites and deliberate standards-pin selection remain the source's and maintainer's responsibility.

Repository Standards 7.2.0

Choose a tag to compare

@github-actions github-actions released this 17 Oct 20:32
e6b1272

Repository Standards 7.2.0 is a minor release with no breaking changes. It supports stable Node.js 24 and 26, while keeping Node.js 24 as the default toolchain. Implements #276 and fixes #277.

What changed

  • Node.js 26 support (#276). The npm package, public inspection/adoption, and standalone bootstrap support stable 24.x and 26.x with their bundled npm. Shipped author examples, authoring guidance, and installation documentation describe both. Linux CI runs all three test parts on each major; macOS and release validation and public installation cover both majors. Publication still produces and publishes one tarball.
  • Fewer repeated source downloads (#277). Verified immutable source snapshots and annotated tag objects are reused from an external cache, and one guided adoption invocation shares its acquisition observations. Repository and tag identities are checked fresh at the existing safety boundaries; moved tags still fail. Damaged cache entries are reacquired. A GitHub connection closed before any response is retried once on a new connection. Optional GitHub token setup is documented for shared-IP anonymous quotas.

Compatibility and migration

  • The supported Node.js range is >=24 <25 || >=26 <27. Node.js 22 remains outside the support policy; odd majors, prereleases and future majors are excluded. Source format, reports, committed state and adoption safety boundaries are unchanged.
  • Existing projects keep their exact CLI pin, installed system skill and copied bootstrap until deliberately replaced. Finish or abandon an active run, then run npx @lutzseverino/repo-standards@7.2.0 adopt from a clean project root. Choose the current standards tag to update only the CLI, and commit once status reports the run ready to commit. Replace an old standalone bootstrap with this release's matching asset separately; independently installed authoring skills also require an explicit update.
  • Standards sources own their operation prerequisites. This CLI release does not broaden a retained source's Node.js range. Repo Canon's source update is tracked separately in repo-canon#503; adopters deliberately update their standards pin after that source publishes.

Published acceptance verified in Release and verification workflow run 39064856448: full validation and public CLI/bootstrap plus standalone authoring-skill installation passed on Linux and macOS under both Node.js 24 and 26. Public checks used Linux Node 24.21.0/26.12.0 and macOS Node 24.19.0/26.12.0. Registry integrity matches release.json; tag v7.2.0 identifies the reviewed release commit e6b1272.

Repository Standards 7.1.0

Choose a tag to compare

@github-actions github-actions released this 17 Oct 18:05
25c9f8e

Repository Standards 7.1.0 is a minor release with no breaking changes. The repository-standards skill now reads the rules that cover the whole repository at the start of any work, not only before a file changes, and adopt no longer offers an older release as the newest when GitHub refuses its release lookup. Implements #268 and fixes #273.

What changed

  • Repository-wide rules at the start of any work (#268). repo-standards rules now accepts no path and prints only the rules of repository-wide declarations, those that cover no path and report coverage repository. When none are installed, it prints No repository-wide rules are installed. and exits 0. The repository-standards skill runs it once at the start of any work, next to its update notice, and the agent follows those rules throughout, including work that changes no file, such as triaging an issue, writing a ticket or applying labels. rules <path> and its output are unchanged. In rules --json, the repo-standards/rules/v1 report's path is null for the no-path form.
  • adopt fails when GitHub refuses the release lookup (#273). Run without a version in an adopted project, adopt lists the source's releases to offer the newest. When GitHub refuses that request because the API quota is exhausted or it rejected the token in GH_TOKEN or GITHUB_TOKEN, adopt now fails with QUOTA_EXHAUSTED or SOURCE_UNAVAILABLE and writes nothing. Before, it offered the current version as though it were the newest. To apply the current version again on purpose, pass --standards-version <current version>. A source that cannot be reached at all still falls back to the current version, and the adoption record now says so under Selection.
  • Alice example (#269). The packaged Alice author example's Python prerequisite is now >=3.9.0 <4.0.0, so its check runs on Python 3.9 to 3.11 as well.

Compatibility and migration

  • Source format, reports, committed state, lock and installed rules are unchanged, so a 7.0.0 source and a 7.0.0 adoption work with 7.1.0 as they are.
  • A 7.0.0 installation keeps its earlier skill, which reads rules only before a file changes, until the project updates its CLI pin. A standards source whose repository-wide rules govern work that changes no file should set requires.repo-standards to ">=7.1.0".
  • To update an adopted project, finish or abandon any active run, then run npx @lutzseverino/repo-standards@7.1.0 adopt from the project root with a clean working tree. Choose your current standards tag to update only the CLI. Commit the update once status reports it ready to commit.

Published acceptance verified in Release workflow run 39054708019, which both published this release and ran its public verification; there is no separate verification run. Full validation passed on Linux and macOS, and public CLI/bootstrap and standalone authoring-skill installation passed on Linux (x64) and Intel macOS, both under Node.js 24.11.1. Registry integrity in both public CLI reports matches release.json, and the downloaded release.json and repo-standards-bootstrap assets match the published checksums. Tag v7.1.0 identifies the reviewed release commit 25c9f8e. These are automated installation, validation and bootstrap checks only: they cover Node.js 24.11.1 alone, not Node.js 26, and establish no adoption, assessment or authoring journey with a real agent, no skills.sh listing, and no completion of the parent specification.

Repository Standards 7.0.0

Choose a tag to compare

@github-actions github-actions released this 14 Oct 13:59
7225c76

Repository Standards 7.0.0 is a breaking release. One adopt command now adopts a standards source and updates an adopted project, for a person in a terminal or for an agent with an answers file. Standards sources can install lasting rules, draft scopes with discovery scripts, and declare remote setup that an adopter can defer. One system skill, repository-standards, replaces standards-updates and adopt-standards. Implements #240; release tracked in #264.

What changed

  • One command to adopt or update (#246, #247, #258). Run npx @lutzseverino/repo-standards adopt <source-url>. In a terminal, it asks for the version, the profile, discovery scope, remote setup deferral and any confirmation-required change. It then walks you through each contextual declaration and writes the assessment from your answers. Without a terminal, it prints an answers-file template (repo-standards/answers/v1) and next steps for an agent, and continues from the filled file. An agent can confirm a confirmation-required change only with the inspection identity that the maintainer confirmed. adopt installs and pins the exact CLI that ran it, so you no longer install a CLI outside the project by hand. Run it without a source in an adopted project to update the current selection. inspect, start and resume remain the lower-level commands that adopt drives.
  • Installed rules (#241). A declaration other than a skill can name rules: Markdown stating its lasting requirements. Adoption installs them at .repo-standards/rules/<declaration-id>.md, with a generated README.md index. repo-standards rules <path> prints the rules covering a path, offline. A check that did not pass names its declaration's installed rules.
  • Discovery scripts (#243). A declaration with discovery can name a discovery-script, declared like a check. Inspection runs it read-only against a copy of the project to draft the scope proposal. Its open questions go to the maintainer, and it never decides scope.
  • Deferred remote setup (#244). A fix that changes the hosting platform's settings can declare remote-setup with a read-only readiness probe. Inspection runs each probe before anything is written. When a probe is not ready, the adopter defers that setup and completes adoption locally, or stops without changes. status and the adoption record list deferred setup, and a later run applies it once its probe passes.
  • Ready-to-commit verdict (#242). status states whether the last run is complete and ready to commit, with a reason for each failing condition.
  • One system skill (#245, #246). The model-invocable repository-standards skill keeps the update notice and looks up installed rules before an agent changes a file. adopt-standards is removed; its procedure is now the next steps that adopt prints.
  • Documentation (#248). The README and the usage guides lead with adopt, and the protocol documents remain as reference.

Breaking changes and migration

CLI commands and reports
  • Plain status now prints the Markdown adoption record with its Ready to commit verdict, as status --summary does. It used to print JSON. Scripts that parse it must call status --json.
  • status --json now returns repo-standards/status/v8, which adds readyToCommit, readinessReasons and deferred. Read readyToCommit instead of combining active, lastComplete, stateError and changeSet yourself.
  • Inspection reports now use repo-standards/inspection/v8, which adds remoteSetup readiness, discovery drafts and the rules contextual change. Obtain a fresh inspection with 7.0.0 rather than reuse an earlier report or identity.
  • check --json now returns repo-standards/check/v2, whose results that did not pass carry rules. Work requests now use repo-standards/work-request/v4, where each declaration names its installed rules. The CHECKS_FAILED reason now names each failed check's rules.
  • Committed state, lock, run and scope-history formats are unchanged, so a 6.0.0 adoption updates in place.
Standards sources

Repo Canon's follow-up specification, repo-canon#370, plans these changes for Repo Canon.

  • guidance is now adoption guidance: one-time steps for the run, kept only with the retained inputs and never installed. Move each declaration's lasting requirements into a separate rules file. Keep migrations, questions for the maintainer and assessment instructions in guidance, written for a person as well as an agent. Rules are accepted on exact files, contextual files and repository declarations. A skill with rules fails with UNKNOWN_FIELD, and a declaration with rules cannot use the ID readme (RESERVED_NAME).
  • Remove every route to adopt-standards. Point adopters and agents to repo-standards adopt instead, using the pinned runtime .repo-standards/runtime/node_modules/.bin/repo-standards once a run has started. Rename any mention of standards-updates to repository-standards.
  • Write no pointer to installed rules in AGENTS.md or other guidance; the repository-standards skill does rule lookup. Cite repo-standards commands, such as rules <path> and status, rather than paths under .repo-standards/inputs/source/.
  • Cite status's ready-to-commit verdict in contribution rules, for example the condition for opening an adoption pull request, instead of status --json fields.
  • repository-standards and author-standards are now the reserved system skill names, along with their .agents/skills/ and .claude/skills/ targets. Rename an author skill or target that uses repository-standards. The retired names are free to use.
  • Optional: declare your scope drafter as a discovery-script so that adopt runs it. Mark fixes that change hosting platform settings, such as labels or repository integrations, with remote-setup and a read-only probe that checks the tool, remote, sign-in and role.
  • Once a source uses rules, discovery-script or remote-setup, set requires.repo-standards to ">=7.0.0", because CLI 6.x rejects these fields as UNKNOWN_FIELD. The source format stays repo-standards/v2. Publish the changes as a new stable tag; leave old tags immutable. A source that uses none of the new fields keeps working with 7.0.0 unchanged, but nothing of its guidance is installed until it adds rules.
Adopting projects: next update
  1. Finish or abandon any active run with its current pinned CLI before you change the pin.
  2. From the project's root, with a clean working tree, run npx @lutzseverino/repo-standards@7.0.0 adopt, either yourself in a terminal or through your agent, which follows the printed answers-file steps. Without a source, adopt updates the current selection. It offers the newest stable standards release, so choose your current tag to update only the CLI, or update both together. The run installs CLI 7.0.0 and pins it in .repo-standards/runtime.
  3. The update installs the repository-standards skill and its .claude/skills link. It removes unedited copies of standards-updates and adopt-standards and their links. A copy you edited stays project-owned, so delete or keep it yourself. Update any personal instructions that name the old skills.
  4. When the selected standards ship rules, the update adds .repo-standards/rules/; commit it with the rest of the update.
  5. Switch any script or CI step that parses plain status output to status --json with status/v8.
  6. Commit the update through your normal workflow once status reports it ready to commit. Fresh checkouts still restore the pinned runtime with npm ci --ignore-scripts --prefix .repo-standards/runtime.

Corrections to the release issue

#264 credited the removal of adopt-standards to #245. #246 removed it, and #245 replaced standards-updates. #264 also listed #242 without marking its status change as breaking. It is breaking, as described above.

Verification: Publication and public acceptance passed on 2026-10-14. Release run 38571220998 validated on Linux and macOS and published the package with trusted publishing. Its macOS public acceptance passed. Its Linux public acceptance failed because npm propagation took longer than the 300-second wait (#266). That failed attempt is preserved in its artifacts. The release-status helper then confirmed the npm integrity, the v7.0.0 tag at 7225c76742c71b4d341c66d2a7f16562b3190fb2 and all four assets against the original bundle. Verification-only run 38577483753 passed the OIDC check and the public CLI, bootstrap and standalone authoring-skill installation on Linux (ubuntu-latest) and macOS (macos-26-intel). Per-OS JSON evidence is retained in each run's `pu...

Read more