chore(deps): bump tough-cookie, @analytics/google-analytics and node-sass in /frontend/amundsen_application/static #70
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.
Bumps tough-cookie to 4.1.3 and updates ancestor dependencies tough-cookie, @analytics/google-analytics and node-sass. These dependencies need to be updated together.
Updates
tough-cookie
from 4.0.0 to 4.1.3Release notes
Sourced from tough-cookie's releases.
... (truncated)
Commits
4ff4d29
4.1.3 release preparation, update the package and lib/version to 4.1.3. (#284)12d4747
Prevent prototype pollution in cookie memstore (#283)f06b72d
Fix documentation for store.findCookies, missing allowSpecialUseDomain proper...b1a8898
fix: allow set cookies with localhost (#253)ec70796
4.1.1 Patch -- allow special use domains by default (#250)d4ac580
fix: allow special use domains by default (#249)79c2f7d
4.1.0 release to NPM (#245)4fafc17
Prepare tough-cookie 4.1 for publishing (updated GitHub actions, move Dockerf...aa4396d
fix: distinguish between no samesite and samesite=none (#240)b8d7511
Modernize README (#234)Updates
@analytics/google-analytics
from 0.5.3 to 1.0.7Commits
56ce22c
chore(release): 🎉 🚀 [skip ci]e660491
refactor: attach user id if assigned2d72376
Merge pull request #351 from clarkieryan/master95a4dfb
chore(release): 🎉 🚀 [skip ci]6ace4f4
chore: dummy commit904e8bc
chore(release): 🎉 🚀 [skip ci]f483ad7
chore: lock file9efe41e
Merge pull request #367 from oddnavy/david/react-native-supportcc3e7c4
chore(release): 🎉 🚀 [skip ci]9b55708
docs: update GA docs for new id formalUpdates
node-sass
from 5.0.0 to 9.0.0Release notes
Sourced from node-sass's releases.
... (truncated)
Commits
87f3899
feat: Node 20 support (#3355)06ae4c7
build(deps): bump coverallsapp/github-action from 2.0.0 to 2.1.0 (#3350)e069f73
build(deps): bump coverallsapp/github-action from 1.2.0 to 2.0.0c34837d
build(deps): bump coverallsapp/github-action from 1.1.3 to 1.2.0ee13eb9
8.0.098e75b3
feat: Node 18 and 19 support and drop Node 17 (#3257)e9bb866
Bump node-gyp and nan for node 19 support (#3314)ab7840b
Fix binaries being partially downloaded (#3313)d595abf
7.0.33b556c1
7.0.2You can trigger a rebase of this PR by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.