what stackpulse tracks
Stripe Node releases from GitHub
StackPulse watches Stripe Node release notes and keeps the original source link close to every summary.
Node.js library for the Stripe API StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Stripe Node release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
The release notes only link to a separate changelog and provide no details about the changes in this release. The specific features, fixes, and upgrade implications cannot be determined from the supplied release text.
view details view source on github->The release notes provide only a link to the changelog; they do not describe the changes in this release. The available source is therefore insufficient to identify features, fixes, or compatibility impacts.
view details view source on github->The release notes contain only a link to the changelog, so the changes in this prerelease cannot be determined from the provided source. No features, breaking changes, security fixes, deprecations, or migration steps are documented here.
view details view source on github->The release notes only link to the changelog and provide no details about the changes in this prerelease. Features, compatibility changes, fixes, and upgrade guidance cannot be determined from the supplied source.
view details view source on github->The release notes link to the project changelog for the full details but do not describe any changes in the provided text. The available source is too limited to identify features, fixes, or upgrade requirements.
view details view source on github->This is a beta release of Stripe Node. Refer to the changelog for detailed release notes.
view details view source on github->Release notes reference an external changelog without providing specific details in the GitHub release markdown.
view details view source on github->This is a pre-release version with no detailed release notes provided.
view details view source on github->Release notes are not directly available in the markdown; refer to the linked changelog for details.
view details view source on github->This is a prerelease version with no detailed release notes provided.
view details view source on github->This is a prerelease version (v23.1.0-alpha.1) with no detailed release notes provided in the markdown. Users should refer to the linked changelog for full details.
view details view source on github->This is a beta release of Stripe Node v23.1.0. Refer to the changelog for detailed release notes.
view details view source on github->This release includes updates and changes to the Stripe Node library. Refer to the changelog for detailed information.
Review the changelog for detailed release notes and any necessary actions.
This is a pre-release version with limited details provided in the release notes.
view details view source on github->This is a prerelease version with limited release notes available. Refer to the changelog for detailed information.
view details view source on github->This alpha release introduces several new API fields and enum values while making two previously optional fields required. The changes primarily expand tax, payment, and subscription functionality.
Developers using `PaymentIntent.payment_record` or `Subscription.trial_settings.end_behavior.billing_cycle_anchor` without setting them will be affected.
Update code to provide required fields `PaymentIntent.payment_record` and `Subscription.trial_settings.end_behavior.billing_cycle_anchor`.
This release introduces validation for webhook secrets to ensure they are non-empty, improving reliability and security.
Developers using webhook secrets in Stripe Node are affected by the new validation.
Ensure all webhook secrets are non-empty to avoid validation errors.
This alpha release introduces several new resources and methods, particularly around Radar, Signals, and Tax integrations, while making some breaking changes to existing APIs.
Developers using removed methods or enum values, or relying on the changed types, will be affected.
Review breaking changes and update code to use new methods and types where necessary.
This release focuses on security improvements and bug fixes, including hardening API requestor code against malicious URLs and fixing serialization issues for GET and DELETE parameters.
Users relying on GET/DELETE parameter serialization or handling file uploads may be affected.
Upgrade to ensure secure handling of file uploads and API requests.
This release introduces support for new resources and methods, such as `CustomerTaxExemption`, and adds various enhancements to existing features. It also includes several breaking changes, including the removal of support for `sequra_payments` and `sequra` across multiple endpoints.
Users relying on `sequra_payments` or `sequra` functionality will be affected by the breaking changes.
Review the breaking changes and update your code to remove references to `sequra_payments` and `sequra`.