This repository has been archived by the owner on Sep 26, 2022. It is now read-only.
Runtime nodejs6 is no longer available. Please redeploy your function to a newer version. #251
Comments
|
Thx for reporting this. Let's keep the discussion on angular/angular.js#17111. |
gkalpak
added a commit
to gkalpak/angular.js
that referenced
this issue
Feb 5, 2021
Previously, we only deploy to Firebase hosting for the `docs-angularjs-org` Firebase project. This meant that the eployed functions used an old version of Node.js and started failing once support was dropped for that version. See angular#17111 for details. This commit fixes this by ensuring that we deploy to all enabled Firebase services (currently functions and hosting). Fixes angular#17111 Fixes angular/angularjs.org#251
gkalpak
added a commit
to gkalpak/angular.js
that referenced
this issue
Feb 5, 2021
Previously, we only deployed to Firebase hosting for the `docs-angularjs-org` Firebase project. This meant that the deployed functions used an old version of Node.js and started failing once support was dropped for that version. See angular#17111 for details. This commit fixes this by ensuring that we deploy to all enabled Firebase services (currently functions and hosting). Fixes angular#17111 Fixes angular/angularjs.org#251
gkalpak
added a commit
to gkalpak/angular.js
that referenced
this issue
Feb 6, 2021
Previously, we only deployed to Firebase hosting for the `docs-angularjs-org` Firebase project. This meant that the deployed functions used an old version of Node.js and started failing once support was dropped for that version. See angular#17111 for details. This commit fixes this by ensuring that we deploy to all enabled Firebase services (currently functions and hosting). Fixes angular#17111 Fixes angular/angularjs.org#251
gkalpak
added a commit
to angular/angular.js
that referenced
this issue
Feb 6, 2021
Previously, we only deployed to Firebase hosting for the `docs-angularjs-org` Firebase project. This meant that the deployed functions used an old version of Node.js and started failing once support was dropped for that version. See #17111 for details. This commit fixes this by ensuring that we deploy to all enabled Firebase services (currently functions and hosting). Fixes #17111 Fixes angular/angularjs.org#251
gkalpak
added a commit
to angular/angular.js
that referenced
this issue
Feb 6, 2021
Previously, we only deployed to Firebase hosting for the `docs-angularjs-org` Firebase project. This meant that the deployed functions used an old version of Node.js and started failing once support was dropped for that version. See #17111 for details. This commit fixes this by ensuring that we deploy to all enabled Firebase services (currently functions and hosting). Fixes #17111 Fixes angular/angularjs.org#251
AnkushLambdatest
pushed a commit
to AnkushLambdatest/angular.js
that referenced
this issue
Jun 29, 2022
Previously, we only deployed to Firebase hosting for the `docs-angularjs-org` Firebase project. This meant that the deployed functions used an old version of Node.js and started failing once support was dropped for that version. See angular#17111 for details. This commit fixes this by ensuring that we deploy to all enabled Firebase services (currently functions and hosting). Fixes angular#17111 Fixes angular/angularjs.org#251
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For example: https://docs.angularjs.org/api/ng/service/$location
See angular/angular.js#17111
The text was updated successfully, but these errors were encountered: