You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cybersource is adding a security requirement to use certificates Feb 15th. The old methods security methods won't work anymore. I'm going to try to integrate the new certificate into the codebase. My question is, this is clearly a breaking change. Is there any way we can let people know about this breaking change before we push the update? I'd hate to take down production websites because of this update.
The text was updated successfully, but these errors were encountered:
We have two options:
- Publish a version that supports both the old mechanism and the new, so that upgrading won’t break existing setups.
- Publish a fix in a release which bumps the MAJOR version. Nobody should be upgrading a MAJOR version of a dependency on production without at minimum checking the changelog.
https://developer.cybersource.com/docs/cybs/en-us/platform/relnote/all/na/rn-2024-11-26/rn-announce.html
Cybersource is adding a security requirement to use certificates Feb 15th. The old methods security methods won't work anymore. I'm going to try to integrate the new certificate into the codebase. My question is, this is clearly a breaking change. Is there any way we can let people know about this breaking change before we push the update? I'd hate to take down production websites because of this update.
The text was updated successfully, but these errors were encountered: