Skip to content
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

doc: create maintaining folder for deps #47589

Merged

Conversation

marco-ippolito
Copy link
Member

@marco-ippolito marco-ippolito commented Apr 17, 2023

I would like to receive some feedback on this idea.
I wanted to move all the maintaining-x files under a common folder and I have created an overview file that lists all the dependencies and in a second iteration their version that will be updated by the tools.yml action.
Should we keep the name of the md files maintaing-x or just x?
@nodejs/security-wg
Refs: nodejs/security-wg#828

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Apr 17, 2023
@targos
Copy link
Member

targos commented Apr 17, 2023

SGTM

Copy link
Member

@tniessen tniessen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of these files seem like they could be very short now that most is automated (and we don't want manual updates in most cases), maybe we could even put everything into a single document or so.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file does not really match the common theme since only a small part of it is about updating uvwasi.

@marco-ippolito
Copy link
Member Author

probably there is no longer the need to describe the updating procedure because for most of them is automated and there is just one script thus making some maintaining.md useless

@marco-ippolito marco-ippolito marked this pull request as ready for review April 19, 2023 10:04
@marco-ippolito marco-ippolito force-pushed the feat/organize-maintaining branch 3 times, most recently from 05b4919 to 19d33fe Compare April 19, 2023 10:26
@RafaelGSS
Copy link
Member

I think we should keep them in multiple files once the automation doesn't handle other active release lines. For instance, OpenSSL 1.x on v14 or OpenSSL 1.x+quic on v16 versions.

Also, I'm not sure about removing the maintaining files that were already covered by the update automation. It seems a good reference to perform maintenance in automation.

@marco-ippolito
Copy link
Member Author

marco-ippolito commented Apr 19, 2023

OpenSSL has its own maintaining file, I left the maintaining files for dependencies that have a complex procedure. Most of the ones I'm removing I created them and they were just execute dep_updaters/foo.sh. For the 14 release line is EOL, so we dont need to backport anymore right?

@marco-ippolito marco-ippolito added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Apr 24, 2023
@marco-ippolito marco-ippolito added the commit-queue Add this label to land a pull request using GitHub Actions. label Apr 26, 2023
@nodejs-github-bot nodejs-github-bot added commit-queue-failed An error occurred while landing this pull request using GitHub Actions. and removed commit-queue Add this label to land a pull request using GitHub Actions. labels Apr 26, 2023
@nodejs-github-bot
Copy link
Collaborator

Commit Queue failed
- Loading data for nodejs/node/pull/47589
✔  Done loading data for nodejs/node/pull/47589
----------------------------------- PR info ------------------------------------
Title      doc: create maintaining folder for deps (#47589)
Author     Marco Ippolito  (@marco-ippolito)
Branch     marco-ippolito:feat/organize-maintaining -> nodejs:main
Labels     doc, author ready
Commits    1
 - doc: create maintaining folder for deps
Committers 1
 - Marco Ippolito 
PR-URL: https://github.com/nodejs/node/pull/47589
Refs: https://github.com/nodejs/security-wg/issues/828
Reviewed-By: James M Snell 
Reviewed-By: Paolo Insogna 
Reviewed-By: Rafael Gonzaga 
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/47589
Refs: https://github.com/nodejs/security-wg/issues/828
Reviewed-By: James M Snell 
Reviewed-By: Paolo Insogna 
Reviewed-By: Rafael Gonzaga 
--------------------------------------------------------------------------------
   ⚠  Commits were pushed since the last review:
   ⚠  - doc: create maintaining folder for deps
   ℹ  This PR was created on Mon, 17 Apr 2023 09:09:21 GMT
   ✔  Approvals: 3
   ✔  - James M Snell (@jasnell) (TSC): https://github.com/nodejs/node/pull/47589#pullrequestreview-1394928517
   ✔  - Paolo Insogna (@ShogunPanda): https://github.com/nodejs/node/pull/47589#pullrequestreview-1395787388
   ✔  - Rafael Gonzaga (@RafaelGSS) (TSC): https://github.com/nodejs/node/pull/47589#pullrequestreview-1396007103
   ✔  Last GitHub CI successful
   ✘  No Jenkins CI runs detected
--------------------------------------------------------------------------------
   ✔  Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/4806355194

@marco-ippolito marco-ippolito removed the commit-queue-failed An error occurred while landing this pull request using GitHub Actions. label Apr 26, 2023
@marco-ippolito marco-ippolito added the commit-queue Add this label to land a pull request using GitHub Actions. label Apr 26, 2023
@nodejs-github-bot nodejs-github-bot added commit-queue-failed An error occurred while landing this pull request using GitHub Actions. and removed commit-queue Add this label to land a pull request using GitHub Actions. labels Apr 26, 2023
@nodejs-github-bot
Copy link
Collaborator

Commit Queue failed
- Loading data for nodejs/node/pull/47589
✔  Done loading data for nodejs/node/pull/47589
----------------------------------- PR info ------------------------------------
Title      doc: create maintaining folder for deps (#47589)
Author     Marco Ippolito  (@marco-ippolito)
Branch     marco-ippolito:feat/organize-maintaining -> nodejs:main
Labels     doc, author ready
Commits    1
 - doc: create maintaining folder for deps
Committers 1
 - Marco Ippolito 
PR-URL: https://github.com/nodejs/node/pull/47589
Refs: https://github.com/nodejs/security-wg/issues/828
Reviewed-By: James M Snell 
Reviewed-By: Paolo Insogna 
Reviewed-By: Rafael Gonzaga 
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/47589
Refs: https://github.com/nodejs/security-wg/issues/828
Reviewed-By: James M Snell 
Reviewed-By: Paolo Insogna 
Reviewed-By: Rafael Gonzaga 
--------------------------------------------------------------------------------
   ℹ  This PR was created on Mon, 17 Apr 2023 09:09:21 GMT
   ✔  Approvals: 3
   ✔  - James M Snell (@jasnell) (TSC): https://github.com/nodejs/node/pull/47589#pullrequestreview-1394928517
   ✔  - Paolo Insogna (@ShogunPanda): https://github.com/nodejs/node/pull/47589#pullrequestreview-1395787388
   ✔  - Rafael Gonzaga (@RafaelGSS) (TSC): https://github.com/nodejs/node/pull/47589#pullrequestreview-1402037281
   ✔  Last GitHub CI successful
   ✘  No Jenkins CI runs detected
--------------------------------------------------------------------------------
   ✔  Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/4809803241

@marco-ippolito marco-ippolito added request-ci Add this label to start a Jenkins CI on a PR. and removed commit-queue-failed An error occurred while landing this pull request using GitHub Actions. labels Apr 26, 2023
Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@marco-ippolito marco-ippolito added the request-ci Add this label to start a Jenkins CI on a PR. label May 2, 2023
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label May 2, 2023
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@marco-ippolito marco-ippolito added the commit-queue Add this label to land a pull request using GitHub Actions. label May 2, 2023
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label May 2, 2023
@nodejs-github-bot nodejs-github-bot merged commit 109ab0a into nodejs:main May 2, 2023
48 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in 109ab0a

targos pushed a commit that referenced this pull request May 3, 2023
PR-URL: #47589
Refs: nodejs/security-wg#828
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Paolo Insogna <paolo@cowtech.it>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
@targos targos mentioned this pull request May 3, 2023
targos pushed a commit that referenced this pull request May 3, 2023
PR-URL: #47589
Refs: nodejs/security-wg#828
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Paolo Insogna <paolo@cowtech.it>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
danielleadams pushed a commit that referenced this pull request Jul 6, 2023
PR-URL: #47589
Refs: nodejs/security-wg#828
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Paolo Insogna <paolo@cowtech.it>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
MoLow pushed a commit to MoLow/node that referenced this pull request Jul 6, 2023
PR-URL: nodejs#47589
Refs: nodejs/security-wg#828
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Paolo Insogna <paolo@cowtech.it>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants