Conversation
I seem to have merged into the wrong branch
sync next with master
…-metadata chore: update extension release metadata
There was a problem hiding this comment.
Code Review
This pull request updates the Dependabot configuration and bumps versions across several Firebase extensions, including updating their respective changelogs. The review feedback highlights that the newly added cooldown configuration in .github/dependabot.yml is unsupported by GitHub Dependabot and will cause a schema validation error, so it should be removed.
| cooldown: | ||
| default-days: 7 | ||
| semver-major-days: 7 | ||
| semver-minor-days: 7 | ||
| semver-patch-days: 7 |
There was a problem hiding this comment.
chore(firestore-bigquery-export): reinstall modules
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
4 similar comments
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
…acker to version 2.0.4
chore: trigger kokoro
chore: fix formatting of changelog entry for version 0.1.30
Drop unused ts-node@^7 devDep and regenerate lock so npm ci resolves jest-config's optional ts-node peer against the lock. The prior lock was generated with a newer npm than the extensions builder runs (npm 9), which demanded a ts-node@10.9.2 subtree absent from the lock.
No description provided.