-
Notifications
You must be signed in to change notification settings - Fork 30k
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
report: separate release metadata #25826
Conversation
"openssl": "1.1.0j" | ||
}, | ||
"release": { | ||
"name": "node" |
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.
Should we document other fields for a normal release build?
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.
Possibly, but a normal release build wouldn't be: "nodejsVersion": "v12.0.0-pre",
.
f6ad48a
to
ede0655
Compare
Report release metadata separately from `componentVersions`. Test `componentVersions` and `release` values in the report. PR-URL: nodejs#25826 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
ede0655
to
d0d84b0
Compare
Landed in d0d84b0. |
Report release metadata separately from `componentVersions`. Test `componentVersions` and `release` values in the report. PR-URL: #25826 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Report release metadata separately from
componentVersions
.Test
componentVersions
andrelease
values in the report.Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes