From ac1e90329451bf78e8a7a6a666d3e342d1adbafd Mon Sep 17 00:00:00 2001 From: sehkone Date: Sun, 9 Aug 2026 14:14:47 +0900 Subject: [PATCH] Take the changelog block and schedule the apply Two gaps were left when the pin moved to a data file. Nothing here scheduled apply.yml, so this repository never proposed a release to itself; and repos.json upstream now lists changelog for deploy-core while the repository carried only workflow and rust. The second one cannot be delivered by the machinery that delivers everything else. render.py refuses a block whose marker pair is not already in the target, so the apply cannot bootstrap a block into a repository that has never had it -- the marker pair has to arrive by hand once, and so does the CHANGELOG.md the block is about. STYLE.md upstream asks the block to follow the file rather than lead it, and this is the file arriving. Landing it at the end state in one commit, because every intermediate is red: a marker pair the pin file does not list is a block this repository does not carry, a pin file listing changelog before the region is filled does not match the release, and either without CHANGELOG.md is a rule about a file that is not here. The regions were rewritten by apply_blocks.py against the 0.1.1 tree rather than by hand, so this is what the scheduled job would have written had it been able to. It moves the pin from v2 to 0.1.1 and drops the old v from every BEGIN marker along the way. Closes #46 --- .agents/instructions.toml | 4 +- .github/workflows/update-instructions.yml | 34 ++++++++++++++++ AGENTS.md | 49 ++++++++++++++++++++--- CHANGELOG.md | 6 +++ 4 files changed, 86 insertions(+), 7 deletions(-) create mode 100644 .github/workflows/update-instructions.yml create mode 100644 CHANGELOG.md diff --git a/.agents/instructions.toml b/.agents/instructions.toml index 065b919..ed64752 100644 --- a/.agents/instructions.toml +++ b/.agents/instructions.toml @@ -2,5 +2,5 @@ # it is on, and the shared blocks it has. Its drift check reads this file, # and its apply job rewrites it. Which blocks a repository should carry is # decided upstream in repos.json, not here. -ref = "v2" -blocks = ["workflow", "rust"] +ref = "0.1.1" +blocks = ["workflow", "rust", "changelog"] diff --git a/.github/workflows/update-instructions.yml b/.github/workflows/update-instructions.yml new file mode 100644 index 0000000..db8d8e8 --- /dev/null +++ b/.github/workflows/update-instructions.yml @@ -0,0 +1,34 @@ +name: Update shared instructions + +# Proposes the latest release of aicers/agent-instructions as a pull +# request: it rewrites the marked regions in AGENTS.md and moves the pin in +# `.agents/instructions.toml`. A run that finds this repository already on +# the latest release opens nothing. +# +# No `with:` and no `secrets:`, deliberately. Which blocks this repository +# takes is decided upstream in repos.json and read out of the release; the +# pin comes from the file. Nothing here needs editing, which is what lets +# the apply run on the default GITHUB_TOKEN: it never has to push a change +# to a workflow file, and GitHub refuses such a push from the Actions app. +# +# workflow_dispatch is not only for convenience. GitHub disables a schedule +# after 60 days without repository activity, and does so silently, so the +# manual trigger is how a stopped schedule is recovered without a dummy +# commit. +# +# The pull request arrives with no checks on it. Events from GITHUB_TOKEN +# start no workflow runs, which is GitHub's guard against a workflow +# retriggering itself. Close and reopen the pull request to run them. + +on: + schedule: + - cron: "0 6 * * 1" + workflow_dispatch: + +jobs: + update: + name: Update + permissions: + contents: write + pull-requests: write + uses: aicers/agent-instructions/.github/workflows/apply.yml@main diff --git a/AGENTS.md b/AGENTS.md index 10c7f3a..3788173 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -5,7 +5,7 @@ The marked regions below are generated from Do not edit them here — change the wording upstream, tag a release, and re-run its sync. The drift check in CI fails if this copy diverges. - + ## Language - Code, comments, commit messages, PR descriptions, and issues are written @@ -29,9 +29,10 @@ re-run its sync. The drift check in CI fails if this copy diverges. - Branch names must follow the format `/issue-#` (e.g., `alice/issue-42`). If there is no related issue, ask the user how to proceed before creating the branch. -- The sole exception is a branch carrying a synced update to the shared - blocks below, which uses `/instructions-