Update content scope scripts to version 11.4.0 #6567
Closed
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
CDRussell
force-pushed
the
automated/update-content-scope-scripts-dependencies-11.4.0
branch
from
8196de6 to
acfdb61
Compare
Member
|
Superseded by #6575 |
CDRussell
deleted the
automated/update-content-scope-scripts-dependencies-11.4.0
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Task/Issue URL: https://app.asana.com/0/488551667048375/1211041492727687/f
This PR updates the content scope scripts dependency to the latest available version and copies the necessary files.
Tests will only run if something has changed in the
node_modules/@duckduckgo/content-scope-scriptsfolder.If only the package version has changed, there is no need to run the tests.
If tests have failed, see https://app.asana.com/0/1202561462274611/1203986899650836/f for further information on what to do next.
content-scope-scriptsfolder updateOnly
content-scope-scriptspackage update