[finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR #13893

Closed
#14211
Closed
[finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR#13893
#14211
Assignees
baozhoutao
Labels
documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3

Description

@claude
claude
bot
opened on Aug 31, 2026

Filed from the work on #13779, which corrected only the page's concluding disclaimer. The rest of the page — and one page outside it — carry the same defect in the same direction, and were deliberately left untouched there to keep that diff scoped.

The defect

The repo's operative versioning rule today is the launch-window convention: every published @objectstack/* package sits in one Changesets fixed group (69 packages, check:changeset-fixed), and a breaking change ships as MINOR rather than burning a MAJOR. It is mechanically enforced by scripts/check-changeset-no-major.mjs, which is currently in its enforcing state (.changeset/pre.json is absent) and reports 559 pending changesets, 0 declaring a major. packages/spec/CHANGELOG.md shows 17.2.0's Minor Changes section carrying an entry marked **BREAKING**.

Three surfaces still tell customers the opposite.

1. content/docs/protocol/backward-compatibility.mdx — the SemVer table

The MINOR row's Guarantee reads "Existing code continues to work". #13779 added an overriding section at the page's conclusion, but the table itself is unqualified where a reader meets it first.

2. Same page — the Breaking Change Policy table and process

Every row of the breaking-change table maps to Version Impact: MAJOR; the process section ends "Breaking change ships in the next MAJOR version"; and the deprecation timeline's Phase 3 is "Removal (next MAJOR release)". All three are contradicted by shipped releases — 17.2.0 retired http_request_errors_total in a MINOR under ADR-0049, and 15.1.0 removed tenancy.strategy and tenancy.crossTenantAccess in a MINOR.

Also unverified on that page, and worth a look in the same pass: the Breaking Change Process claims a "Minimum 30-day community review period". No mechanism for it was found in the repo.

3. content/docs/releases/index.mdx — the Versioning policy section

Minor releases add capabilities without breaking existing metadata or code.

This is the same false statement on a second customer-facing page. ⚠️ That directory is fenced by AGENTS.md (never edited in a code PR), so it needs its own docs-only change — which is part of why this is a separate card.

Why it is worth a card

Same reasoning triage applied to #13779: this is what a customer reads to judge upgrade risk, and the version number is not the safety signal the pages say it is. The v17 release notes already say so plainly — "17.1.0 and 17.2.0 are minors by version number, not by blast radius" — so the drift is between the release notes and the policy pages, not inside the project's own understanding.

Not addressed here

#13779 covers the concluding disclaimer only and does not touch any of the above.

Generated by Claude Code

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    , 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
     blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

    Skip to content
    [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR #13893
    Closed
    #14211
    Closed
    [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR#13893
    #14211
    Assignees
    baozhoutao
    Labels
    documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
    Description
    @claude
    claude
    bot
    opened on Aug 31, 2026
    Filed from the work on #13779, which corrected only the page's concluding disclaimer. The rest of the page — and one page outside it — carry the same defect in the same direction, and were deliberately left untouched there to keep that diff scoped.
    The defect
    The repo's operative versioning rule today is the launch-window convention: every published @objectstack/* package sits in one Changesets fixed group (69 packages, check:changeset-fixed), and a breaking change ships as MINOR rather than burning a MAJOR. It is mechanically enforced by scripts/check-changeset-no-major.mjs, which is currently in its enforcing state (.changeset/pre.json is absent) and reports 559 pending changesets, 0 declaring a major. packages/spec/CHANGELOG.md shows 17.2.0's Minor Changes section carrying an entry marked **BREAKING**.
    Three surfaces still tell customers the opposite.
    1. content/docs/protocol/backward-compatibility.mdx — the SemVer table
    The MINOR row's Guarantee reads "Existing code continues to work". #13779 added an overriding section at the page's conclusion, but the table itself is unqualified where a reader meets it first.
    2. Same page — the Breaking Change Policy table and process
    Every row of the breaking-change table maps to Version Impact: MAJOR; the process section ends "Breaking change ships in the next MAJOR version"; and the deprecation timeline's Phase 3 is "Removal (next MAJOR release)". All three are contradicted by shipped releases — 17.2.0 retired http_request_errors_total in a MINOR under ADR-0049, and 15.1.0 removed tenancy.strategy and tenancy.crossTenantAccess in a MINOR.
    Also unverified on that page, and worth a look in the same pass: the Breaking Change Process claims a "Minimum 30-day community review period". No mechanism for it was found in the repo.
    3. content/docs/releases/index.mdx — the Versioning policy section
    Minor releases add capabilities without breaking existing metadata or code.
    This is the same false statement on a second customer-facing page. ⚠️ That directory is fenced by AGENTS.md (never edited in a code PR), so it needs its own docs-only change — which is part of why this is a separate card.
    Why it is worth a card
    Same reasoning triage applied to #13779: this is what a customer reads to judge upgrade risk, and the version number is not the safety signal the pages say it is. The v17 release notes already say so plainly — "17.1.0 and 17.2.0 are minors by version number, not by blast radius" — so the drift is between the release notes and the policy pages, not inside the project's own understanding.
    Not addressed here
    #13779 covers the concluding disclaimer only and does not touch any of the above.
    Generated by Claude Code
    Metadata
    Metadata
    Assignees
    Labels
    documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
    Type
    No type
    Projects
    No projects
      Milestone
      No milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions
      
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

      Skip to content
      [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR #13893
      Closed
      #14211
      Closed
      [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR#13893
      #14211
      Assignees
      baozhoutao
      Labels
      documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
      Description
      @claude
      claude
      bot
      opened on Aug 31, 2026
      Filed from the work on #13779, which corrected only the page's concluding disclaimer. The rest of the page — and one page outside it — carry the same defect in the same direction, and were deliberately left untouched there to keep that diff scoped.
      The defect
      The repo's operative versioning rule today is the launch-window convention: every published @objectstack/* package sits in one Changesets fixed group (69 packages, check:changeset-fixed), and a breaking change ships as MINOR rather than burning a MAJOR. It is mechanically enforced by scripts/check-changeset-no-major.mjs, which is currently in its enforcing state (.changeset/pre.json is absent) and reports 559 pending changesets, 0 declaring a major. packages/spec/CHANGELOG.md shows 17.2.0's Minor Changes section carrying an entry marked **BREAKING**.
      Three surfaces still tell customers the opposite.
      1. content/docs/protocol/backward-compatibility.mdx — the SemVer table
      The MINOR row's Guarantee reads "Existing code continues to work". #13779 added an overriding section at the page's conclusion, but the table itself is unqualified where a reader meets it first.
      2. Same page — the Breaking Change Policy table and process
      Every row of the breaking-change table maps to Version Impact: MAJOR; the process section ends "Breaking change ships in the next MAJOR version"; and the deprecation timeline's Phase 3 is "Removal (next MAJOR release)". All three are contradicted by shipped releases — 17.2.0 retired http_request_errors_total in a MINOR under ADR-0049, and 15.1.0 removed tenancy.strategy and tenancy.crossTenantAccess in a MINOR.
      Also unverified on that page, and worth a look in the same pass: the Breaking Change Process claims a "Minimum 30-day community review period". No mechanism for it was found in the repo.
      3. content/docs/releases/index.mdx — the Versioning policy section
      Minor releases add capabilities without breaking existing metadata or code.
      This is the same false statement on a second customer-facing page. ⚠️ That directory is fenced by AGENTS.md (never edited in a code PR), so it needs its own docs-only change — which is part of why this is a separate card.
      Why it is worth a card
      Same reasoning triage applied to #13779: this is what a customer reads to judge upgrade risk, and the version number is not the safety signal the pages say it is. The v17 release notes already say so plainly — "17.1.0 and 17.2.0 are minors by version number, not by blast radius" — so the drift is between the release notes and the policy pages, not inside the project's own understanding.
      Not addressed here
      #13779 covers the concluding disclaimer only and does not touch any of the above.
      Generated by Claude Code
      Metadata
      Metadata
      Assignees
      Labels
      documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
      Type
      No type
      Projects
      No projects
        Milestone
        No milestone
        Relationships
        None yet
        Development
        No branches or pull requests
        Issue actions
        
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

        Skip to content
        [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR #13893
        Closed
        #14211
        Closed
        [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR#13893
        #14211
        Assignees
        baozhoutao
        Labels
        documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
        Description
        @claude
        claude
        bot
        opened on Aug 31, 2026
        Filed from the work on #13779, which corrected only the page's concluding disclaimer. The rest of the page — and one page outside it — carry the same defect in the same direction, and were deliberately left untouched there to keep that diff scoped.
        The defect
        The repo's operative versioning rule today is the launch-window convention: every published @objectstack/* package sits in one Changesets fixed group (69 packages, check:changeset-fixed), and a breaking change ships as MINOR rather than burning a MAJOR. It is mechanically enforced by scripts/check-changeset-no-major.mjs, which is currently in its enforcing state (.changeset/pre.json is absent) and reports 559 pending changesets, 0 declaring a major. packages/spec/CHANGELOG.md shows 17.2.0's Minor Changes section carrying an entry marked **BREAKING**.
        Three surfaces still tell customers the opposite.
        1. content/docs/protocol/backward-compatibility.mdx — the SemVer table
        The MINOR row's Guarantee reads "Existing code continues to work". #13779 added an overriding section at the page's conclusion, but the table itself is unqualified where a reader meets it first.
        2. Same page — the Breaking Change Policy table and process
        Every row of the breaking-change table maps to Version Impact: MAJOR; the process section ends "Breaking change ships in the next MAJOR version"; and the deprecation timeline's Phase 3 is "Removal (next MAJOR release)". All three are contradicted by shipped releases — 17.2.0 retired http_request_errors_total in a MINOR under ADR-0049, and 15.1.0 removed tenancy.strategy and tenancy.crossTenantAccess in a MINOR.
        Also unverified on that page, and worth a look in the same pass: the Breaking Change Process claims a "Minimum 30-day community review period". No mechanism for it was found in the repo.
        3. content/docs/releases/index.mdx — the Versioning policy section
        Minor releases add capabilities without breaking existing metadata or code.
        This is the same false statement on a second customer-facing page. ⚠️ That directory is fenced by AGENTS.md (never edited in a code PR), so it needs its own docs-only change — which is part of why this is a separate card.
        Why it is worth a card
        Same reasoning triage applied to #13779: this is what a customer reads to judge upgrade risk, and the version number is not the safety signal the pages say it is. The v17 release notes already say so plainly — "17.1.0 and 17.2.0 are minors by version number, not by blast radius" — so the drift is between the release notes and the policy pages, not inside the project's own understanding.
        Not addressed here
        #13779 covers the concluding disclaimer only and does not touch any of the above.
        Generated by Claude Code
        Metadata
        Metadata
        Assignees
        Labels
        documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
        Type
        No type
        Projects
        No projects
          Milestone
          No milestone
          Relationships
          None yet
          Development
          No branches or pull requests
          Issue actions
          
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

          Skip to content
          [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR #13893
          Closed
          #14211
          Closed
          [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR#13893
          #14211
          Assignees
          baozhoutao
          Labels
          documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
          Description
          @claude
          claude
          bot
          opened on Aug 31, 2026
          Filed from the work on #13779, which corrected only the page's concluding disclaimer. The rest of the page — and one page outside it — carry the same defect in the same direction, and were deliberately left untouched there to keep that diff scoped.
          The defect
          The repo's operative versioning rule today is the launch-window convention: every published @objectstack/* package sits in one Changesets fixed group (69 packages, check:changeset-fixed), and a breaking change ships as MINOR rather than burning a MAJOR. It is mechanically enforced by scripts/check-changeset-no-major.mjs, which is currently in its enforcing state (.changeset/pre.json is absent) and reports 559 pending changesets, 0 declaring a major. packages/spec/CHANGELOG.md shows 17.2.0's Minor Changes section carrying an entry marked **BREAKING**.
          Three surfaces still tell customers the opposite.
          1. content/docs/protocol/backward-compatibility.mdx — the SemVer table
          The MINOR row's Guarantee reads "Existing code continues to work". #13779 added an overriding section at the page's conclusion, but the table itself is unqualified where a reader meets it first.
          2. Same page — the Breaking Change Policy table and process
          Every row of the breaking-change table maps to Version Impact: MAJOR; the process section ends "Breaking change ships in the next MAJOR version"; and the deprecation timeline's Phase 3 is "Removal (next MAJOR release)". All three are contradicted by shipped releases — 17.2.0 retired http_request_errors_total in a MINOR under ADR-0049, and 15.1.0 removed tenancy.strategy and tenancy.crossTenantAccess in a MINOR.
          Also unverified on that page, and worth a look in the same pass: the Breaking Change Process claims a "Minimum 30-day community review period". No mechanism for it was found in the repo.
          3. content/docs/releases/index.mdx — the Versioning policy section
          Minor releases add capabilities without breaking existing metadata or code.
          This is the same false statement on a second customer-facing page. ⚠️ That directory is fenced by AGENTS.md (never edited in a code PR), so it needs its own docs-only change — which is part of why this is a separate card.
          Why it is worth a card
          Same reasoning triage applied to #13779: this is what a customer reads to judge upgrade risk, and the version number is not the safety signal the pages say it is. The v17 release notes already say so plainly — "17.1.0 and 17.2.0 are minors by version number, not by blast radius" — so the drift is between the release notes and the policy pages, not inside the project's own understanding.
          Not addressed here
          #13779 covers the concluding disclaimer only and does not touch any of the above.
          Generated by Claude Code
          Metadata
          Metadata
          Assignees
          Labels
          documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
          Type
          No type
          Projects
          No projects
            Milestone
            No milestone
            Relationships
            None yet
            Development
            No branches or pull requests
            Issue actions
            
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

            Skip to content
            [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR #13893
            Closed
            #14211
            Closed
            [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR#13893
            #14211
            Assignees
            baozhoutao
            Labels
            documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
            Description
            @claude
            claude
            bot
            opened on Aug 31, 2026
            Filed from the work on #13779, which corrected only the page's concluding disclaimer. The rest of the page — and one page outside it — carry the same defect in the same direction, and were deliberately left untouched there to keep that diff scoped.
            The defect
            The repo's operative versioning rule today is the launch-window convention: every published @objectstack/* package sits in one Changesets fixed group (69 packages, check:changeset-fixed), and a breaking change ships as MINOR rather than burning a MAJOR. It is mechanically enforced by scripts/check-changeset-no-major.mjs, which is currently in its enforcing state (.changeset/pre.json is absent) and reports 559 pending changesets, 0 declaring a major. packages/spec/CHANGELOG.md shows 17.2.0's Minor Changes section carrying an entry marked **BREAKING**.
            Three surfaces still tell customers the opposite.
            1. content/docs/protocol/backward-compatibility.mdx — the SemVer table
            The MINOR row's Guarantee reads "Existing code continues to work". #13779 added an overriding section at the page's conclusion, but the table itself is unqualified where a reader meets it first.
            2. Same page — the Breaking Change Policy table and process
            Every row of the breaking-change table maps to Version Impact: MAJOR; the process section ends "Breaking change ships in the next MAJOR version"; and the deprecation timeline's Phase 3 is "Removal (next MAJOR release)". All three are contradicted by shipped releases — 17.2.0 retired http_request_errors_total in a MINOR under ADR-0049, and 15.1.0 removed tenancy.strategy and tenancy.crossTenantAccess in a MINOR.
            Also unverified on that page, and worth a look in the same pass: the Breaking Change Process claims a "Minimum 30-day community review period". No mechanism for it was found in the repo.
            3. content/docs/releases/index.mdx — the Versioning policy section
            Minor releases add capabilities without breaking existing metadata or code.
            This is the same false statement on a second customer-facing page. ⚠️ That directory is fenced by AGENTS.md (never edited in a code PR), so it needs its own docs-only change — which is part of why this is a separate card.
            Why it is worth a card
            Same reasoning triage applied to #13779: this is what a customer reads to judge upgrade risk, and the version number is not the safety signal the pages say it is. The v17 release notes already say so plainly — "17.1.0 and 17.2.0 are minors by version number, not by blast radius" — so the drift is between the release notes and the policy pages, not inside the project's own understanding.
            Not addressed here
            #13779 covers the concluding disclaimer only and does not touch any of the above.
            Generated by Claude Code
            Metadata
            Metadata
            Assignees
            Labels
            documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
            Type
            No type
            Projects
            No projects
              Milestone
              No milestone
              Relationships
              None yet
              Development
              No branches or pull requests
              Issue actions
              
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

              Skip to content
              [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR #13893
              Closed
              #14211
              Closed
              [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR#13893
              #14211
              Assignees
              baozhoutao
              Labels
              documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
              Description
              @claude
              claude
              bot
              opened on Aug 31, 2026
              Filed from the work on #13779, which corrected only the page's concluding disclaimer. The rest of the page — and one page outside it — carry the same defect in the same direction, and were deliberately left untouched there to keep that diff scoped.
              The defect
              The repo's operative versioning rule today is the launch-window convention: every published @objectstack/* package sits in one Changesets fixed group (69 packages, check:changeset-fixed), and a breaking change ships as MINOR rather than burning a MAJOR. It is mechanically enforced by scripts/check-changeset-no-major.mjs, which is currently in its enforcing state (.changeset/pre.json is absent) and reports 559 pending changesets, 0 declaring a major. packages/spec/CHANGELOG.md shows 17.2.0's Minor Changes section carrying an entry marked **BREAKING**.
              Three surfaces still tell customers the opposite.
              1. content/docs/protocol/backward-compatibility.mdx — the SemVer table
              The MINOR row's Guarantee reads "Existing code continues to work". #13779 added an overriding section at the page's conclusion, but the table itself is unqualified where a reader meets it first.
              2. Same page — the Breaking Change Policy table and process
              Every row of the breaking-change table maps to Version Impact: MAJOR; the process section ends "Breaking change ships in the next MAJOR version"; and the deprecation timeline's Phase 3 is "Removal (next MAJOR release)". All three are contradicted by shipped releases — 17.2.0 retired http_request_errors_total in a MINOR under ADR-0049, and 15.1.0 removed tenancy.strategy and tenancy.crossTenantAccess in a MINOR.
              Also unverified on that page, and worth a look in the same pass: the Breaking Change Process claims a "Minimum 30-day community review period". No mechanism for it was found in the repo.
              3. content/docs/releases/index.mdx — the Versioning policy section
              Minor releases add capabilities without breaking existing metadata or code.
              This is the same false statement on a second customer-facing page. ⚠️ That directory is fenced by AGENTS.md (never edited in a code PR), so it needs its own docs-only change — which is part of why this is a separate card.
              Why it is worth a card
              Same reasoning triage applied to #13779: this is what a customer reads to judge upgrade risk, and the version number is not the safety signal the pages say it is. The v17 release notes already say so plainly — "17.1.0 and 17.2.0 are minors by version number, not by blast radius" — so the drift is between the release notes and the policy pages, not inside the project's own understanding.
              Not addressed here
              #13779 covers the concluding disclaimer only and does not touch any of the above.
              Generated by Claude Code
              Metadata
              Metadata
              Assignees
              Labels
              documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
              Type
              No type
              Projects
              No projects
                Milestone
                No milestone
                Relationships
                None yet
                Development
                No branches or pull requests
                Issue actions
                
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

                Skip to content
                [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR #13893
                Closed
                #14211
                Closed
                [finding] docs(protocol): the Backward Compatibility page's MAJOR/MINOR tables, and the releases Versioning policy, still say breaking changes take a MAJOR#13893
                #14211
                Assignees
                baozhoutao
                Labels
                documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
                Description
                @claude
                claude
                bot
                opened on Aug 31, 2026
                Filed from the work on #13779, which corrected only the page's concluding disclaimer. The rest of the page — and one page outside it — carry the same defect in the same direction, and were deliberately left untouched there to keep that diff scoped.
                The defect
                The repo's operative versioning rule today is the launch-window convention: every published @objectstack/* package sits in one Changesets fixed group (69 packages, check:changeset-fixed), and a breaking change ships as MINOR rather than burning a MAJOR. It is mechanically enforced by scripts/check-changeset-no-major.mjs, which is currently in its enforcing state (.changeset/pre.json is absent) and reports 559 pending changesets, 0 declaring a major. packages/spec/CHANGELOG.md shows 17.2.0's Minor Changes section carrying an entry marked **BREAKING**.
                Three surfaces still tell customers the opposite.
                1. content/docs/protocol/backward-compatibility.mdx — the SemVer table
                The MINOR row's Guarantee reads "Existing code continues to work". #13779 added an overriding section at the page's conclusion, but the table itself is unqualified where a reader meets it first.
                2. Same page — the Breaking Change Policy table and process
                Every row of the breaking-change table maps to Version Impact: MAJOR; the process section ends "Breaking change ships in the next MAJOR version"; and the deprecation timeline's Phase 3 is "Removal (next MAJOR release)". All three are contradicted by shipped releases — 17.2.0 retired http_request_errors_total in a MINOR under ADR-0049, and 15.1.0 removed tenancy.strategy and tenancy.crossTenantAccess in a MINOR.
                Also unverified on that page, and worth a look in the same pass: the Breaking Change Process claims a "Minimum 30-day community review period". No mechanism for it was found in the repo.
                3. content/docs/releases/index.mdx — the Versioning policy section
                Minor releases add capabilities without breaking existing metadata or code.
                This is the same false statement on a second customer-facing page. ⚠️ That directory is fenced by AGENTS.md (never edited in a code PR), so it needs its own docs-only change — which is part of why this is a separate card.
                Why it is worth a card
                Same reasoning triage applied to #13779: this is what a customer reads to judge upgrade risk, and the version number is not the safety signal the pages say it is. The v17 release notes already say so plainly — "17.1.0 and 17.2.0 are minors by version number, not by blast radius" — so the drift is between the release notes and the policy pages, not inside the project's own understanding.
                Not addressed here
                #13779 covers the concluding disclaimer only and does not touch any of the above.
                Generated by Claude Code
                Metadata
                Metadata
                Assignees
                Labels
                documentationImprovements or additions to documentationdomain:devxpriority:p2Medium: important, M3
                Type
                No type
                Projects
                No projects
                  Milestone
                  No milestone
                  Relationships
                  None yet
                  Development
                  No branches or pull requests
                  Issue actions