v1.1.0 release prep: gosec bump, VERSION/CHANGELOG, tag-version.sh#16
Merged
Conversation
Upgrade github.com/securego/gosec/v2 v2.22.11 -> v2.27.1, the latest release still declaring go 1.25 so the tools module's go directive stays at 1.25.0 (no bump to 1.26). Transitive updates pulled in: golang.org/x/net 0.49.0->0.55.0, x/sync 0.19.0->0.20.0, x/text 0.34.0->0.37.0, x/tools 0.41.0->0.45.0, google.golang.org/grpc 1.75.0->1.81.1, genai 1.37.0->1.58.0, protobuf 1.36.8->1.36.11, and genproto/googleapis/rpc.
Introduce a VERSION file (v1.1.0, using Go module version syntax with a leading v to match the git release tags and tag-release.sh) and a Keep a Changelog CHANGELOG.md reconstructed from the v1.0.0..v1.0.7 tag history, with the pending release documented under [1.1.0]. Document the VERSION format and the tag-release.sh flow in CLAUDE.md.
Add a CHANGELOG bullet for the v1.1.0 logsentry Sentry payload change (values move from the removed Event.Extra to the "log" context; reserved "type" key sent as "type_"), and correct CLAUDE.md to note test-workspace.sh also skips the examples module for gosec.
tag-version.sh tags the root, goslog/, and logsentry/ modules with the version read from the VERSION file instead of a command-line argument, keeping the same module list, current-tag listing, and dry-run/confirm flow. Update the CLAUDE.md Releasing section and the CHANGELOG.
ungerik
changed the title
Only surface gosec output when it finds issues, instead of printing a scan summary on every clean run.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Prepares the v1.1.0 release and finishes the dependency/tooling cleanup.
VERSIONfile (v1.1.0, Go module version syntax) and a Keep a ChangelogCHANGELOG.mdreconstructed from thev1.0.0..v1.0.7tag history, with the pending release documented under[1.1.0].tag-release.sh(version passed as an argument) withtag-version.sh, which reads the version from theVERSIONfile while keeping the same module list, current-tag listing, and dry-run/confirm flow.securego/gosecto v2.27.1 (stays on Go 1.25, no go-directive bump), pulling alonggoogle.golang.org/grpc1.81.1 and assortedgolang.org/x/*andgoogle.golang.org/*updates. Supersedes Dependabot PR Bump google.golang.org/grpc from 1.75.0 to 1.79.3 in /tools #12.CLAUDE.mdfor AI coding agents (incl. a Releasing section) plus changelog notes for the logsentry payload change.Tagging via
./tag-version.shhappens after merge to master; no tags are pushed by this PR.