Update firebase-tools → 13.0.2 (unknown) #170
Closed
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ firebase-tools (^12.9.1 → ^13.0.2) · Repo · Changelog
Release Notes
13.0.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 12 commits:
13.0.2
Add utility commands for app hosting. (#6616)
Fix bug where fetching linkable repos for a connection uses location associated with the backend instead of the resource itself. (#6612)
Create build and update traffic during backends:create (#6611)
Rename frameworks to apphosting (#6610)
Dynamically load available locations from App Hosting API (#6609)
Add RSC headers of Next.js app directory pages to Hosting headers. (#6608)
Change default name of backend to something more generic ("my-web-app") (#6601)
Fix bug where backends:list and backends:get command fails when no backends exists. (#6600)
Fix for the default import of strip-ansi (#6599)
fix Next.js dynamic and static OG images (#6592)
[firebase-release] Removed change log and reset repo after 13.0.1 release
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands