-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Pin kopia to 0.18.2 #8472
Pin kopia to 0.18.2 #8472
Conversation
e839e75
to
2309326
Compare
Signed-off-by: Lyndon-Li <[email protected]>
2309326
to
3cd85f5
Compare
@kaovilai Please notice Golang version in |
@blackpiglet that's not ideal but works. 1.22.7 was not very recent. |
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.
Could we wait for kopia/kopia#4292 to get resolved?
We can let go this PR, so that we can test the integration with Kopia 0.18.2 earlier. During a release cycle, we bump up Kopia several times. So once Kopia upstream has a fixing commit, we will cherry-pick it. |
go 1.22.0 | ||
go 1.22.7 | ||
|
||
toolchain go1.22.9 |
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.
This is actually more problematic than the
go 1.22.7
line. It's added by go automatically when go <patch version>
is bumped via go get
.
We can either delete this manually or follow with go get toolchain@none
.
Pin kopia to 0.18.2