x/website: ref/mod should mention +dirty

[xnox]

Go version

go1.24

Output of go env in your module/workspace:

N/A

What did you do?

Build binary and inspect its version

What did you see happen?

The version reported for the module is not documented in any of the specs as to what it means

# go version -m /usr/bin/pulumi  | grep -e pulumi
/usr/bin/pulumi: go1.24.0
	path	github.com/pulumi/pulumi/pkg/v3/cmd/pulumi
	mod	github.com/pulumi/pulumi/pkg/v3	v3.152.0+incompatible+dirty	

The module version is v3.1152.0+incompatible+dirty and the spec at https://go.dev/ref/mod#versions does not specify what "+dirty" means, or that two pluses are allowed.

What did you expect to see?

I expected https://go.dev/ref/mod#versions to be updated to explain what "+dirty" means, and what "+incompatible+dirty" means, and what the ordering of these flags are (ie. if +dirty+incompatible is or isn't allowed)

Also do we even need +dirty, given we already have vcs.modified=true|false field as well.

[xnox]

Note:

• cmd/go: +dirty in version stamping doesn't combine well with +incompatible #71971

Which highlights that a valid semver build metadata (after plus) should be dot separate fields as in +incompatible.dirty

[gabyhelp]

Related Issues

• cmd/go: +dirty in version stamping doesn't combine well with +incompatible #71971

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[prattmic]

cc @matloob @samthanawalla