-
-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: allow release breaking change for stripe node module bump #714
chore: allow release breaking change for stripe node module bump #714
Conversation
* chore: bump stripe version to 14.19.0 * fix: bump default Stripe API version --------- Co-authored-by: Dennis von der Bey <fermentfan@users.noreply.github.com>
ts-vitest is meant to be imported by vitest as such it needs to be a proper ESM module. The package.json already defined it as "type": "module", but the typescript build was still generating a CommonJS build. This fix updates the typescript configuration to output an ESM module. re golevelup#613
* feat(rpc): handle parallel RPCs response * docs(rabbitmq): add in distributed systems
…wildcards (golevelup#713) * fix(rabbitmq): a fix for routing key check. The check should respect wildcards fix golevelup#712 * test(rabbitmq): added tests for matchesRoutingKey and logic improved re golevelup#712 --------- Co-authored-by: andriusm <andriusm@softpauer.com>
BREAKING CHANGE: this marks the next release to be released with a breaking version
Bump 👀 |
@WonderPanda Any idea when you're around to do this? :) |
3b0cb11
to
30e501d
Compare
I updated the commit history for this and a few other commits to make sure that they're following conventional commits and we don't have to add new commits to backfill. I bumped stripe to 0.7.0 (instead of 0.6.6 which it would have been prior to this change) since we've never done an official 1.0 release. The changelog for the package makes it clear that this is a breaking change and people will have to update their underlying Stripe dependency |
This is the PR to solely add the needed commit message for the release process to get the newest Stripe node module in the pipeline. See #705 .
BREAKING CHANGE: this marks the next release to be released with a breaking version