-
Notifications
You must be signed in to change notification settings - Fork 15
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This adds a utility that can add and remove `replace` statements from a set of go.mod files. This builds on previous developments in this repo -- continues relying on a go.work file being checked in. The release tools will remove replace statements. The `genotelarrowcol` tool will add replace statements. This PR includes the results of ``` make prepare-release RELEASE_CANDIDATE=v0.8.0 PREVIOUS_VERSION=v0.7.0 MODSET=beta ``` which updates the go.mod files with an unreleased version, such that `go work sync` cannot succeed. It will succeed again after the release is pushed. It was difficult to untangle several changes from happening at once. 1. The release v0.7.0 was improperly made, so the go tools want to update all .sum files with the actual sum of those tags. 2. The ocb tool at v0.88.0 would insert a necessary replace statement, so we needed v0.89.x The change to v0.89.x was carried out using `make genotalarrowcol` which now runs `go work sync`, resulting in all modules receiving the update to v0.89.x. However, to avoid this sort of problem in the future, the ocb version is now hard-coded in the Dockerfile and Makefile.
- Loading branch information
Showing
31 changed files
with
6,030 additions
and
1,759 deletions.
There are no files selected for viewing
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
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
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
Oops, something went wrong.