Skip to content

fix: default payment methods - #7823

Merged
mergify[bot] merged 2 commits into
mainfrom
fetch/payment-methods
Oct 6, 2026
Merged

mergify[bot] merged 2 commits into
mainfrom
fetch/payment-methods

Conversation

@fetchfern

@fetchfern fetchfern commented Oct 5, 2026 •

Copy link
Copy Markdown
Member
  • If a default payment method doesn't exist explicitly on Stripe's end, use the customer's payment method if only one exists. Retrying across multiple payment methods will be implemented later.
  • The frontend currently assumes that the first payment method is the primary, if no explicit primary exists. Fix this to reflect the new behavior.

Fixes DEV-1472

@fetchfern fetchfern added backend Involves work from the backend team frontend Involves work from the frontend team labels Oct 5, 2026
@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Pull request changelog

App

Added

Changed

Deprecated

Removed

Fixed

Security

Website

Added

Changed

Deprecated

Removed

Fixed

Security

Hosting

Added

Changed

Deprecated

Removed

Fixed

Security

@fetchfern
fetchfern requested review from a team and aecsocket October 5, 2026 16:33
@github-actions

github-actions Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

@mergify

mergify Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Queued — the merge queue status continues in this comment ↓.

@mergify

mergify Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Merge Queue Status

  • ✅ Entered queue — 2026-10-06 16:28 UTC · Rule: default · triggered by @fetchfern with the merge queue checkbox
  • 🚫 Left the queue — 2026-10-06 16:55 UTC · at 61cc0645ba04f44b826be0671a68b20029b1a927

This pull request spent 26 minutes 43 seconds in the queue, with no time running CI.

Reason

Pull request #7823 has been dequeued

Queue conditions are not satisfied:

  • -conflict [📌 queue requirement]

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

# Conflicts:
#	apps/labrinth/src/routes/internal/billing.rs
@mergify mergify Bot removed the dequeued label Oct 6, 2026
@mergify

mergify Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Merge Queue Status

This pull request spent 16 minutes 13 seconds in the queue, including 15 minutes 45 seconds running CI.

Required conditions to merge

@mergify mergify Bot added the queued label Oct 6, 2026
@mergify mergify Bot mentioned this pull request Oct 6, 2026
6 of 10 tasks
@mergify
mergify Bot merged commit ed5ccb5 into main Oct 6, 2026
15 checks passed
@mergify
mergify Bot deleted the fetch/payment-methods branch October 6, 2026 20:19
@mergify mergify Bot removed the queued label Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend Involves work from the backend team frontend Involves work from the frontend team

Development

Successfully merging this pull request may close these issues.

2 participants