Skip to content

feat(runtime): Add option to disable Document Schema upgrades#26713

Draft
scottn12 wants to merge 2 commits intomicrosoft:mainfrom
scottn12:disableDocSchemaUpgradesOption
Draft

feat(runtime): Add option to disable Document Schema upgrades#26713
scottn12 wants to merge 2 commits intomicrosoft:mainfrom
scottn12:disableDocSchemaUpgradesOption

Conversation

@scottn12
Copy link
Contributor

@scottn12 scottn12 commented Mar 12, 2026

Description

This PR adds an option disableSchemaUpgrade to ContainerRuntimeOptions. When enabled, it will prevent the runtime from sending DocumentSchemaChange ops and will throw on incoming DocumentSchemaChange ops.

This is useful for applications that don't require schema upgrades, as it guarantees that no mid-session errors can arise from schema upgrades.

Misc

AB#53703
Spec

@github-actions
Copy link
Contributor

🔗 No broken links found! ✅

Your attention to detail is admirable.

linkcheck output


> fluid-framework-docs-site@0.0.0 ci:check-links /home/runner/work/FluidFramework/FluidFramework/docs
> start-server-and-test "npm run serve -- --no-open" 3000 check-links

1: starting server using command "npm run serve -- --no-open"
and when url "[ 'http://127.0.0.1:3000' ]" is responding with HTTP status code 200
running tests using command "npm run check-links"


> fluid-framework-docs-site@0.0.0 serve
> docusaurus serve --no-open

[SUCCESS] Serving "build" directory at: http://localhost:3000/

> fluid-framework-docs-site@0.0.0 check-links
> linkcheck http://localhost:3000 --skip-file skipped-urls.txt

Crawling...

Stats:
  257792 links
    1822 destination URLs
    2063 URLs ignored
       0 warnings
       0 errors


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.

1 participant