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

[legacy] Blog: v21.7.1 release post #6469

Merged
merged 1 commit into from
Mar 9, 2024
Merged

Conversation

targos
Copy link
Member

@targos targos commented Mar 8, 2024

Refs: nodejs/node#52002

I was told that we're supposed to open two PRs when doing a release for now.

Description

Validation

Related Issues

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run npx turbo format to ensure the code follows the style guide.
  • I have run npx turbo test to check if all tests are passing.
  • I have run npx turbo build to check if the website builds without errors.
  • I've covered new added functionality with unit tests if necessary.

@targos targos requested a review from a team as a code owner March 8, 2024 22:04
Copy link

vercel bot commented Mar 8, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Mar 8, 2024 10:06pm

@targos targos added the github_actions:pull-request Trigger Pull Request Checks label Mar 8, 2024
@targos targos changed the title Blog: v21.7.1 release post [legacy] Blog: v21.7.1 release post Mar 8, 2024
@richardlau richardlau merged commit 58fdf75 into nodejs:legacy Mar 9, 2024
1 check passed
@targos targos deleted the v21.7.1-legacy branch March 9, 2024 07:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
github_actions:pull-request Trigger Pull Request Checks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants