Skip to content

Pin nexusguard to shield v1.9.0 - #53

Merged
juicycleff merged 1 commit into
mainfrom
chore/nexusguard-shield-v1.9.0
Oct 27, 2026
Merged

juicycleff merged 1 commit into
mainfrom
chore/nexusguard-shield-v1.9.0

Conversation

@juicycleff

Copy link
Copy Markdown
Contributor

This pins nexusguard to the shield release it was written for. Until now its go.mod required shield v1.8.1 and only built through the local go.work, which a go get from outside the repo never sees.

Now it requires github.com/xraph/shield v1.9.0. A plain go mod tidy works again, so the tidy -e workaround isn't needed any more. The rest of the go.sum churn is two golang.org/x bumps that came in with the release.

With GOWORK=off in integrations/nexusguard, go vet, go test -race and golangci-lint all pass, with 0 issues.

Once this merges, release.yml with tag=integrations/nexusguard/v1.9.0 cuts the module's tag.

The module required shield v1.8.1 and built only through the local workspace. It now requires the released v1.9.0, so a plain go get resolves the shield it was written against.
@juicycleff
juicycleff merged commit 251fddc into main Oct 27, 2026
13 checks passed
@juicycleff
juicycleff deleted the chore/nexusguard-shield-v1.9.0 branch October 27, 2026 23:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant