Repository navigation
Re-pin to registry v1.4.1 — second drift in one day - #213
Merged
Merged
Conversation
Same procedure as #212, same outcome: our 13 declared names are unchanged in class and membership at v1.4.1, verified rather than assumed before the pair was bumped. The upstream change is a register reframing that imposes nothing on consumers. Noted in ADR-013 rather than acted on: the registry moved twice today, and a pin chased per-PR is a real cost. If views-appwrite stays this active, the check may want a MAJOR/MINOR floor rather than an exact match. That is a decision, not a fix, so it is recorded where the next person re-pinning will read it. Co-Authored-By: Claude Opus 5 (1M context) <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.
Unblocks CI. Same procedure as #212, same outcome.
The Appwrite Seam Contract's registry moved twice today — v1.3.0 → v1.4.0 → v1.4.1. S6's detector caught both.
Re-verified, not just bumped
Upstream change is a register reframing (their D-05 / C-61..C-64) — nothing that reaches a consumer. Pin bumped as a pair, and the commit confirmed an ancestor of
main.One thing recorded rather than acted on
A pin that has to be chased per-PR is a real cost. Two re-pins in one day is not the cadence this check was designed against — S6 assumed a registry that moves occasionally, not hourly.
If views-appwrite stays this active, the check may want to compare a MAJOR/MINOR floor rather than an exact version, so a patch-level reframing upstream doesn't turn this repo red. That is a design decision about how tightly the two repos should be coupled, not a bug, so I have written it into ADR-013 where the next person re-pinning will read it rather than changing the check unilaterally.
🤖 Generated with Claude Code