Beth Griggs

> I prefer the original proposition from Myles given that if there's any breaking change (even if they're kept to a minimal as described above) it's safer (and more clearly...

> support for npm6 and all versions of node that ship with npm6 has already ended, @nlf, can I just check this statement? Apologies if I am interpreting it out...

Based on https://github.com/adoptium/website-v2/pull/1029#issuecomment-1253353724, I've tried to capture a proposed flow of where release notes should be generated, and where the output should be published, and how the website will fetch...

I wrote a very small script in https://github.com/BethGriggs/release-notes-prototype to attempt to pull out the JSON we need. Also pushed an early example of the [JSON output](https://github.com/BethGriggs/release-notes-prototype/blob/main/RELEASE-NOTES-18.0.1.json). I think we need...

## Update I now have two scripts in https://github.com/BethGriggs/release-notes-prototype (see documentation in that repository) - `fetchCommitList` traverses the Git history between two tags, pulls out the JDK numbers and commit...

I think this is no longer a pertinent issue as when running `citgm-smoker-nobuild` for Node.js 18, the job no longer attempts to run on `ubuntu1804-64` (now `rhel8-x64`): ```console 02:03:53 Triggering...

Closing as stale and superseded by the most recent review in https://github.com/nodejs/citgm/issues/997

I had some initial thoughts, but didn't get too far. Some of them: * GitHub produces a SBOM downloadable from [Insights](https://github.com/nodejs/node/network/dependencies) on the repository. This is incomplete and I believe...

Happy to volunteer to set this job up if I can be granted access to do so. It doesn't seem like it'd require much more than duplicating the job and...

> Would you believe it should be a default workflow for all PRs or an opt-in such as request-ci label? I think the latter is reasonable. Probably makes sense to...