Stripe's new Endive API version removes payment_method_types and the payment request button, which hits a Shopify and Next.js checkout built on Elements. Dependencies named in your list are covered; "Shopify" was read as the developer platform and Admin API, and "React" as the react/react library.
01Stripe API · Sep 30Stripe Endive breaks payment_method_types and the payment request button
Stripe's changelog lists API version 2026-09-30.endive. Its breaking changes include removing payment_method_types as a writable parameter on PaymentIntent create/update/confirm and SetupIntent create/update. On this version a request that passes it returns HTTP 400 with code payment_method_types_no_longer_supported. A matching Checkout Sessions change and a removal of the Elements payment-method-types option are listed in the same release.
Endive also deprecates the payment request button: elements.create('paymentRequestButton') throws, including the React PaymentRequestButtonElement. Stripe says Stripe.js versions through Dahlia keep supporting it. The release also lists SeQura payments, BLIK, MB WAY and Bizum changes, and a requirement to collect billing address parameters for non-EEA SEPA Direct Debit payments. Existing pinned versions are not changed until you upgrade. Note: one Stripe page refers to 'API version 2026-08-26.preview' in its impact text, which looks inconsistent with the 2026-09-30.endive heading; check the version string in Workbench.
Act now, before upgrading to 2026-09-30.endive: remove payment_method_types in your Next.js server code, use dynamic payment methods, and replace the payment request button with Express Checkout Element.
02AWS Lambda · Oct 5Lambda python3.10 deprecates Oct 31, 2026; .NET 8 follows Nov 10
AWS's runtime page lists python3.10 (Amazon Linux 2) with a deprecation date of Oct 31, 2026. Block function create and update are both listed as Jul 29, 2027 and Aug 31, 2027 respectively. dotnet8 and container-only dotnet9 are listed at Nov 10, 2026. AWS says it sends notices at least 180 days before deprecation and may stop security patches after the date.
For Node: nodejs20.x was deprecated Apr 30, 2026 (create/update blocks Jul 29 and Aug 31, 2027), nodejs22.x is listed at Apr 30, 2027, and nodejs24.x at Apr 30, 2028. Node.js 26 is in public preview, with a target launch of November 2026, and is not covered by the SLA. The page says dates are for planning and subject to change.
Act now, by Oct 31, 2026: move any python3.10 functions (for example Shopify webhook handlers) to python3.12 or later; move any nodejs20.x functions to nodejs22.x or nodejs24.x.
03Shopify · Aug 24Shopify script tags stop running Mar 1, 2027; creation blocked Oct 1
Shopify's Aug 24 changelog says that from Oct 1, 2026, scriptTagCreate and scriptTagUpdate return a user error and the REST ScriptTag resource rejects POST and PUT, across all API versions. Existing script tags keep running until Mar 1, 2027, when Shopify stops injecting them into storefronts. scriptTags queries and scriptTagDelete keep working.
Replacements are app embed blocks in a theme app extension, or web pixels for analytics-only scripts. This applies to apps using a display_scope of online_store. Published more than 30 days ago but included because the deadline is still ahead and the create block took effect this week.
Coming, by Mar 1, 2027: audit installed apps for script tags, ask vendors for app embed or pixel versions, and re-test tracking on your storefront.
04Shopify · Sep 22Shopify removes marketCurrencySettingsUpdate in Admin API 2027-01
Shopify announced that Admin GraphQL API version 2027-01 removes the marketCurrencySettingsUpdate mutation and its payload and error types. It was deprecated when Markets Home launched in 2025-04, and every call already returns the UNIFIED_MARKETS_ENABLED user error. Versions 2026-10 and earlier keep the field.
Use marketCreate and marketUpdate, which take currency settings directly. In 2027-01, a request that still references the removed field fails validation for the whole request. The changelog also lists 2027-01 removals of the metafieldInteger collection condition and the automaticDiscounts query, and a 2026-10 release dated Oct 1.
Coming, before moving to 2027-01: for EU multi-currency markets, grep your integrations for marketCurrencySettingsUpdate and switch to marketUpdate; no 2027-01 release date was confirmed.
05Census ACS · Aug 6Census has not set a release date for 2025 ACS 1-year estimates
The Census Bureau's ACS updates page (revised Aug 6, 2026) says the release date for the 2025 ACS 1-year estimates is being determined. It says the Bureau is assessing a new Department of Commerce administrative order on disclosure avoidance and seeking compliant solutions to release the 1-year tables later this year. The latest published vintage on that page is 2020–2024 5-year (released Jan 29, 2026) and its PUMS (Mar 5, 2026).
Separately, the page notes a proposal to add the updated race and ethnicity question to the 2027 ACS. No schema or API change for the 1-year tables is confirmed. Dated over 30 days ago but still unresolved.
Worth knowing: if your demographic personalization pulls ACS 1-year via the API, keep using the 2024 vintage and don't schedule a 2025 refresh; it only matters for US data.
06React · Sep 9React 19.3.0 adds ViewTransition and Fragment refs
React 19.3.0 was released Sep 9, 2026, per the GitHub releases page. It adds ViewTransition and addTransitionType, Fragment refs, and a react-dom browser() API, enables Trusted Types integration, and makes transitions render independently instead of being entangled. A DEV warning now flags conditional use().
The same page lists 19.2.8, 19.1.9 and 19.0.8 on Jul 21, 2026, with RSS decoding performance changes. No license change was seen in the releases list; the license file was not checked. Check your Next.js version's supported React range before upgrading.
Worth knowing: test 19.3.0 on a staging Next.js build, watching transitions behavior and Trusted Types; this was not confirmed against Next.js release notes.
Enable JavaScript to read this edition.