-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Create tool to pin locally replaced modules to latest trunk commit #15290
Conversation
Separating it to avoid potential merge conflicts when surrounding lines change as we expect CI to update its psuedo version.
I see you updated files related to
|
TODO
|
tools/gomod-required-updater/internal/updater/system_operator.go
Outdated
Show resolved
Hide resolved
Tests and linting should now be ran from the ci-core workflow.
AER Report: CI Core ran successfully ✅AER Report: Operator UI CI ran successfully ✅ |
Co-authored-by: Jordan Krage <[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.
Is this separate workflow necessary?
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.
Hm, it's pretty sparse right now. Would love to remove it. Would you suggest just throwing this as a step in ci-core.yml
?
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.
Well the make command already installs so what effect is this build meant to have?
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.
The goal would be to ensure that the build doesn't break but maybe unnecessary or it gets built in another way that I'm not aware of?
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.
It should already be covered by the normal CI as part of the root module. I.e. there should be a line for this package in the ci core test output
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.
Makes sense, removed in ccf2842.
…ub.com/smartcontractkit/chainlink into re-3199/updater-root-module-go.mod-ref
Run locally via:
make gomodslocalupdate