Skip to content

Conversation

@shyim
Copy link
Contributor

@shyim shyim commented Apr 24, 2024

image

new nodejs release 😱
https://openjsf.org/blog/nodejs-22-available

For new package PRs only

  • This PR is marked as fixing a pre-existing package request bug
    • Alternatively, the PR is marked as related to a pre-existing package request bug, such as a dependency
  • REQUIRED - The package is available under an OSI-approved or FSF-approved license
  • REQUIRED - The version of the package is still receiving security updates
  • This PR links to the upstream project's support policy (e.g. endoflife.date)

For new version streams

  • The upstream project actually supports multiple concurrent versions.
  • Any subpackages include the version string in their package name (e.g. name: ${{package.name}}-compat)
  • The package (and subpackages) provides: logical unversioned forms of the package (e.g. nodejs, nodejs-lts)

For security-related PRs

  • The security fix is recorded in the advisories repo

For version bump PRs

  • The epoch field is reset to 0

For PRs that add patches

  • Patch source is documented

@ajayk
Copy link
Member

ajayk commented Apr 24, 2024

We are currently waiting for this to be merged endoflife-date/endoflife.date#5036 so our bots can create an automatic version stream for the new releases

Example here

@shyim
Copy link
Contributor Author

shyim commented Apr 25, 2024

It's merged the bot did nothing 🤔

@ajayk
Copy link
Member

ajayk commented Apr 25, 2024

Bot created the new version stream here

@ajayk
Copy link
Member

ajayk commented Apr 25, 2024

Closing this as version streams are handled by bots

@ajayk ajayk closed this Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants