Skip to content

docs: note pre-1.0 versioning policy in CONTRIBUTING #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
amondnet merged 1 commit into from
Jul 23, 2026
+4 −0
Merged

docs: note pre-1.0 versioning policy in CONTRIBUTING #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,10 @@ deno test # run the test suite

We follow [Conventional Commits](https://www.conventionalcommits.org/): `type(scope): subject`, where `type` is one of `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, etc. Breaking changes include a `BREAKING CHANGE:` footer. Versioning and the changelog are generated automatically from these messages, so accurate types matter.

## Versioning

OpenHWP is pre-1.0. While the major version is `0`, behavior and APIs may change between releases. [release-please](https://github.com/googleapis/release-please) derives the next version from Conventional Commits: a `feat` bumps the minor, a `fix` bumps the patch, and — because the project is still `0.x` — a breaking change bumps the minor rather than the major. We cut `1.0.0` intentionally, not automatically.

## Pull requests

External contributions start with an issue or a discussion, not a PR. If a
Expand Down
Loading