chore: fix missing pnpm install in release workflow

[ymc9]

Summary by CodeRabbit

• Chores
  • Updated Node.js version in the workflow setup to 20.x.
  • Updated pnpm action setup to version 7.15.0.

[coderabbitai]

Walkthrough

Walkthrough

The update involves upgrading the Node.js version to 20.x in a GitHub Actions workflow and updating the pnpm action to version 7.15.0. This change is part of enhancing the CI/CD pipeline to ensure compatibility with newer technologies and improve the efficiency of the development process.

Changes

Files	Change Summary
.github/workflows/management-changelog.yml	Updated Node.js version to 20.x; updated pnpm action to version 7.15.0

Related issues

• Proper CI/CD for npm package publishing #68: This PR could potentially address the objective of implementing and improving a CI/CD pipeline by updating the Node.js version and pnpm action, which are crucial for automated testing, linting, and deployment processes. The change ensures the pipeline remains compatible with the latest technologies, aligning with best practices for npm package publishing and deployment.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 3001759 and a8bd1ee.

Files selected for processing (1)

• .github/workflows/management-changelog.yml (1 hunks)

Additional comments: 1

.github/workflows/management-changelog.yml (1)

• 48-48: The update of the Node.js version to 20.x is a significant change that aligns with the objective of using a more current and supported version. This update can bring several benefits, including performance improvements, access to new features, and better security. It's important to ensure that all Node.js dependencies are compatible with this new version to avoid potential issues during the build or runtime.

Ensure compatibility of all Node.js dependencies with version 20.x by reviewing the project's package.json and conducting thorough testing.

[coderabbitai]

The update of the pnpm action to version ^7.15.0 is correctly implemented. However, using the caret ^ in the version specification for CI/CD workflows can introduce unpredictability by automatically upgrading to newer minor versions. While this can be beneficial for receiving updates, it might also introduce breaking changes unexpectedly.

Consider pinning the pnpm action to an exact version (7.15.0) to ensure consistent behavior across builds.

- version: ^7.15.0
+ version: 7.15.0

---

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

	- uses: pnpm/action-setup@v2
	if: ${{ steps.release.outputs.release_created }}
	with:
	version: ^7.15.0
	- uses: pnpm/action-setup@v2
	if: ${{ steps.release.outputs.release_created }}
	with:
	version: 7.15.0