Skip to content

Update Annual Price Id#1198

Open
Queen-esther01 wants to merge 1 commit into
developfrom
update-stripe-annual-price-id
Open

Update Annual Price Id#1198
Queen-esther01 wants to merge 1 commit into
developfrom
update-stripe-annual-price-id

Conversation

@Queen-esther01

@Queen-esther01 Queen-esther01 commented Jan 8, 2026

Copy link
Copy Markdown
Contributor

Closes #<GH_issue_number>

Description of the Problem / Feature

Update stripe annual price id

Explanation of the solution

Instructions on making this work

UI changes for review

When major UI changes will happen with this PR, please include links to URLS to compare or screenshots demonstrating the difference and notify design

Summary by CodeRabbit

  • Chores
    • Updated OMNI_CHATS pricing configuration to use a new price identifier.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai

coderabbitai Bot commented Jan 8, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

A Stripe price ID configuration value for OMNI_CHATS annual pricing was updated in the stripe configuration file. The environment variable fallback mechanism remains unchanged, and no control flow or business logic was altered.

Changes

Cohort / File(s) Summary
Configuration Update
desci-server/src/config/stripe.ts
Updated default ANNUAL price ID for OMNI_CHATS from price_1S0sHWAqadM33xzp6wNaaRe3 to price_1SmxVFAqadM33xzpTGjdBBeA. Environment variable fallback mechanism preserved.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A price ID hops along,
From one to the next, not wrong,
Stripe's numbers dance and sway,
OMNI_CHATS charges the day,
Config fresh, the path stays long! 🌕

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Update Annual Price Id' directly matches the changeset which updates the annual price ID constant in the Stripe configuration file from one value to another.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ec5d9bb and 708d4e0.

📒 Files selected for processing (1)
  • desci-server/src/config/stripe.ts
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: build-and-test
  • GitHub Check: test-nodes-lib
🔇 Additional comments (1)
desci-server/src/config/stripe.ts (1)

9-9: Ensure the new price ID has been configured and tested in Stripe before deployment.

This updates the fallback annual price ID for OMNI_CHATS (used when STRIPE_OMNI_CHATS_ANNUAL_PRICE_ID is not set). The change is isolated to line 9 and correctly reflects the $90/year pricing defined in PLAN_DETAILS (line 33). However, before merging, confirm that:

  1. The price ID price_1SmxVFAqadM33xzpTGjdBBeA is active in Stripe
  2. Checkout flows have been tested in your Stripe staging environment
  3. Deployments relying on this fallback have been validated

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@Queen-esther01 Queen-esther01 requested a review from m0ar January 8, 2026 23:33
@m0ar

m0ar commented Jan 9, 2026

Copy link
Copy Markdown
Contributor

@Queen-esther01 Can we close this after the vault update?

@Queen-esther01

Copy link
Copy Markdown
Contributor Author

@Queen-esther01 Can we close this after the vault update?

Incase the env is ever missing, we'd need the right fallback.

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.

2 participants