prometheus / prometheus/client_java
Switch Micrometer compatibility workflow to upstream once typed-descriptor path becomes default
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 833
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 86
Description
The temporary typed-descriptor leg in .github/workflows/micrometer-compatibility.yml should be removed once Micrometer switches its Prometheus client integration to the typed-descriptor path by default.
Follow-up for PR #2123.
Acceptance criteria:
- remove the temporary opt-in compatibility leg that targets
zeitlinger/micrometer - keep the workflow validating the default upstream Micrometer path only
- remove any temporary TODO/comment added for this rollout tracking
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
Open .github/workflows/micrometer-compatibility.yml and inspect the temporary typed-descriptor compatibility leg targeting zeitlinger/micrometer, along with any rollout TODO or comment. Remove that temporary configuration while preserving validation of the default upstream Micrometer path, then review the workflow diff to confirm the acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 86/100