Docs: record v1.1 as released; adopt PR-only workflow - #38
Merged
Conversation
CLAUDE.md and userdocs/Changelog.md still described v1.1 as "the next tagged release" after it shipped 2026-08-04 -- the same staleness class CLAUDE.md's own release paragraph warns about. Update both (release header, M12 section, and a real What's-next list pointing at the queued vlink-inspired ideas #31/#32). Also document the new repo workflow: main is now branch-protected (PRs + passing CI checks required, admins included), so all changes -- including this one, the first to follow the rule -- go via pull requests. Motivated partly by the v1.1 release's --generate-notes coming out nearly empty because M14-M19 landed as direct commits. Co-Authored-By: Claude Fable 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
1 participant
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.
Docs-only. Two things:
userdocs/Changelog.mdstill described v1.1 as "the next tagged release" after it shipped 2026-08-04. Both updated (Changelog release header, M12 section, and a real What's-next list pointing at the queued vlink-inspired ideas Mirror device name: crossover pairing for unit-0-only consumers (vlink's vlink/vlinkmirror pattern) #31/Userdocs: step-by-step real-stack wiring walkthroughs (Miami/AmiTCP/Roadshow), à la vlink.guide #32). The stale Changelog text already shipped to the published v1.1 docs site — re-publish viadocs.yml'sworkflow_dispatchafter this merges.mainis now branch-protected (PR + passing CI checks required, enforced for admins; tag pushes unaffected). New CLAUDE.md section documents it, including why (the v1.1--generate-notesgap: generated notes only see PRs, and M14–M19 all landed as direct commits) and the maintenance caveat (required check contexts must tracksidick/amiga-workflowsjob names). This PR is the first to follow the rule.🤖 Generated with Claude Code