feat(release): added automatic project versioning

[francescopausellii]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @francescopausellii, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces an automated release workflow by integrating semantic-release. The primary goal is to streamline the versioning process, ensuring that new releases are automatically generated, version numbers are consistently bumped based on commit messages, and release notes and changelogs are created without manual intervention. This enhancement aims to improve release efficiency and reliability.

Highlights

• Automatic Versioning Configuration: A new .releaserc file has been added to configure semantic-release, specifying the main branch for releases and integrating plugins for commit analysis, release notes, changelog generation, GitHub releases, and Git operations.
• Release Script Added: A new release script has been added to package.json, which will execute semantic-release to automate the versioning and release process.
• Semantic Release Dependencies: Several semantic-release related packages, including semantic-release itself and its changelog, git, and github plugins, have been added as development dependencies to package.json.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/release.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces automatic project versioning using semantic-release. The configuration is mostly correct, but I've found a critical issue with missing dependencies that would cause the release process to fail. I've also suggested a small improvement to the .releaserc configuration to make it more explicit and maintainable.

[francescopausellii]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces automatic project versioning using semantic-release. While this is a great addition, the current configuration has a critical issue with the plugin order and is missing the @semantic-release/npm plugin, which is required to update the package.json version. I've provided suggestions to correct the configuration and add the missing dependency to ensure the automated release process works as expected.