ci(v2): add release configuration for v2 module

Doug Barrettrequested to merge
db-v2-release-config into master

Context

The v2 module (gitlab.com/gitlab-org/labkit/v2) lives in a subdirectory with its own go.mod. The Go module proxy requires tags in the format v2/vX.Y.Z for subdirectory modules. The existing .releaserc.json only handles root module releases with standard vX.Y.Z tags.

Without this, v2 cannot be released as a versioned Go module.

What's in this MR?

  • v2/.releaserc.json: semantic-release config with tagFormat: "v2/v${version}" so tags match the Go module proxy convention
  • .gitlab-ci.yml: adds a release-v2 job in the release stage that runs npx semantic-release --extends ./v2/.releaserc.json on the main branch

Open questions

  • semantic-release's commit-analyzer will analyze all commits on main, not just v2-scoped ones. A future improvement could filter by commit scope (e.g. only feat(v2/*), fix(v2/*)) to avoid releasing v2 when only v1 changes land. For now, an extra no-op release is harmless.

Merge request reports