Watching 44 sources · checked 4 h ago
Changes
- 2172
- in the catalog
- 192
- new this week
- 63
- dated ahead
npm packages1 d agominimatch 3.1.5 → 11.0.3: changes the arguments of 2 function(s)breaks on upgrade+13
RubyGems packages1 d agoactivesupport: Possible DoS vulnerability in Active Support safe_constantizesecurity+8RubyGems packages1 d agoactivestorage: Possible arbitrary file read and remote code execution in Active Storage video previews, analysis and image processingsecurity+6RubyGems packages1 d agoactionview: Possible XSS vulnerability in Action View highlight helpersecurity+3RubyGems packages1 d agoactionpack: Possible sensitive session information leak in Active Storage proxy modesecurity+62026-10
“Deprecated POST /quote, POST /quote/v2, and POST /price: the useExternalLiquidity and useFallbacks request fields are now accepted but ignored. The canonical+ bridging path and the fallback-route path they selected have been removed from the quote engine. Both fields are marked deprecated in the request schema and can be dropped from your integration. Callers that previously sent useExternalLiquid…”docs.relay.link ›
“Deprecated POST /quote, POST /quote/v2, and POST /price: the useExternalLiquidity and useFallbacks request fields are now accepted but ignored. The canonical+ bridging path and the fallback-route path they selected have been removed from the quote engine. Both fields are marked deprecated in the request schema and can be dropped from your integration. Callers that previously sent useExternalLiquid…”docs.relay.link ›
“Breaking GET /requests/:requestId/signature and GET /requests/:requestId/signature/v2 have been removed. Calls to both endpoints now return 404. Both returned a solver signature over a small subset of intent fields, which never covered the minimum output amount, required a second call after the quote, returned only partial data until the request reached a terminal state, and behaved inconsistently…”docs.relay.link ›
“Breaking GET /requests/:requestId/signature and GET /requests/:requestId/signature/v2 have been removed. Calls to both endpoints now return 404. Both returned a solver signature over a small subset of intent fields, which never covered the minimum output amount, required a second call after the quote, returned only partial data until the request reached a terminal state, and behaved inconsistently…”docs.relay.link ›
2026-11
“Renames the allowed_source_types field for sources to payment_method_types · Payments · Breaking · api”docs.stripe.com ›
“Renames the authorize_with_url field for Payment Intents to redirect_to_url · Payments · Breaking · api”docs.stripe.com ›
“Renames the next_source_action field for Payment Intents to next_action · Payments · Breaking · api”docs.stripe.com ›
“Renames the save_source_to_customer field for sources to save_payment_method · Payments · Breaking · api”docs.stripe.com ›
“Accounts no longer provide a keys field. Platforms should use their own API key to authenticate as their connected accounts · Connect · Breaking · api”docs.stripe.com ›
“Accounts in the US now require specifying capabilities at creation time · Connect · Breaking · api”docs.stripe.com ›
“Several fields describing an account’s business details have moved to the business_profile subhash · Connect · Breaking · api”docs.stripe.com ›
“Changes statement descriptor behaviors for card payments created with Charges · Payments · Breaking · api”docs.stripe.com ›
“Renames the business_id_number for an account’s legal entity to business_registration_number · Connect · Breaking · api”docs.stripe.com ›
“Several account fields have been refactored to better describe legal entity, verification status and requirements, and configurable settings · Connect · Breaking · api”docs.stripe.com ›
“Verification of accounts or persons now supports uploading both front and back sides · Connect · Breaking · api”docs.stripe.com ›
“Invoices now provide timestamps for each state transition · Billing, Invoicing · Breaking · api”docs.stripe.com ›
“Invoices now specify when they’re finalized alongside other status transitions · Billing, Invoicing · Breaking · api”docs.stripe.com ›
“Renames application_fee on invoices to application_fee_amount · Connect, Invoicing · Breaking · api”docs.stripe.com ›
“Renames the date field for invoices to created · Billing, Invoicing · Breaking · api”docs.stripe.com ›
“Subscriptions are now successfully created even if the first payment fails · Billing · Breaking · api”docs.stripe.com ›
“Bank pull payments no longer expose internal system refunds on failure · Payments · Breaking · api”docs.stripe.com ›
“Configuring a person as an account opener no longer automatically sets them as an executive · Connect · Breaking · api”docs.stripe.com ›
“Renames the platform_payments capability for accounts to card_payments, requiring the manual specification of the added transfers capability · Connect · Breaking · api”docs.stripe.com ›
“Accounts in many countries now require specifying capabilities at creation time · Connect · Breaking · api”docs.stripe.com ›
“Adds new details_code values to person document verification · Connect · Breaking · api”docs.stripe.com ›
“The due_date property is always null on auto-billed invoices · Billing, Invoicing · Breaking · api”docs.stripe.com ›
“Renames account_balance to balance on Customer object · Billing, Invoicing · Breaking · api”docs.stripe.com ›
“Renames billing to collection_method on invoices, subscriptions, and subscription schedules · Billing, Invoicing · Breaking · api”docs.stripe.com ›
“Replaces the subscription start field with start_date · Billing · Breaking · api”docs.stripe.com ›
“Renames and updates subscription schedule renewal properties · Billing · Breaking · api”docs.stripe.com ›
“Adds requirement for requested_capabilities on custom account creation · Connect · Breaking · api”docs.stripe.com ›
“Nested subscription schedule settings under default_settings · Billing · Breaking · api”docs.stripe.com ›
“Customer balances are now returned when voiding invoices · Billing, Invoicing · Breaking · api”docs.stripe.com ›
“New requirement for out_of_band_amount when creating post-payment credit notes · Billing, Invoicing · Breaking · api”docs.stripe.com ›
“Removes deprecated tax information fields from the Customer object · All products · Breaking · api”docs.stripe.com ›
“Invoices can now be numbered sequentially across your account · Billing, Invoicing · Breaking · api”docs.stripe.com ›
“Adds new error codes to the Accounts, Persons, and Capabilities APIs · Connect · Breaking · api”docs.stripe.com ›
“Customer sources are no longer auto-expanded by default · Payments, Billing, Invoicing · Breaking · api”docs.stripe.com ›
“Customer subscriptions are no longer auto-expanded by default · Billing · Breaking · api”docs.stripe.com ›
“Plan tiers are no longer auto-expanded by default · Billing · Breaking · api”docs.stripe.com ›
“Tax IDs are no longer auto-expanded on the Customer object · All products · Breaking · api”docs.stripe.com ›
“Deprecates subscription prorate and subscription_prorate parameters · Billing · Breaking · api”docs.stripe.com ›
“Formats requirements for key persons associated with accounts · Connect · Breaking · api”docs.stripe.com ›
“Removes the display_items property from Checkout Sessions · Checkout · Breaking · api”docs.stripe.com ›
“Removes the tax_percent attribute · Checkout, Billing, Invoicing · Breaking · api”docs.stripe.com ›
“Renames event type that triggers on automatic updates · Payments · Breaking · api”docs.stripe.com ›
“Renames phases attributes in subscription schedules · Billing · Breaking · api”docs.stripe.com ›
