Skip to content

test(billing): regenerate storefront goldens for plan catalog revision 13 - #24390

Closed
Git-on-my-level wants to merge 2 commits into
mainfrom
lane/storefront-golden-rev13
Closed

Git-on-my-level wants to merge 2 commits into
mainfrom
lane/storefront-golden-rev13

Conversation

@Git-on-my-level

@Git-on-my-level Git-on-my-level commented Nov 2, 2026 •

Copy link
Copy Markdown
Member

What

backend/config/plan_catalog.json moved to catalog_revision 13 in #24367, but the storefront v2 goldens (backend and app fixtures) stayed at 12. As a result, tests/unit/test_golden_storefront_scenarios fails on main and on every backend PR (seen on #24382, backend unit shard 4/6).

The goldens were regenerated with UPDATE_STOREFRONT_GOLDENS=1. The only change in all 52 files is "catalog_revision": 12 → 13.

Verification

UPDATE_STOREFRONT_GOLDENS=1 BACKEND_UNIT_TEST_FILE_LIST=<test_storefront_presentation.py> bash backend/test.sh: 345 passed.

Product invariants affected

none

🤖 Generated with Claude Code

View guided diff Turn on auto-fix

Git-on-my-level and others added 2 commits November 2, 2026 20:11
…n 13

plan_catalog.json moved to catalog_revision 13 (#24367) while the storefront v2
goldens stayed at 12, so test_golden_storefront_scenarios fails on main and on
every backend PR. Regenerated with UPDATE_STOREFRONT_GOLDENS=1; the only change
is the revision number.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ⚠️ Failed 2026-11-02T13:30:55.767536Z
We couldn’t complete this review. Comment @codex review to try again.
716f0e8 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 53 files

Confidence score: 4/5

  • The schema version 2 parses deck fields test still expects catalogRevision to be 12, but its default fixture now has 13, so the test will fail. Update the expectation to 13.
Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="app/test/fixtures/storefront_v2/cancel_scheduled_pro.json">

<violation number="1" location="app/test/fixtures/storefront_v2/cancel_scheduled_pro.json:3">
P2: The Dart test `schema version 2 parses deck fields` still expects `catalogRevision` to be 12, but its default fixture `plus_monthly_yearly_toggle.json` is now 13. Update the expectation in `app/test/models/plan_storefront_test.dart` to 13, or derive it from the fixture, and run the Flutter tests.</violation>
</file>

Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic

{
"schema_version": 2,
"catalog_revision": 12,
"catalog_revision": 13,

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: The Dart test schema version 2 parses deck fields still expects catalogRevision to be 12, but its default fixture plus_monthly_yearly_toggle.json is now 13. Update the expectation in app/test/models/plan_storefront_test.dart to 13, or derive it from the fixture, and run the Flutter tests.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At app/test/fixtures/storefront_v2/cancel_scheduled_pro.json, line 3:

<comment>The Dart test `schema version 2 parses deck fields` still expects `catalogRevision` to be 12, but its default fixture `plus_monthly_yearly_toggle.json` is now 13. Update the expectation in `app/test/models/plan_storefront_test.dart` to 13, or derive it from the fixture, and run the Flutter tests.</comment>

<file context>
@@ -1,6 +1,6 @@
 {
   "schema_version": 2,
-  "catalog_revision": 12,
+  "catalog_revision": 13,
   "show_subscription_ui": true,
   "header": "Your Pro plan ends Nov 1",
</file context>

@Git-on-my-level

Copy link
Copy Markdown
Member Author

Superseded by #24389 (merged), per the lead.

@Git-on-my-level
Git-on-my-level deleted the lane/storefront-golden-rev13 branch November 2, 2026 15:31
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Hey @Git-on-my-level 👋

Thank you so much for taking the time to contribute to Omi! We truly appreciate you putting in the effort to submit this pull request.

After careful review, we've decided not to merge this particular PR. Please don't take this personally — we genuinely try to merge as many contributions as possible, but sometimes we have to make tough calls based on:

  • Project standards — Ensuring consistency across the codebase
  • User needs — Making sure changes align with what our users need
  • Code best practices — Maintaining code quality and maintainability
  • Project direction — Keeping aligned with our product principles and locked invariants

Before your next PR, please skim:

  • PRODUCT.md — product north star
  • Product invariants — locked rules (shared chat, memory tiers, agent control plane, integrations, brand)

If this was declined for direction or taste, maintainers should cite an invariant ID or open a proposed one — ask if that citation is missing.

Your contribution is still valuable to us, and we'd love to see you contribute again in the future! If you'd like feedback on how to improve this PR or want to discuss alternative approaches, please don't hesitate to reach out.

Thank you for being part of the Omi community!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant