Skip to content

Update README status: released, v0.x series #24

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
hstern merged 1 commit into from
Jun 21, 2026
Merged

Update README status: released, v0.x series #24

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
13 changes: 8 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,14 @@ A Go library implementing

[rfc9493]: https://www.rfc-editor.org/rfc/rfc9493.html

> **Status: pre-release.** API surface is being shaped against RFC 9493
> §3 with the goal of byte-stable round-trip on every spec example.
> First tag will be `v0.1.0`. The module path
> `github.com/hstern/go-subjectid` is stable from the first commit; do
> not depend on the repo until `v0.1.0` is tagged.
> **Status: released, `v0.x`.** Latest tag `v0.2.0`. The API is tagged
> and usable, achieving byte-stable round-trip on every RFC 9493 §3
> example. While the library is in the `v0.x` series a minor release
> may still make breaking changes (per SemVer's `0.x` convention) — see
> [`CHANGELOG.md`](CHANGELOG.md) before upgrading. The module path
> `github.com/hstern/go-subjectid` has been stable since the first
> commit. A `v1.0.0` API-stability commitment will follow once the
> surface settles.

## What it is

Expand Down
Loading