Closed dependabot[bot] closed 2 days ago
@KoWeiJAC how do we know that the major version update of google cloud storage works? Can you test file uploads using the local emulator?
@KoWeiJAC how do we know that the major version update of google cloud storage works? Can you test file uploads using the local emulator?
@drieJAC Good point, I've tested the uploads with local emulator, it worked. But I checked the google storage again, found it is not an dependency of firebase storage. It is used in virus scanner for setting meta data of scanned files. I'll check if it is possible to test it in local or dev environment.
@drieJAC @tomlovesgithub
I tested the virus scanner with google cloud storage v7.x in develop environment, it worked.
I also upgraded Node JS in google-app-engine/virus-scanning-node/Dockerfile
to node:20-bookworm
for the image can build successfully, the original one (node:10.15-stretch) is too old, some of Debian packages are not found.
How to test:
google-app-engine/virus-scanning-node/README.md
instruction, set up gcloud and run gcloud app deploy
, it will build image and deploy onto GCP https://console.cloud.google.com/appengine/services?serviceId=malware-scanner&versionId=20240926t115741&project=digital-platform-developSCAN_SERVICE_URL: 'https://malware-scanner-dot-digital-platform-develop.appspot.com/scan'
and PROJECT_ID: 'digital-platform-develop'
in nodeScripts/shared/config.js
filenpm run nodeScript runScannerTest
, it should fetch test files and pass tests
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version
or @dependabot ignore this minor version
.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
Bumps tough-cookie from 2.5.0 to 4.1.3. Removes
node-forge
Updates@google-cloud/storage
from 3.5.0 to 7.12.1Release 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)Maintainer changes
This version was pushed to npm by awaterma, a new releaser for tough-cookie since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 show