fix: report module version for go install - #7
Merged
Conversation
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.
Summary
go install ...@version--versionoutput and the CLI bannerdevvalueTest evidence
go vet ./...go test -ldflags='-linkmode=external' ./... -count=1go test -race -ldflags='-linkmode=external' ./pkg/... -count=1bash scripts/cross-build.shpatchlog devpatchlog v0.1.2Security and operations
The fallback reads only Go's embedded build metadata and performs no filesystem or network access. Release archive builds continue to use the immutable linker-injected tag. The real versioned-module path will be verified after publishing
v0.1.2.Proxy metrics remain diagnostic only and are not release gates.