P2: Declare 1.0.0 + versioning & schema stability policy (#178)#198
Open
dkijania wants to merge 1 commit into
Open
P2: Declare 1.0.0 + versioning & schema stability policy (#178)#198dkijania wants to merge 1 commit into
dkijania wants to merge 1 commit into
Conversation
The package was pre-1.0 (0.0.6) with no documented stability guarantees, which public consumers need. - Bump version to 1.0.0 (package.json only — no tag; the actual release/publish remains a deliberate maintainer step via `npm version` + tag push). - Add docs/versioning.md: SemVer applied to the GraphQL schema / HTTP endpoints / config, a precise definition of breaking vs additive changes, a deprecation policy (@deprecated + one minor & 90 days before removal), and how the existing graphql-inspector "Check Schema" gate enforces it via the expected-breaking-change label. - Link the policy from the README. Closes #178. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QSuak9smCHbp4N17xjjLF6
dkijania
added
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Part of the production-readiness epic (#163). Closes #178.
The package was pre-1.0 (
0.0.6) with no documented stability guarantees — public consumers need them.Changes
1.0.0inpackage.json.docs/versioning.md— SemVer applied to the GraphQL schema / HTTP endpoints / config: a precise definition of breaking vs additive changes, a deprecation policy (@deprecated+ one minor & 90 days before removal), and how the existing graphql-inspector "Check Schema" gate enforces it via theexpected-breaking-changelabel.Important: this PR does not publish anything
The version bump is
package.json-only — no git tag, so no release is cut. Publishing is tag-triggered (npm version+git push --follow-tags) and remains a deliberate maintainer action. Treat merging this PR as the decision to declare 1.0; if you're not ready for that, hold the PR (the policy doc stands on its own). Sequence it after the other production-readiness PRs so 1.0.0 ships with them.Testing
Docs + version only.
prettier --debug-check .clean; build sane. No code changed.🤖 Generated with Claude Code