chore: upgrade Univer SDK to 1.0.0-rc.0 - #52
Merged
Merged
Conversation
Align every @UniverJs, @univerjs-pro, and @univer-cli dependency to 1.0.0-rc.0 with the renamed pnpm update:univer-sdk command. Tool contract changes: - Rename update:sdk to update:univer-sdk; it now aligns all three SDK scopes in one pass instead of only the Univer runtime cohort. - The updater strips every SDK override from pnpm-workspace.yaml and the 140 pre-existing overrides are removed; SDK overrides are no longer a supported way to hold mixed SDK versions together. - Self-versioned packages (@univerjs/icons, @univerjs-pro/cli-assets, @univerjs-pro/doc-typst-native-binding) keep their own exact versions. - Native bindings are never declared directly: engine-formula-rust and exchange-node wrappers move into the published runtime dependencies and carry their bindings transitively. The release manifest gate now maps each binding to its wrapper. rc.0 contract adaptation: - univerfile-sqlite: ChangesetRange is gone; getChangesets and getDraftChangesets return the changeset list directly with an optional range end, and the adapters implement the new getSnapshotInfo. - collab-gateway: GetChangesetsResult no longer carries latestRevision; the fetch-missing handlers drop it (the protocol field is optional).
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.
Summary
@univerjs,@univerjs-pro, and@univer-clidependency to1.0.0-rc.0(37 declarations) via the renamedpnpm update:univer-sdkcommand. The resolved graph is single-train: one version of@univerjs/core, one copy of each native binding.update:sdkis renamed toupdate:univer-sdkand now aligns all three SDK scopes in one pass instead of only the Univer runtime cohort. The updater strips every SDK override frompnpm-workspace.yaml; the 140 pre-existing overrides are removed and SDK overrides are no longer a supported mechanism. Self-versioned packages (@univerjs/icons,@univerjs-pro/cli-assets,@univerjs-pro/doc-typst-native-binding) keep their own exact versions.@univerjs-pro/engine-formula-rust-bindingand@univerjs-pro/exchange-node-bindingare removed from all manifests and are never imported directly. Theengine-formula-rustandexchange-nodewrappers become the published runtime dependencies and carry their bindings transitively (formula bindinginsiders.20260910, exchange binding0.1.2). The release manifest gate maps each binding to its wrapper, and the build/release scripts stay name-based with no pinned versions.rc.0 contract adaptation
univerfile-sqlite:ChangesetRangeno longer exists;getChangesets/getDraftChangesetsreturn the changeset list directly with an optional range end, and the adapters implement the newgetSnapshotInfo.collab-gateway:GetChangesetsResultno longer carrieslatestRevision; the fetch-missing handlers drop it (the protocol response field is optional in rc.0).Validation
pnpm checkfully green: format, lint, typecheck, locales, 545 tests across 9 suites (including the packaged-CLI e2e loop), andpack:check.Plugin version mismatchwarning (formula plugin vs core) is gone — zero occurrences across the test run.Docs: README (en/zh) and AGENTS.md updated to the new upgrade contract.