prometheus / prometheus/common
Prevent incompatibility issues between common and dependent repositories
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 295
- Forks
- 367
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 18
Description
Common is not a stable repository, but it is being used by others that are considered stable, like client_golang and Prometheus itself.
Last week we had an incompatibility problem between common and client_golang which forced us to rush and cut a new release. We don't want to tell prometheus/common "no more breaking changes!!!!!", but it would be nice if these changes could be communicated better when they happen.
One suggestion is to add a CI workflow that tries to build the latest stable release of client_golang and/or Prometheus on pull requests. The workflow doesn't need to be "Required to pass", but if merged with failures let's communicate with dependent projects within the Prometheus organization
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No specific files or tests are named. Start by reviewing the repository's current CI configuration and dependency setup, then determine how to build the latest stable client_golang and/or Prometheus releases against pull requests. Done means compatibility results are reported without being required, with failures available for communication to dependent projects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100