Fix gulp update plugin versions #3624
Merged
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.
Fixes #3623
This changes the
srcpath that locates all of the docs/plugins files. The problem was that the path was set relative to theconfigpackage directory, but thegulptask is running from root, so thesrccall was not picking up any docs/plugins files. The path is now relative to root.Running this task (via
npm run update-plugin-versionsornpm run changeset:versionfrom root) locally updates all of the package version numbers in docs/plugins as expected. But I didn't include the docs file changes here because I want to make sure that the docs files are updated during the release workflow, which should be triggered by thisconfigpackage release. One of the release steps callschangeset:version:Which calls the
update-plugin-versionstask:The release PR should contain all of the docs/plugins version updates. We will also need to trigger the publish docs action to make those changes live.