v2.0.0-rc1

[ptdropper]

Support CycloneDX specification 1.6
breaking release to add support for this specification.

What's Changed

• chore: restructure project, fix packaging, add python CT for entry point by @jkowalleck in chore: restructure project, fix packaging, add python CT for entry point #52
• docs: fix package name by @jkowalleck in docs: fix package name #57
• ci: run tests by @jkowalleck in ci: run tests #58
• Handle empty cpe value by @ptdropper in Handle empty cpe value #60
• chore: add dependabot by @jkowalleck in chore: add dependabot #62
• tests: SCA with mypy by @jkowalleck in tests: SCA with mypy #63
• build: release process by @jkowalleck in build: release process #65
• Support user provided value manufacture and manufacturer by @ptdropper in Support user provided value manufacture and manufacturer #59
• chore(deps-dev): bump tox from 4.24.1 to 4.25.0 by @dependabot in chore(deps-dev): bump tox from 4.24.1 to 4.25.0 #73
• chore: remove codeQL workflow by @jkowalleck in chore: remove codeQL workflow #72
• chore(deps): bump packageurl-python from 0.14.0 to 0.16.0 by @dependabot in chore(deps): bump packageurl-python from 0.14.0 to 0.16.0 #70
• chore(deps): allow a wider range of dependency versions by @jkowalleck in chore(deps): allow a wider range of dependency versions #61
• Support CycloneDX 1.6 by @ptdropper in Support CycloneDX 1.6 #74
• docs: readme - remove duplicates by @jkowalleck in docs: readme - remove duplicates #82

New Contributors

• @dependabot made their first contribution in chore(deps-dev): bump tox from 4.24.1 to 4.25.0 #73

Full Changelog: v1.1.1...v2.0.0-rc1

---

This discussion was created from the release v2.0.0-rc1.

[ptdropper]

My first attempt at using github.com web interface to discuss how to do a release and what to do to make a proper release. Comments welcome.

[jkowalleck]

the original release notes were a bit off, probably due to auto-detect.
if was v1.2.0b1...v2.0.0-rc1. i took the liberty to to adjust it to v1.1.1...v2.0.0-rc1.

Seams like one needs to keep a keen eye on the auto-generation, when pre-releases were involved - then it tries to increment those change-logs from one pre-release to the other.
Never happened with regular releases.

[jkowalleck]

@ptdropper , from the releas log it is not clear what breaking changes are in the new version.

breaking release to add support for this specification.

I would phrase it like :

## BREAKING changes
 * Generates CycloneDX according to spec 1.6, was spec 1.4.