chore(readme): point the adopter pin at the newest servable release #1519
No reviewers
Labels
No labels
bump
major
bump
minor
bump
patch
kind
bug
kind
chore
kind
docs
kind
epic
kind
feature
loop/paused
mirror-drift
priority
critical
priority
high
priority
low
priority
medium
size
L
size
M
size
S
size
XL
status
blocked
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
frankenbit/release-toolkit!1519
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/readme-pin-20261002184936"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Opened by
mirror-release.ymlafter a successful mirror publish (release-toolkit#1378). The adopter-facing pins inREADME.md,docs/integration.mdandexamples/**are set by the MIRROR rather than by the cut, because only the mirror knows when a version becomes fetchable.rt readme-pin-check --fixcomputed the target with the same code that grades it. Read the diff: this changes what a stranger is told to pin.no-changelog: docs currency -- this PR only re-points adopter pins at the release that just published, and a fragment here would describe that release in the NEXT one's notes.
Landing identity record
340608c8e0865d8364fbb31f3dc855ca75b76d6eThis is a post-merge identity record. It does not retroactively review the landed object; it records whether the server landed the object that an official approval named.