-
Notifications
You must be signed in to change notification settings - Fork 6
Add bitcoin estimates and registry_url #32
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
Conversation
strategy: | ||
matrix: | ||
node: ['10', '12', '14'] | ||
node: ['10', '12', '14', '16'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding node 16, which is getting common. Node 10 is EOL and could be removed in the future (AWS dropped support recently)
require: '@babel/register' | ||
recursive: true No newline at end of file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Switching to the non-deprecated config format for mocha options.
expect(parseFloat(createOrderResponse.data.price_cents_usd)).to.be.closeTo( | ||
500, | ||
1 | ||
); | ||
expect(createOrderResponse.data.patch_fee_cents_usd).to.equal('0.0'); | ||
expect(createOrderResponse.data.mass_g).to.equal(500000); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Existing values were not working after we changed billing. This should have been updated, but most importantly caught by the health check. It did, but we weren't paying attention (I don't know where the alerts went). I'll take a closer look when we strengthen the SDK.
What
Why
SDK Release Checklist
For breaking changes, did you plan for the release of the new SDK versions and deploy the API to production?