Skip to content
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: use db ids > JS MAX_SAFE_INTEGER in test #2020

Merged
merged 1 commit into from Oct 17, 2022

Conversation

yusefnapora
Copy link
Contributor

We got hit by this recently during the rollout of tiered pricing, so I decided to pick it up this morning. Closes #1367

@yusefnapora yusefnapora temporarily deployed to production October 10, 2022 16:11 Inactive
@vasco-santos
Copy link
Member

Thanks @yusefnapora ❤️

@yusefnapora yusefnapora merged commit 6103e99 into main Oct 17, 2022
@yusefnapora yusefnapora deleted the chore/db-ids-js-maxint branch October 17, 2022 18:46
gobengo pushed a commit that referenced this pull request Oct 18, 2022
🤖 I have created a release *beep* *boop*
---


##
[7.9.1](api-v7.9.0...api-v7.9.1)
(2022-10-18)


### Bug Fixes

* issue with logging user being set to different value than underlying
user.id bigint::text
([#2042](#2042))
([9659ab0](9659ab0))
* update toucan-js and move to deps
([#2045](#2045))
([9de591d](9de591d))


### Other Changes

* use db ids > JS MAX_SAFE_INTEGER in test
([#2020](#2020))
([6103e99](6103e99))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Set SQL auto-incremement sequences to Javascript-unsafe integers for tests
2 participants