Create release.yml

[NxPKG]

User description

Notes for Reviewers

This PR fixes #

Signed commits

• Yes, I signed my commits.

---

PR Type

configuration changes

---

Description

• Added a new release.yml file to configure changelog generation for releases.
• Excluded 'dependabot' from the list of authors in the changelog.
• Defined categories for organizing changes: New Features, Bug Fixes, Maintenance, and Other Changes.
• Mapped specific labels to each category to enhance clarity and organization.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	release.yml Add changelog configuration for release management              .github/release.yml Added a changelog configuration file for release management. Excluded 'dependabot' from authors in the changelog. Defined categories for new features, bug fixes, maintenance, and other changes. Mapped labels to each category for better organization. +17/-0

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

Summary by CodeRabbit

• New Features
  • Enhanced changelog generation process with new configuration options.
  • Introduced categories for organizing changelog entries, including "New Features," "Bugs Fixes," "Maintenance," and "Other Changes."
• Chores
  • Excluded contributions from "dependabot" in the changelog.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR adds a new GitHub release configuration file that defines how the changelog should be generated for releases. The configuration excludes Dependabot commits and categorizes changes based on different labels.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Added GitHub release configuration for automated changelog generation	Configured to exclude Dependabot authored commits Defined four changelog categories with corresponding labels Set up category mapping for Enhancement, Bug, Maintenance, and Other changes Added emoji indicators for each category type	.github/release.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Walkthrough

A new configuration section has been added to the .github/release.yml file to improve the changelog generation process. This includes an exclude directive to omit contributions from "dependabot" and a categories section to organize changelog entries into specified categories: "New Features," "Bugs Fixes," "Maintenance," and "Other Changes," each with corresponding labels.

Changes

File	Change Summary
.github/release.yml	Added changelog configuration with exclude directive for "dependabot" and categories for organizing changelog entries. New categories include "New Features" (Type: Enhancement), "Bugs Fixes" (Type: Bug), "Maintenance" (Type: Maintenance), and "Other Changes" (*).

Poem

In the land of code where rabbits play,
Changelogs bloom in a bright array.
With features new and bugs all gone,
We hop along, our work goes on!
Exclude the bots, let the good times roll,
In our changelog garden, we reach our goal! 🐇✨

---

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>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• 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 testing code 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

Hey @NxPKG - I've reviewed your changes - here's some feedback:

Overall Comments:

• Please update the PR description to include the issue number this PR fixes.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

nitpick (typo): Fix grammatical error in category title

Should be 'Bug Fixes' or 'Bugs Fixed' instead of 'Bugs Fixes'

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Configuration Review The wildcard label "*" in the "Other Changes" category might catch too many unrelated changes. Consider being more specific with label definitions.

[codiumai-pr-agent-free]

PR Code Suggestions ✨

No code suggestions found for the PR.

[github-actions]

This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 365 days.