Repository navigation
chore: version skills - #98
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 13, 2026 23:05
c7b6eeb to
bf94c67
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 14, 2026 02:23
bf94c67 to
ce8e21f
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 14, 2026 03:02
ce8e21f to
6d2a2d9
Compare
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
github-agent-workflow@1.11.1
Patch Changes
reconcile-github-issues,file-github-issues,explore-github-repoandsetup-github-agent-workflow) now list what they may write asallowentries, which completes ADR 0017: every contract that writes is checked by what it writes and not only by where. Anallowforcreate_issueandcreate_prnow has a requiredlabelslist, so "new issues, with no labels" and "a PR labelled agent:needs-work" are checked, andimplement-github-issueis tightened to match. The wording of the contracts is unchanged.triage-github-issue,implement-github-issueandreview-github-prnow list what they may write asallowentries (step 2 of ADR 0017), so the scenario checker refuses a label, a comment marker or an op that the skill's text does not permit, even where its scope allows a write. For example triage applyingwontfix, implementing merging a PR, or review sending a linked issue back toready-for-agent. The wording of the skills' contracts is unchanged.effects.writescan now carry anallow(op, and where it applieslabelandmarker), so the scenario checker can tell that an effect is the right one and not only that it is in the right scope. A skill that addswontfixto its claimed PR, or comments with a marker it does not list, is now a violation. A scope that has noallowis checked as before, and one that mixes the two is rejected.shepherd-github-pris the first contract migrated (ADR 0017); the others follow a scope at a time.