CHORE: fix that release system
- Dominant language
- Python
- Stars
- 7
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
we did not have any new features in a long time.
so this was no issue so far ...
the release system is outdated: it no longer works. see for example:
goals
- have the release peocess working
- migrate to https://github.com/python-semantic-release/python-semantic-release v10
- see https://github.com/CycloneDX/cyclonedx-python-lib/blob/af0059d8fb6c9f8cc437f6c210487d131a6f658f/pyproject.toml#L128-L156
- dont trigger releases on every push to master, but only on manual innovation
- see https://github.com/CycloneDX/cyclonedx-python-lib/blob/main/.github/workflows/release.yml
Contributor guide
Research direction
Start by examining the repository's release configuration and compare it with the referenced pyproject.toml sections and .github/workflows/release.yml example. Check the linked failed Actions run to understand the current breakage. Done means the release process works with python-semantic-release v10 and runs only through manual triggering rather than every push to master.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd, release
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100