| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
This reverts commit 647175e.
|
Review requested:
|
Sorry, something went wrong.
Sorry, something went wrong.
Codecov ReportAll modified and coverable lines are covered by tests ✅ Additional details and impacted files @@ Coverage Diff @@
## main #58211 +/- ##
==========================================
- Coverage 90.13% 90.12% -0.02%
==========================================
Files 629 629
Lines 186628 186644 +16
Branches 36632 36621 -11
==========================================
- Hits 168218 168210 -8
+ Misses 11219 11214 -5
- Partials 7191 7220 +29
... and 38 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Sorry, something went wrong.
|
Fast-track has been requested by @panva. Please 👍 to approve. |
Sorry, something went wrong.
|
@panva please use Resume build to avoid re-running already-green jobs |
Sorry, something went wrong.
I did two times already before and because node-test-commit-osx failed each time with no indication why (other than pointing to checks API) i suspect that's because there were duplicate jobs started (or resumed) by someone as the ones I resumed were already running. |
Sorry, something went wrong.
You can see it in the logs: Build timed out (after 60 minutes). Marking the build as failed. Build was aborted Re-running the other jobs is not going to help, I'd be very surprised it has anything to do with duplicated jobs (or that not resuming would even help if duplicate jobs were an issue). |
Sorry, something went wrong.
https://ci.nodejs.org/job/node-test-commit-osx/64970/nodes=osx13-x64/console
|
Sorry, something went wrong.
FWIW I think this macOS failure is nodejs/build#4072 where it's taking a very long time to correct file ownership on the ccache files post-build. |
Sorry, something went wrong.
|
@richardlau yeah, it's stuck on that step again now. |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
any intention on getting a patch release out there for this? it's broken pretty much everything we use, now we need to roll back to 23. |
Sorry, something went wrong.
This reverts commit 0579e0e PR-URL: #58211 Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: LiviaMedeiros <livia@cirno.name> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Chengzhong Wu <legendecas@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
|
The notable-change PRs with changes that should be highlighted in changelogs. label has been added by @aduh95. Please suggest a text for the release notes if you'd like to include a more detailed summary, then proceed to update the PR description with the text or a link to the notable change suggested text comment. Otherwise, the commit will be placed in the Other Notable Changes section. |
Sorry, something went wrong.
jwt token has a dependency that breaks in node 25 nodejs/node#58211 Azure/azure-sdk-for-js#34243
jwt token has a dependency that breaks in node 25 node:slim will always point to the latest node version, which is currently 25 nodejs/node#58211 Azure/azure-sdk-for-js#34243
jwt token has a dependency that breaks in node 25 node:slim will always point to the latest node version, which is currently 25 nodejs/node#58211 Azure/azure-sdk-for-js#34243
| Back | FazBrowse Home | New Git URL |
This reverts commit 647175e.
The API in question was runtime-deprecated (#55175) and EOLd (#58008 which i'm reverting here) in the same major release. The intended cycle is that it gets runtime-deprecated as a major, and then EOLd in another later major.
Despite best efforts to detect it in the EOL PR there is breakage in the jsonwebtoken > jws > jwa dependency chain (29-30M weekly downloads on jwa).
This PR reverts to the runtime-deprecation state that was pending release with 24.0.0, EOL shouldn't have landed yet.
https://openjs-foundation.slack.com/archives/C019MGJQ8RH/p1746596637445769
We would re-land the EOL and ship it with a future major release after this revert.