If your platform touches cloud infrastructure, payment processing, or AI tooling, there’s a good chance something you depend on is changing in the next two months. Here’s a roundup of confirmed deprecations and sunset dates coming up, organized so you can check your own dependency list against it.
AWS Proton retires on October 7
AWS is ending support for Proton, its infrastructure deployment and management service, on October 7. After that date, you’ll lose access to the Proton console and its resources entirely, though any infrastructure it already deployed will keep running. If your team uses Proton to manage CI/CD templates or environment provisioning, AWS is pointing customers toward CodePipeline and CodeBuild as the more flexible path forward. This one’s worth flagging even if you don’t think you use it directly, since it sometimes shows up buried in a DevOps team’s tooling from a few years back.
Source: AWS Proton Service Deprecation and Migration Guide
Amazon Pinpoint sunsets on October 30
Pinpoint’s campaign, journey, segment, and analytics features go away on October 30. This matters most if you’ve built customer engagement workflows (scheduled SMS sends, A/B tested campaigns, audience targeting) on top of Pinpoint. The good news is that straightforward transactional messaging (SMS, push notifications, voice, OTP codes) has already moved to AWS End User Messaging and needs no migration. But if your ISV built anything with the campaign orchestration layer, that piece needs a real migration plan before the end of October.
Source: Amazon Pinpoint end of support
OpenAI’s Assistants API goes away on August 26
If your product integrates with OpenAI’s Assistants API, this is close: OpenAI notified developers a year ago that the Assistants API would be removed on August 26, and that date has essentially arrived by the time you’re reading this. The Responses API and Conversations API are the intended replacements. If you haven’t migrated, treat this as urgent rather than upcoming, and check your integration today rather than filing it under next quarter’s roadmap.
Source: OpenAI API deprecations page
PayPal Standard is being phased out
PayPal has been actively sunsetting its older Standard integration (including the classic Buy Now and Add to Cart buttons) throughout 2026, with full processing shutdown coming in January 2027. If your checkout flow still runs through PayPal Standard rather than the modern PayPal Checkout integration, this isn’t an emergency yet, but it’s close enough that you should have a migration ticket open now rather than scrambling in December. Ecommerce platforms like WooCommerce have already started disabling Standard automatically for merchants who connect a modern PayPal account, so some of your customers may find this decision made for them.
Sources: WooCommerce: PayPal Standard is sunsetting, Gravity Forms: PayPal Payments Standard Add-On end of life
GitHub’s code search API field deprecation lands September 27
GitHub has set a sunset date of September 27 for a deprecated field in its code search API, part of the platform’s ongoing move toward its newer search endpoints. This is a narrower change than the others on this list, but if your product does any code analysis, repository scanning, or developer tooling integration with GitHub, it’s worth a quick check against your API calls before the date arrives.
Source: GitHub API deprecation coverage
What this means for your team
None of these individually are catastrophic, but taken together they’re a good reminder that deprecation notices rarely arrive with enough runway to handle casually. The pattern worth building into your own process is simple: assign someone to actually own vendor changelogs and deprecation pages for your critical dependencies, rather than relying on catching an email that might land in a shared inbox nobody checks. A missed deprecation doesn’t just cost you a scramble, it costs you a support ticket from a customer who didn’t do anything wrong and doesn’t care whose API changed.
If you’re building against a mix of cloud, payment, and AI platforms (which most modern ISVs are), it’s worth setting a recurring calendar reminder, maybe monthly, to skim the changelog pages for your top five or six dependencies. It’s a small habit that saves you from the worst version of this problem: finding out about a sunset date from an angry customer instead of from the vendor.
