Dev docs/standards/document versioning components refactor#16479
Closed
Dev docs/standards/document versioning components refactor#16479
Conversation
Add spec metadata (version, status, changelog) and RFC 2119 components to all SDK standards pages, following the format established in sdk/telemetry/check-ins. Changes: - Add spec_id, spec_version, spec_status, spec_platforms frontmatter - Add spec_changelog with descriptive summaries - Add SpecRfcAlert, SpecMeta components at top - Add SpecChangelog component at bottom All standards set to v1.0.0 candidate status with dates from git history. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Renames Spec* components to purpose-based names that work across specifications, standards, playbooks, and documentation. Organizes versioning components in dedicated document-versioning/ directory following existing codebase patterns. - SpecRfcAlert → RfcComplianceAlert - SpecMeta → VersionMeta - SpecChangelog → VersionChangelog - SpecSection → VersionedSection Updates 8 MDX files and component registry. Maintains identical functionality. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
keep current naming |
dingsdax
deleted the
dev-docs/standards/document-versioning-components-refactor
branch
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.
DESCRIBE YOUR PR
Tell us what you're changing and why. If your PR resolves an issue, please link it so it closes automatically.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES