-
-
Notifications
You must be signed in to change notification settings - Fork 12
fix: don't turn an omitted assert message into undefined #70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
hexbinoct
wants to merge
1
commit into
nodejs:main
Choose a base branch
from
hexbinoct:hexbinoct/assert-message-forwarding
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+58
−10
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -17,6 +17,7 @@ jobs: | |
| - 22.x | ||
| - 24.x | ||
| - 25.x | ||
| - 26.x | ||
| runs-on: ${{ matrix.runner }} | ||
| steps: | ||
| - name: Harden Runner | ||
|
|
||
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand that this PR came because of behavioral changes in Node 26, but would it be better to separate this PR into two, for separation / tracking: one for the assert changes, and one for the GitHub workflow change? 🤔 Or is that too nit-picky @legendecas thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy to split it, and there is an ordering that makes the split better than keeping it together.
The two are coupled in one direction only. The new harness test can only fail on 26.x, so if the assert fix lands without 26.x in the matrix, CI runs a test that passes on all four existing versions without ever exercising the thing it is checking. The other direction is free: adding 26.x on its own is safe today, because nothing in the suite fails until an assertion actually fails, so the matrix line cannot turn main red by itself.
So if you would rather have them separate:
26.x. Green on current main, no behavior change.implementors/node/assert.jsandtests/harness/assert.js.Each is then independently reviewable, and the fix arrives with a job that actually runs it. Say the word and I will open the matrix PR and strip the workflow line out of this one.
One thing that belongs in the matrix PR rather than here: it takes the matrix to five Node.js versions while #37 is still open about dropping 20.x. 20.x and 25.x are both end of life now (v20.20.2 and v25.9.0, both March 2026) and 26.x is Current and untested, so trading 20.x for 26.x would hold the count at four. I left that out of this PR because it is a separate decision.