Skip to content

Correct the v4 to v5 migration guide - #501

Open
alexluckett wants to merge 3 commits into
feature/node-v26-supportfrom
docs/v5-migration-guide-fixes
Open

alexluckett wants to merge 3 commits into
feature/node-v26-supportfrom
docs/v5-migration-guide-fixes

Conversation

@alexluckett

@alexluckett alexluckett commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Makes the v4 to v5 migration guide match the code on the Node 26 branch and removes some unnecessary filler.

Add Node 26 to the supported Node.js range and say that v5 drops Node 22.
Name conditionEvaluations as a field that a strict v4 schema rejects,
because the plugin always sends it. Limit the map proxy note to upgrades
from a version before v4.22.0, which is where the path parameter came in.
Put the table rows in the same order as the sections.
A service that uses the v5 schemas accepts the new fields, so the risk
exists only while services still run the v4 schemas during the release.
How a service that reads submissions validates them, and when it
upgrades, belongs to that service. The schema section still lists the
changes to the schemas that the plugin exports.
@alexluckett
alexluckett added this pull request to stack #502 November 19, 2026 15:03
@sonarqubecloud

Copy link
Copy Markdown

This branch has not been deployed

No deployments
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