Repository navigation
chore(brand): refresh the snapshot — the markers were rendering a stale catalog - #517
Conversation
…le catalog Opened by brand/fanout-brand-numbers.mjs. brand-numbers.json here was behind the published artifact, so every br: marker in this repo rendered a number that is no longer true. The markers did their job — they rendered the input they were given. --check is offline on purpose so PR CI stays deterministic, which means it validates against this repo's own snapshot, and only --refresh updates that snapshot. This job is what runs it. Produced by --refresh, not by hand.
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Update fallback model count brand-numbers.json |
The models.withFallbackAllEntries value changes from 68 to 69. |
Priority:
Estimated code review effort: 1 (Trivial) | ~2 minutes
Change: Other
Suggested reviewers: ubounty-app
Merge Risk: 
cb9e4
-
No actionable merge-blocking risk was identified.
Pre-merge checks: 
-
Check name Status Explanation Description Check Check skipped - CodeRabbit’s high-level summary is enabled. Title check The title names the main change: a refresh of the brand-numbers.json snapshot, which the author says was stale and caused br: markers to render old numbers. The raw summary confirms a single-value upd… Docstring Coverage No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Title check
-
Explanation
The title names the main change: a refresh of the brand-numbers.json snapshot, which the author says was stale and caused br: markers to render old numbers. The raw summary confirms a single-value update (models.withFallbackAllEntries from 68 to 69) in brand-numbers.json. The title uses the conventional chore(brand) prefix and states the purpose. It is 79 characters, slightly longer than ideal, but it is specific and clear.
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
brand-numbers.jsonin this repo was behind the published artifact, so everybr:marker here rendered a stale number.The markers worked correctly — they rendered the input they had.
--checkis offline by design so PR CI stays deterministic, which means it validates against this repo's own snapshot; only--refreshupdates that snapshot.Opened automatically by
brand/fanout-brand-numbers.mjs. Produced by--refresh, no hand-edited digits.Summary by CodeRabbit