-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/vuln: release version v0.1.0 #59686
Comments
Change https://go.dev/cl/485978 mentions this issue: |
Change https://go.dev/cl/485979 mentions this issue: |
Change https://go.dev/cl/487076 mentions this issue: |
x/vuln will soon start tagging releases, but does not want automatic tagging yet, only manual tags. However, as soon as the first tag is created then the repo will become eligible for automatic tagging. Add an explicit ignore for x/vuln to the task to avoid eligibility. This isn't ideal because the single tag task also uses the ignore list, so tags must be created manually, but this unblocks the process. For golang/go#59686. Change-Id: Iac190e1da5edd328aacdb001b7ef6acfefafdb98 Reviewed-on: https://go-review.googlesource.com/c/build/+/485978 TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Heschi Kreinick <[email protected]> Run-TryBot: Michael Pratt <[email protected]>
Change https://go.dev/cl/525655 mentions this issue: |
x/vuln opted out of automatic tagging, but there's no reason for it not to receive automatic updates. Also see a motivating data point captured in https://go.dev/issue/56530#issuecomment-1342988547. Now that there's a more fine-grained method of controlling whether to tag a repo, move the decision there and stop ignoring the entire vuln repo. For golang/go#59686. For golang/go#56530. Change-Id: I32815b3d52d7bd2e601b4eae0290008b33eefbec Reviewed-on: https://go-review.googlesource.com/c/build/+/525655 Reviewed-by: Dmitri Shuralyov <[email protected]> Reviewed-by: Heschi Kreinick <[email protected]> Auto-Submit: Dmitri Shuralyov <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]>
This issue tracks progress toward releasing x/[email protected].
The text was updated successfully, but these errors were encountered: