fix: production hardening (tok 0.1.0 CHANGELOG, trace panic, pin gosec/govulncheck, gosec enforcing)#25
Merged
Merged
Conversation
…c/govulncheck, gosec enforcing)
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
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.
Production Readiness Fixes (9-May-2026)
## [0.1.0]header and moved Unreleased content, now all ecosystem repos have consistent version docsfmt.Errorfgovulncheck@v1.1.4andgosec@v2.22.4across all 11 repos; removedcontinue-on-error: truefrom eyrie gosec, making it an enforcing jobAll 11 repos are now:
• Clean on main (no uncommitted/untracked changes)
• In sync with origin/main (0/0 ahead-behind)
• CI green on HEAD (including Scorecard where applicable)
• Version-consistent (0.1.0 project version, Go 1.26.4 toolchain)
• Properly integrated (hawk/external submodules aligned, cross-repo pins valid)
Ready for merge and promotion to production.
Required Checks