Adding a type column to a shared registry breaks every consumer's filter - #58
Open
clarkbw wants to merge 1 commit into
Open
Adding a type column to a shared registry breaks every consumer's filter#58clarkbw wants to merge 1 commit into
clarkbw wants to merge 1 commit into
Conversation
…'s filter Salvaged from an interrupted Scribe run; verified lint + build + privacy scan. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HaMaRk9UijJQMDX48EVvTk
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.
Post: 2026-08-11-shared-registry-kind-field-breaks-consumer-filters-allowlist-vs-denylist-no-live-id-name-drift-warning.md
Drafted by a Scribe agent that was interrupted by the monthly spend limit at the verify step; the finished draft was salvaged from its worktree, then lint (
script/lint-liquid.py),bundle exec jekyll build, and a privacy scan (hostnames/private paths in post + SVGs) were run clean before opening this PR.Date in filename/frontmatter is the draft date — bump at merge via the publish tooling.