Update checksums in go.work.sum + tidy everything
#543
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
So this is going to be a small annoyance with workspaces. After cutting a new release, Go **really** wants to put the new checksums in `go.work.sum`, and even having the LSP running will update it for you automatically. If you revert the changes, the LSP will update them again, which will block you from rebasing and switching branches, which as you can imagine, is great fun. So here, add the new checksums to `go.work.sum`, something which we'll probably have to do after each release goes out. Also, since we're doing a checksum change anyway, I also ran `make tidy` to clean up all the package `go.sum` files.
brandur
force-pushed
the
brandur-update-go-work-sum
branch
from
ae05da7
to
6a3a418
Compare
bgentry
approved these changes
Aug 21, 2024
|
ty. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So this is going to be a small annoyance with workspaces. After cutting
a new release, Go really wants to put the new checksums in
go.work.sum, and even having the LSP running will update it for youautomatically. If you revert the changes, the LSP will update them
again, which will block you from rebasing and switching branches, which
as you can imagine, is great fun.
So here, add the new checksums to
go.work.sum, something which we'llprobably have to do after each release goes out.
Also, since we're doing a checksum change anyway, I also ran
make tidyto clean up all the package
go.sumfiles.