-
Notifications
You must be signed in to change notification settings - Fork 738
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
Update morango and stop locking sync when db backend is postgres #9556
Update morango and stop locking sync when db backend is postgres #9556
Conversation
I'm not sure what's run with the linting check |
It's the |
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.
I left a small nitpick comment. Also I see this is targeted for v0.14.x. I guess this is going to be ported to v0.15.x and future releases too, isn't it?
|
||
services: | ||
postgres: | ||
image: postgres:12 |
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.
Taking into account that GCP uses v13 as default, and thinking in the future, wouldn it be best to use postgres:13?
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.
Our CI tests currently use 12, so I think good for it to be consistent.
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.
Our github actions (in newer release branches) use version 12, so this is consistent with that. Hopefully this shouldn't make much of a difference
Summary
v0.6.14
https://github.com/learningequality/morango/releases/tag/v0.6.14References
#9524
Reviewer guidance
Testing checklist
PR process
Reviewer checklist
yarn
andpip
)