Tag api submodule
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
### Proposal
The Nomad API is used in a number of other projects (Traefik, Diun, Prometheus, etc...) however the module `github.com/hashicorp/nomad/api` has no tagged versions. Is it possible to create release tags for the API? An `api/v1.7.2` tag would be great, but it is probably worth some policy on when to tag an API module release.
### Use-cases
Building projects dependent on Nomad API without having to pin shas.
### Attempted Solutions
Pinning specific shas
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing how the github.com/hashicorp/nomad/api module is currently versioned and how Nomad release tags are created. Define a tagging policy for the API module, including whether an api/v1.7.2 tag should be created; done means dependent projects can use a released API version instead of pinning a commit SHA.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100