Repository navigation
Correct the v4 to v5 migration guide - #501
Open
alexluckett wants to merge 3 commits into
Open
alexluckett wants to merge 3 commits into
alexluckett wants to merge 3 commits into
Conversation
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.
|
This branch has not been deployed
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
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.



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