docs: add release.md#723
Conversation
|
The PR description has been updated. Please fill out the template for your PR to be reviewed. |
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
|
RELEASE.md
Outdated
| - **MINOR** (`x.y`) – Backwards‑compatible new features | ||
| - **MAJOR** (`x`) – Breaking API changes |
There was a problem hiding this comment.
As we've yet to do a major release this not exactly true, some 0.X minor releases have breaking changes afaik
There was a problem hiding this comment.
I wasn't aware but semver actually documents this with this rule and the next: https://semver.org/#spec-item-4
We should probably just include a disclaimer here anyways and explain our general process.
There was a problem hiding this comment.
I went with the simpler "link to semver and note that we note breaking changes" approach 😄
Signed-off-by: Paul S. Schweigert <paul@paulschweigert.com>
16dd0af
Misc PR
Type of PR
Description
Formally documents release process in repo
Testing