-
Notifications
You must be signed in to change notification settings - Fork 0
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
Explicitly version node
and prisma
in the migrate image
#879
Conversation
958af7d
to
689f79f
Compare
220792c
to
7e0ef79
Compare
7e0ef79
to
6652bf0
Compare
This will require a subsequent PR bumping the commit hash, such as #883. |
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.
We should address the TODO ASAP.
# TODO: Keep the version automatically in sync with common/package.json | ||
RUN npm install [email protected] |
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.
Suspect this'll get annoying very quickly as Dependabot updates Prisma every week...
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.
Good point 👍
Simplest route might be to just COPY ./packages/common/package.json ...
and RUN npm install
. A multi-stage build could be used to drop all of the dependencies we don't care about.
What does this change?
node:20.11.1-alpine
image, which matches the.nvmrc
.[email protected]
, which matches the rest of the service-catalogue (specificallypackages/common/package.json
).Thanks @akash1810 for the heads up.
Why?
The versions of software used in the image should be the same as those used in the rest of the repo.
How has it been verified?
Tested on CODE via #883