Add patch release script

[axeldelafosse]

Summary

• Added a release:patch script to package.json:
  • npm version patch && git push --follow-tags
• Updated README.md to document patch release using the new script:
  • bun run release:patch

Why

• Simplifies the release workflow by combining version bump and tag push into one command.

Files Changed

• package.json
• README.md

Testing

• Not run (script + docs-only change).

[gemini-code-assist]

Summary of Changes

Hello @axeldelafosse, 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 streamlines the patch release process by introducing a new release:patch script. This script automates the version bumping and tag pushing, consolidating multiple manual steps into a single command. The documentation has also been updated to reflect this simplified workflow, making releases more efficient and less error-prone.

Highlights

• New release:patch script: A new release:patch script has been added to package.json to automate patch version bumps and tag pushes using npm version patch && git push --follow-tags.
• README.md updated: The README.md has been updated to document the new bun run release:patch command for simplified patch releases, replacing the manual npm version patch, git push origin main, and git push --tags steps.

Changelog

• README.md
  • Updated the "Example release" section to use bun run release:patch instead of separate npm version and git push commands.
  • Included a comment explaining the new script's equivalent commands.
• package.json
  • Added a new release:patch script to the scripts section.

Activity

• No human activity has occurred on this pull request yet.

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 adds a release:patch script to simplify patch releases. The change is good, but the script can be made more robust. I've suggested making the git push command more explicit to ensure it always pushes to the main branch, as intended for releases. This will prevent accidental releases from other branches.

[gemini-code-assist]

The git push command in this script doesn't specify a branch. It will push the current branch, which may not be main. According to your README.md, releases are triggered by pushes to main. To make the release process more robust and prevent accidental releases from other branches, I recommend explicitly pushing to origin main.

With this change, you'll also want to update the comment in README.md on line 117 to # npm version patch && git push origin main --follow-tags to keep the documentation accurate.

Suggested change

	"release:patch": "npm version patch && git push --follow-tags",
	"release:patch": "npm version patch && git push origin main --follow-tags",