Update 3.x branch references to 4.x#292
Merged
Merged
Conversation
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.
The recent merge from 3.x carried that branch's references to the 3.x branch name onto 4.x, where they should instead refer to 4.x. This points the continuous integration step that retrieves the base commit for git diff at 4.x, sets the package.json lint and prettier scripts that operate on changed files to diff against 4.x, updates the release process note to push to 4.x, and switches the documentation links embedded in the credentials help URL, the configuration validation messages, and the deprecation log output to the blob/4.x path, with the matching unit test expectations updated to agree. The referenced documentation pages all exist on 4.x, so the links resolve, and the test/README.md examples already use relative links and need no change.