Repository navigation
docs: release v1.2.1 — drift the prompt audit found - #36
Merged
Merged
Conversation
A patch release: fixes to the framework's instruction files (#35), with nothing new to adopt. Unreleased becomes v1.2.1, with the upgrade from v1.2.0: /aplyca-adf:upgrade moves the pin; a packaged project updates the three rule files it commits. plugin.json 1.2.1; both READMEs name the release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
A patch release (decision 0017): fixes to the framework's instruction files from the prompt audit (#35), with nothing new to adopt.
CHANGELOG.md: Unreleased becomes v1.2.1 — 2026-10-05, with the upgrade from v1.2.0./aplyca-adf:upgrademoves the pin, and a packaged project updates the three rule files it commits.plugin.json:1.2.1.v1.2.1.Static evals all pass, including the check that the plugin's version matches the newest release in the CHANGELOG.
After merge: push the
v1.2.1tag on the merge commit and create the GitHub release, once approved.🤖 Generated with Claude Code