micrometer-metrics / micrometer-metrics/micrometer-github-workflows
micrometer-bom upgrade not included in generated tracing changelog
Open
Nobody has claimed this yet.
bug
- Dominant language
- Java
- Stars
- 0
- Forks
- 1
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Description
See tracing 1.13.12 milestone, for example. The generated changelog was:
## :lady_beetle: Bug Fixes
- Add extra checks for baggage header parsing [#1010](https://github.com/micrometer-metrics/tracing/pull/1010)
## :heart: Contributors
Thank you to all the contributors who worked on this release:
@songxiaosheng
It should have a dependency upgrade entry in the changelog for the micrometer-bom upgrade.
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 file or test is named. Start by locating the workflow or configuration that generates release changelogs, then compare the tracing 1.13.12 milestone with its generated output and the micrometer-bom upgrade. Done means dependency upgrade entries appear in generated changelogs when those upgrades are included.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100