[mhagape]

Summary

A node manifest with runtimeConstraints: { exclude: [...] } is available in every runtime that ships later. Each new runtime then forces a manifest update just to opt the node back out. include doesn't have this problem, because a new runtime gets no node until a manifest lists it.

This PR marks the exclude variant of nodeRuntimeConstraintsManifestSchema as @deprecated and points the schema docs to include.

Impact

• Manifests that use exclude still parse, so nothing breaks at runtime.
• Code that reads constraints.exclude through the exported RuntimeConstraints type shows a deprecation strike-through in the editor, with the reason.
• Removing exclude is left for a later major release, after the manifests move to include.

Verification

• A probe file run through the TypeScript language service reports 'exclude' is deprecated (6385) when it reads c.exclude, and nothing when it reads c.include.
• tsc --noEmit reports 0 errors, Biome is clean, and the 15 schema tests pass.

🤖 Generated with Claude Code

[Copilot]

🟢 Approval recommended

The change is limited to documentation and deprecation metadata, with no runtime behavior changes or unresolved findings.

No open issues 🎉

What changed in this PR

Deprecates exclusion-based runtime constraints in Apollo React’s node manifest schema, encouraging explicit include lists so nodes are not automatically enabled in future runtimes.

Changes:

• Updates schema documentation to recommend include.
• Adds @deprecated documentation to exclude while preserving existing validation and runtime compatibility.

File	Description
packages/​apollo-react/​src/​canvas/​schema/​node-definition/​node-manifest.ts	Documents the exclude deprecation and its rationale without changing validation logic.

_{Review effort: Balanced}

[github-actions]

Dependency License Review

• ✅ 1957 package(s) scanned
• ✅ No license issues found
• ⚠️ 2 package(s) excluded (see details below)

License distribution

License	Packages
MIT	1721
ISC	91
Apache-2.0	57
BSD-3-Clause	28
BSD-2-Clause	23
BlueOak-1.0.0	8
MPL-2.0	4
CC0-1.0	4
MIT-0	3
MIT OR Apache-2.0	2
(MIT OR Apache-2.0)	2
Unlicense	2
LGPL-3.0-or-later	1
Python-2.0	1
CC-BY-4.0	1
(MPL-2.0 OR Apache-2.0)	1
Unknown	1
Artistic-2.0	1
(WTFPL OR MIT)	1
(BSD-2-Clause OR MIT OR Apache-2.0)	1
CC-BY-3.0	1
0BSD	1
(MIT OR CC0-1.0)	1
MIT AND ISC	1

Excluded packages

Package	Version	License	Reason
@img/sharp-libvips-linux-x64	1.3.4	LGPL-3.0-or-later	LGPL pre-built binary, not linked
khroma	2.1.0	Unknown	MIT per GitHub repo, missing license field in package.json

[github-actions]

📊 Coverage + size by package

Per-package coverage and bundle size on this PR. New-line coverage = of the source lines this PR adds or changes, the % hit by tests.

Package	Coverage	New-line coverage	Packed (gzip)	Unpacked	vs main
@uipath/apollo-core	—	—	42.02 MB	50.17 MB	±0
@uipath/apollo-react	58.4%	— (8 untracked)	8.14 MB	32.17 MB	±0
@uipath/apollo-ui-icons	—	—	2.86 MB	6.97 MB	±0
@uipath/apollo-vertex	—	—	—	—	—
@uipath/apollo-wind	—	—	810.7 KB	4.68 MB	−5 B
@uipath/ap-chat	85.8%	—	40.42 MB	45.71 MB	±0

_{"Coverage" is each package's own coverage.include scope (e.g. apollo-core instruments only scripts/). "Packed"/"Unpacked" come from npm pack --dry-run and only cover built packages — "—" means not measured this run (package not affected / not built). "vs main" is the packed (gzipped) delta against the last successful main build (the package-sizes artifact from the Release workflow); "—" there means no main baseline was available this run. The baseline is main's latest build, not this PR's exact merge-base, so it includes any drift since the branch diverged. Packages with no vitest config are omitted.}

[github-actions]

Storybook visual diff

⚠️ Visual changes detected: 15 changed, 4 added (of 406 compared, 387 unchanged). View report

Baseline is the deployed main Storybook, so changes merged to main after this branch was last updated can also appear here. Logs

Updated (PT): Oct 23, 2026, 07:07:40 AM