Create release.yml

[NxPKG]

Notes for Reviewers

This PR fixes #

Signed commits

• [*] Yes, I signed my commits.

Summary by Sourcery

CI:

• Add release.yml to define changelog categories based on labels.

[sourcery-ai[bot]]

Reviewer's Guide by Sourcery

This pull request introduces a new file release.yml in the .github directory to configure the changelog categories for releases. The changes focus on setting up a structured format for organizing release notes.

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

File-Level Changes

Change	Details	Files
Add a new release configuration file for structured changelogs	Define three main categories for the changelog: Added, Fixed, and Miscellaneous Map 'enhancement' label to the 'Added' category Map 'bug' label to the 'Fixed' category Map 'refactor', 'dependencies', 'documentation', and 'ci' labels to the 'Miscellaneous' category	.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](https://app.sourcery.ai) 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](mailto:support@sourcery.ai) for questions or feedback. - Visit our [documentation](https://docs.sourcery.ai) for detailed guides and information. - Keep in touch with the Sourcery team by following us on [X/Twitter](https://x.com/SourceryAI), [LinkedIn](https://www.linkedin.com/company/sourcery-ai/) or [GitHub](https://github.com/sourcery-ai).

[github-actions[bot]]

Woohoo @NxPKG! 🎉 You've just dropped some hot new code! 🔥

Hang tight while we review this! You rock! 🤘

[github-actions[bot]]

Woohoo @NxPKG! 🎉 You've just dropped some hot new code! 🔥

Hang tight while we review this! You rock! 🤘

[deepsource-io[bot]]

Here's the code health analysis summary for commits 8b487ad..8d2e09e. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Docker	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[codiumai-pr-agent-free[bot]]

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

⚡ No major issues detected

[codiumai-pr-agent-free[bot]]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Enhancement	Include a 'Changed' category in the changelog to better categorize significant updates ___ **Consider adding a 'Changed' category to capture significant changes that are neither new features nor bug fixes. This can help users quickly identify important updates that may affect their usage of the project.** [.github/release.yml [1-14]](https://github.com/khulnasoft/reconpoint/pull/80/files#diff-409fea45635f464aa0592700a92cf483be2f5b21b60f8f1b383756067ee79213R1-R14) ```diff changelog: categories: - title: Added labels: - enhancement + - title: Changed + labels: + - changed - title: Fixed labels: - bug - title: Miscellaneous labels: - refactor - dependencies - documentation - ci ``` - [ ] **Apply this suggestion** Suggestion importance[1-10]: 7 Why:	7
Best practice	Add a label for breaking changes to improve visibility of potentially disruptive updates ___ **Consider adding a 'breaking-change' label to the 'Miscellaneous' category or creating a separate 'Breaking Changes' category to highlight changes that may require user action.** [.github/release.yml [9-14]](https://github.com/khulnasoft/reconpoint/pull/80/files#diff-409fea45635f464aa0592700a92cf483be2f5b21b60f8f1b383756067ee79213R9-R14) ```diff - title: Miscellaneous labels: - refactor - dependencies - documentation - ci + - breaking-change ``` - [ ] **Apply this suggestion** Suggestion importance[1-10]: 7 Why:	7

💡 Need additional feedback ? start a PR chat

[github-actions[bot]]

Holy smokes! 🤯 You've just made reconPoint even more awesome!

Your code is now part of the reconPoint hall of fame. 🏆

Keep the cool ideas coming - maybe next time you'll break the internet! 💻💥

Virtual high fives all around! 🙌

[github-actions[bot]]

Holy smokes! 🤯 You've just made reconPoint even more awesome!

Your code is now part of the reconPoint hall of fame. 🏆

Keep the cool ideas coming - maybe next time you'll break the internet! 💻💥

Virtual high fives all around! 🙌