renovate[bot]
commented
3 months ago ⚠️ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: examples/typescript/yarn.lock
Unknown Syntax Error: Unsupported option name ("--ignore-platform").
$ yarn install [--json] [--immutable] [--immutable-cache] [--refresh-lockfile] [--check-cache] [--check-resolutions] [--inline-builds] [--mode #0]
File name: examples/basic/yarn.lock
Unknown Syntax Error: Unsupported option name ("--ignore-platform").
$ yarn install [--json] [--immutable] [--immutable-cache] [--refresh-lockfile] [--check-cache] [--check-resolutions] [--inline-builds] [--mode #0]
github-actions[bot]
codecov[bot]
This PR contains the following updates:
13.11.2->13.14.2Release Notes
firebase/firebase-tools (firebase-tools)
### [`v13.14.2`](https://togithub.com/firebase/firebase-tools/releases/tag/v13.14.2) [Compare Source](https://togithub.com/firebase/firebase-tools/compare/v13.14.1...v13.14.2) - Improved notification message when an update is available. ([#7293](https://togithub.com/firebase/firebase-tools/issues/7293)) - Fix issue where Data Connect Emulator can't read config ### [`v13.14.1`](https://togithub.com/firebase/firebase-tools/releases/tag/v13.14.1) [Compare Source](https://togithub.com/firebase/firebase-tools/compare/v13.14.0...v13.14.1) - Bump Firebase Data Connect local toolkit to v1.3.1, which contains fixes for Swift SDK code generation ([#7491](https://togithub.com/firebase/firebase-tools/issues/7491)) ### [`v13.14.0`](https://togithub.com/firebase/firebase-tools/releases/tag/v13.14.0) [Compare Source](https://togithub.com/firebase/firebase-tools/compare/v13.13.3...v13.14.0) - Cleans up App Hosting's GitHub integration UX. "Add an account" flow now goes directly to GitHub instead of using Developer Connect. ([#7405](https://togithub.com/firebase/firebase-tools/issues/7405)) - Fix an issue where refresh_tokens would be used before checking whether they were expired. ([#7442](https://togithub.com/firebase/firebase-tools/issues/7442)) - `firebase init dataconnect` now can pull down deployed GQL files. - Improved detection of 'dataconnect.yaml' when not in project root. - GitHub Action fixes for web frameworks ([#6883](https://togithub.com/firebase/firebase-tools/issues/6883)) - Fixes issue where PubSub message `publishTime` is set to 1970-01-01T00:00:00 ([#7441](https://togithub.com/firebase/firebase-tools/issues/7441)) - Display meaningful error message when cannot determine target. ([#6594](https://togithub.com/firebase/firebase-tools/issues/6594)) - Adds support for firealerts events in Eventarc emulator. ([#7355](https://togithub.com/firebase/firebase-tools/issues/7355)) - Released version firebase-tools-ui@1.13.0, which adds Emulator UI support for firealerts events. - Improved errors when an incorrect service ID is passed to `firebase deploy --only dataconnect:serviceId`. - Fixed display of errors in Firestore commands when using JSON or noninteractive modes. ([#7482](https://togithub.com/firebase/firebase-tools/issues/7482)) - Fixed an issue where Firestore backup schedule commands had invalid short option names. ([#7481](https://togithub.com/firebase/firebase-tools/issues/7481)) - Bumps the Firebase Data Connect local toolkit to v1.3.0, which adds Swift SDK, [@index](https://togithub.com/index), [@unique](https://togithub.com/unique), and batch insert support. ([#7486](https://togithub.com/firebase/firebase-tools/issues/7486)) ### [`v13.13.3`](https://togithub.com/firebase/firebase-tools/releases/tag/v13.13.3) [Compare Source](https://togithub.com/firebase/firebase-tools/compare/v13.13.2...v13.13.3) - Fix an issue where refresh_tokens would be used before checking whether they were expired. ([#7442](https://togithub.com/firebase/firebase-tools/issues/7442)) ### [`v13.13.2`](https://togithub.com/firebase/firebase-tools/releases/tag/v13.13.2) [Compare Source](https://togithub.com/firebase/firebase-tools/compare/v13.13.1...v13.13.2) - Fixes an issue where old access_token would be used after expiry. ([#7429](https://togithub.com/firebase/firebase-tools/issues/7429)) ### [`v13.13.1`](https://togithub.com/firebase/firebase-tools/releases/tag/v13.13.1) [Compare Source](https://togithub.com/firebase/firebase-tools/compare/v13.13.0...v13.13.1) - Pass down `functions.ignore` values in `firebase.json` to functions emulator so that supposedly ignored directories/files will not trigger reload. ([#7414](https://togithub.com/firebase/firebase-tools/issues/7414)) - Fixes bug where secret values provided in env files were parsed as list ([#7422](https://togithub.com/firebase/firebase-tools/issues/7422)) - Update the Firebase Data Connect emulator to v1.2.4, which includes a fix for web SDK generation on Windows and a change for the local Vertex AI client to pick up application default credentials automatically ([#7424](https://togithub.com/firebase/firebase-tools/issues/7424)) ### [`v13.13.0`](https://togithub.com/firebase/firebase-tools/releases/tag/v13.13.0) [Compare Source](https://togithub.com/firebase/firebase-tools/compare/v13.12.0...v13.13.0) - Fixes framework support for Nuxt ^3.12 by correctly calling loadNuxtConfig() ([#7375](https://togithub.com/firebase/firebase-tools/issues/7375)) - Add a default for `firebase init dataconnect:sdk` ([#7406](https://togithub.com/firebase/firebase-tools/issues/7406)) - Bump Firebase Data Connect emulator to v1.2.3, which adds support for `@index` on tables, `@auth(level: USER_ANON/USER_EMAIL_VERIFIED)`, and `key: {uid_expr: "auth.uid"}`, and fixes some issues related to SDK generation ([#7409](https://togithub.com/firebase/firebase-tools/issues/7409)) ### [`v13.12.0`](https://togithub.com/firebase/firebase-tools/releases/tag/v13.12.0) [Compare Source](https://togithub.com/firebase/firebase-tools/compare/v13.11.4...v13.12.0) - Moved `dataconnect.location` key in `firebase.json` to `dataconnect.yaml`. - Fixes issue where files were not properly being discovered and deployed to Firebase Hosting ([#7363](https://togithub.com/firebase/firebase-tools/issues/7363), [#7378](https://togithub.com/firebase/firebase-tools/issues/7378)) - Added new command `init dataconnect:sdk`, which interactively configures a generated SDK for a Data Connect connector. ### [`v13.11.4`](https://togithub.com/firebase/firebase-tools/releases/tag/v13.11.4) [Compare Source](https://togithub.com/firebase/firebase-tools/compare/v13.11.3...v13.11.4) - Data Connect emulator now reuses existing instances if they are emulating the same service. - Fixes issue where `deploy --only dataconnect` would error out with `cannot read property undefined`. - Fixes compatibility issue when uploading native symbols to Crashlytics on Intel-based Macs. ### [`v13.11.3`](https://togithub.com/firebase/firebase-tools/releases/tag/v13.11.3) [Compare Source](https://togithub.com/firebase/firebase-tools/compare/v13.11.2...v13.11.3) - Fixes issue where storage emulator throws an error due to non-standard whitespaces in filenames ([#6834](https://togithub.com/firebase/firebase-tools/issues/6834)). - Fixes issue where some emulators would fail to start when their path contained a whitespace ([#7313](https://togithub.com/firebase/firebase-tools/issues/7313)) - Adds prompt for Postgres connection string to `setup:emulators:dataconnect`. - Updates Data Connect emulator to v1.2.2, which includes support for generating Swift SDKs and a number of bug fixes.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.