camunda / camunda/orchestration-cluster-api-python
Automated checks for breaking changes with minor release
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 15m
- Merged PRs (30d)
- 20
Description
This issue has no description.
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
The issue body names no files, tests, or entry points. First clarify which release workflow performs the checks and what counts as a breaking change; done should include automated coverage that prevents a minor release when breaking changes are detected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100