Skip to content

docs(architecture): add API Stability section clarifying module semver policy#3422

Merged
dominikschulz merged 1 commit intogopasspw:masterfrom
dimension-zero:docs/pkg-api-stability
May 4, 2026
Merged

docs(architecture): add API Stability section clarifying module semver policy#3422
dominikschulz merged 1 commit intogopasspw:masterfrom
dimension-zero:docs/pkg-api-stability

Conversation

@dimension-zero
Copy link
Copy Markdown
Contributor

Summary

ARCHITECTURE.md already noted that semver applies to the CLI only and called it "not ideal," but gave consumers of pkg/gopass no actionable guidance on how to protect themselves from silent breaking changes.

This PR adds an API Stability section (inserted between the semver note and ### docs/backends) that:

  • States the current policy explicitly: no module-level semver guarantee
  • Points to pkg/gopass/doc.go's existing instability warning as the canonical signal
  • Gives three concrete steps for consumers (pin, watch CHANGELOG, treat all pkg/ changes as potentially breaking)
  • Links to issue docs(adr): define API stability contract for pkg/gopass #3414 where the longer-term ADR decision is tracked

No behaviour change. Documentation only.

Test plan

  • Markdown renders correctly — section sits between the semver note and ### docs/backends
  • No broken links

…r policy

The existing semver note acknowledged the CLI-only versioning decision
but gave consumers no actionable guidance. The new section states the
current policy explicitly, tells pkg/ consumers how to protect themselves
(pin, watch CHANGELOG), and points to the open ADR issue for the
longer-term resolution.
@dominikschulz dominikschulz merged commit ac6114f into gopasspw:master May 4, 2026
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants