nodejs / tweet Goto Github PK

using to test slack + github integration

Security release pre-alert:

We will release new versions of v18, v16, and v14 release lines on or shortly
after 5th July, 2022 in order to address:

• 2 high severity issues
• 3 moderate severity issues

https://nodejs.org/en/blog/vulnerability/july-2022-security-releases/

Want to make a difference in the Node.js community? Join the Security Working Group and help shape the future of Node.js security in 2023! Contribute to important initiatives and take part in the Security WG sessions.
Follow https://github.com/nodejs/security-wg for further information

Related: #40

First question: is only one approval from a member of the @nodejs/social team adequate to merge a tweet. I assume yes, but we should clarify in our docs.

Also: should we setup a github action that merges a tweet within 24hrs of one approval or should we just rely on the fact that once a social team member approves, they can merge. If we setup a 24hr github action, we could build it as such that it would tweet at an optimal time/day.

Is your feature request related to a problem? Please describe.

There's no system to tweet about EOL versions of Node.js
The tweets need to be manually created like #77

Describe the solution you'd like

Create automated tweets when a Node.js LTS version reaches close to EoL.
The end-of-life dates can be set from Release Schedule like https://github.com/nodejs/Release#release-schedule

It can start tweeting as a countdown before EOL dates, like:

• 3 months
• 1 month
• 1 week
• 3 days
• 0 day

There are existing scripts for recurring tweets for example https://github.com/nodejs/tweet/tree/main/scripts/recurring

Describe alternatives you've considered

Manually remembering about EOL, and creating PR like in #77

Additional context

This question was asked on #nodejs slack, and here are some comments:

@Qard says

Automating tweets for LTS expiry sounds like a good idea to me. It'd be really great if we could get more users off super old versions. 😅

@joesepi says

Sounds like a great idea. automate all the things

Security release pre-alert:

We will release new versions of all release lines on or shortly
after 14 Feb 2023 Year in order to address:

• 2 low severity issues.
• 2 medium severity issues.
• 1 high severity issues.
• OpenSSL security updates for which the highest vulnerability severity is high. You can read more about this update in the OpenSSL security advisory.

https://nodejs.org/en/blog/vulnerability/february-2023-security-releases/

Security release pre-alert:

We will release new versions of release lines on or shortly
after Thursday 22nd of September, 2022 in order to address:

• 4 high severity issues
• 2 moderate severity issues

https://nodejs.org/en/blog/vulnerability/september-2022-security-releases/

Security release:

New security releases are now available for versions 18.5.0, v16.16.0, and v14.20.0 of Node.js.

https://nodejs.org/en/blog/vulnerability/july-2022-security-releases/

Security release pre-alert:

We will release new versions of 14.x, 16.x, 18.x, and 19.x release lines on or shortly
after Thursday, November 3, 2022 in order to address:

• 2 high severity issues
• 1 moderate severity issues

https://nodejs.org/en/blog/vulnerability/november-2022-security-releases/

Ref to nodejs/node#41554

I would like to send the following poll through the @nodejs account to get a good amount of engagement that allows us to understand if there's any interest to keep the multipleResolves event, or if there are use cases we missed.

We're considering deprecating `process.on('multipleResolves'`, but first we would like to gauge the community's familiarity with and usage of 'multipleResolves'

You can help us by answering to the pool below, and if you have used it, please share your experience in a reply

- Unfamiliar with it
- Familiar but not using
- Used before but not now
- Currently using it

The 25 characters limit in each choice option makes it difficult to write a better poll. If folks have a better idea for choices, please feel free to share.

New security releases are now available for versions 12, 14, 16, and 17 of Node.js.

https://nodejs.org/en/blog/vulnerability/jan-2022-security-releases/

Security release:

New security releases are now available for versions v14, v16, v18, and v19 of Node.js.

https://nodejs.org/en/blog/vulnerability/november-2022-security-releases

We've agreed to close the Next-10 survey on Friday April 16th. Could you do a "last chance" complete before April 16 tweet ?

New security releases are now available for versions 14, 16 and 18 of Node.js.

https://nodejs.org/en/blog/vulnerability/september-2022-security-releases/

New security releases are now available for versions 12.x, 14.x, 16.x of Node.js.

https://nodejs.org/en/blog/vulnerability/oct-2021-security-releases/