search

kurosame / glossary

Glossary App with React
https://glossary-kurosame.firebaseapp.com
MIT License
5 stars 0 forks source link

chore(deps): bump cacheable-request and firebase-tools #147

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Removes cacheable-request. It's no longer used after updating ancestor dependency firebase-tools. These dependencies need to be updated together.

Removes cacheable-request

Updates firebase-tools from 11.16.1 to 11.22.0

Release notes

Sourced from firebase-tools's releases.

v11.22.0

  • Refactors Functions Emulator. (#5422)
  • Fixes race condition when discovering functions. (#5444)
  • Added support for Nuxt 2 and Nuxt 3. (#5321)
  • Fixes issue where init firestore was unecessarilly checking for default resource location. (#5230 and #5452)
  • Pass trailingSlash from Next.js config to firebase.json (#5445)
  • Don't use Next.js internal redirects for the backend test (#5445)
  • Fix issue where pnpm support broke for function emulation and deployment. (#5467)
  • Fix bug where .env.local files were not picked up during function emulation. (#5477)

v11.21.0

  • Fix bug where CLI was unable to deploy Firebase Functions in some monorepo setups (#5391)
  • Upgrade Storage Rules Runtime to v1.1.3 to support ternary operators (#5370)
  • Fixes an issue where already deployed functions with the same remote configuration do not get skipped (#5354)
  • App Distribution: Links to new releases are now available. These links help you manage binaries and ensure that testers and other developers have the right release. (#5405)

v11.20.0

  • Fixes a bug in the pubsub emulator by forcing a shutdown if it didn't end cleanly. (#5294)
  • Fixes an issue where dependencies for emulated Extensions would not be installed on Windows - thanks @​stfsy! (#5372)
  • Adds emulator support for Extensions with schedule triggers - thanks @​stsfy! (#5374)
  • Update the Emulator Suite UI to v1.11.2 to capture a set of accessibility improvements. (#5394)
  • Fixes an issue in the Functions emulator where secret values were undefined after hot reload with the --inspect-functions flag. (#5384)
  • Fixes a bug where functions:delete command did not recognize '-' as delimiter. (#5290)
  • Reintroduces an updated Hosting emulator with i18n (#4879) and Windows path (#5133) fixes.

v11.19.0

  • Support for string list typed parameters in functions deployment (#5137)
  • Respect .npmrc in backends spun up for web frameworks (#5235)
  • Remove esbuild dependency, instead bundle Next.js configuration on deploy with NPX (#5336)
  • Add sharp NPM module to Cloud Functions when using Next.js Image Optimization (#5238)
  • Adds user-defined env vars into the functions emulator (#5330).
  • Support Next.js Middleware (#5320)
  • Log the reason for a Cloud Function if needed in Next.js (#5320)
  • Fixed service enablement when installing extensions with v2 functions (#5338)
  • Fix bug where functions:shell command didn't connect to emulators running on other processes. (#5269)
  • Fixed bug with Cross-Service Rules integration for Firestore documents containing nulls (#5342)

v11.18.0

  • Add support for Firestore TTL (#5267)
  • Fix bug where secrets were not loaded when emulating functions with --inpsect-functions. (#4605)
  • Handle Next.js rewrites/redirects/headers incompatible with firebase.json in Cloud Functions (#5212)
  • Filter out Next.js prerendered routes that matches rewrites/redirects/headers rules from SSG content directory (#5212)
  • Warn if a web framework's package.json contains anything other than the framework default build command.
  • Add support for nodejs18 for Cloud Functions for Firebase (#5319)

v11.17.0

  • Fix bug where disabling background triggers did nothing. (#5221)
  • Fix bug in auth emulator where empty string should throw invalid email instead of missing email. (#3898)
  • Fix bug in auth emulator in which createdAt was not set for signInWithIdp new users. (#5203)
  • Add region warning for emulated database functions (#5143)

... (truncated)

Commits


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 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/kurosame/glossary/network/alerts).
dependabot[bot] commented 1 year ago

Looks like these dependencies are no longer a dependency, so this is no longer needed.