Repository navigation
deps: update amaro to 1.3.0 - #66144
Open
nodejs-github-bot wants to merge 1 commit into
Open
nodejs-github-bot wants to merge 1 commit into
nodejs-github-bot wants to merge 1 commit into
Conversation
nodejs-github-bot
added
dependencies
Collaborator
Author
|
Review requested:
|
nodejs-github-bot
added
lib / src
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #66144 +/- ##
==========================================
- Coverage 90.68% 90.63% -0.06%
==========================================
Files 797 797
Lines 278790 278790
Branches 53617 53592 -25
==========================================
- Hits 252834 252676 -158
- Misses 16303 16476 +173
+ Partials 9653 9638 -15 🚀 New features to boost your workflow:
|
Member
|
See #66051 |
Contributor
Regardless, it's probably not expected that a semver-minor breaks Node.js |
Member
Yes I agree this shouldnt have happened |
nodejs-github-bot
changed the title
nodejs-github-bot
force-pushed
the
actions/tools-update-amaro
branch
from
September 21, 2026 15:36
49b3ec8 to
0bcfed5
Compare
avivkeller
approved these changes
Sep 22, 2026
panva
added
author ready
Collaborator
Author
panva
removed
the
request-ci
nodejs-github-bot
force-pushed
the
actions/tools-update-amaro
branch
from
September 27, 2026 01:01
8182620 to
b36d15a
Compare
panva
removed
the
author ready
nodejs-github-bot
force-pushed
the
actions/tools-update-amaro
branch
2 times, most recently
from
October 11, 2026 01:04
840165f to
9abe615
Compare
nodejs-github-bot
force-pushed
the
actions/tools-update-amaro
branch
from
October 18, 2026 00:54
9abe615 to
2ac7755
Compare
nodejs-github-bot
changed the title
nodejs-github-bot
force-pushed
the
actions/tools-update-amaro
branch
from
October 25, 2026 00:54
2ac7755 to
6a05d0c
Compare
nodejs-github-bot
changed the title
nodejs-github-bot
force-pushed
the
actions/tools-update-amaro
branch
from
November 1, 2026 00:40
6a05d0c to
28825fd
Compare
Member
|
What's the status of this? Can it land? |
kdy1
approved these changes
Nov 1, 2026
Member
There was a problem hiding this comment.
I think it's good to go.
For context,
- diff & history: nodejs/amaro@v1.1.11...v1.3.0
The biggest change here is nodejs/amaro#467, where amaro now uses the published version of SWC core and self-maintains features related to Node.js
GeoffreyBooth
approved these changes
Nov 1, 2026
Member
|
The CI is red because now the require needs to be updated from index.js to internal.js |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is an automated update of amaro to 1.3.0.