-
Notifications
You must be signed in to change notification settings - Fork 41
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
feat: add CVE-ID to commit-output #167
base: main
Are you sure you want to change the base?
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
7c6e46b
to
872d352
Compare
I don't know why this is failing. I'm getting success locally:
It might be due to some credentials. Can someone test it too? cc: @nodejs/releasers |
PR-URL: #55830 Refs: nodejs/changelog-maker#167 Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
PR-URL: #55830 Refs: nodejs/changelog-maker#167 Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
@rvagg PTAL |
I still can't reproduce the errors on my local environment |
The workflow checks out with
|
Oh, so I think merging it should be fine? |
No? It will break the workflow. |
remove the fetch-depth in the workflow and give it another go, it's not exactly an expensive repo to fetch, I guess it's there as a copy-pasta from another repo where it made sense |
|
I think this might be because checkout is adding a merge commit, which maybe we don't want here: https://github.com/actions/checkout/blob/61b9e3751b92087fd0b06925ba6dd6314e06f089/README.md#L194-L201 Could you try adding with:
ref: ${{ github.event.pull_request.head.sha }} to the checkout in the action and see if that helps? |
PR-URL: nodejs#55830 Refs: nodejs/changelog-maker#167 Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
FWIW you can also do |
Fake PR-URL for testing CVE-ID: CVE-2024-22020 PR-URL: nodejs/node#55819
fd40009
to
17ce224
Compare
Oh nevermind, I found the error. I made a change on |
This PR changes the commit output to include CVE-ID in the output (part of automation of security releases - fixes: https://github.com/nodejs-private/security-release/issues/38)
Output:
I haven't added support to
--simple
as we won't use it in the automation. We can add it later if needed.