open-telemetry / open-telemetry/weaver
Detection of breaking changes and automation of version management for public APIs
Open
Nobody has claimed this yet.
ci/cd
help wanted
- Dominant language
- Rust
- Stars
- 486
- Forks
- 108
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 40
Description
Once the Semantic Convention Registry is released, we must detect any breaking changes in public APIs and automate the version management for these APIs.
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, test, or entry point is named. Start by reading the Semantic Convention Registry and the repository’s current public API and version-management design, then identify how breaking changes should be detected and which version updates should be automated. Done means the required behavior and its validation are defined and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100