feat: add beta release workflow
With the beta release workflow, all commits into the PR will trigger the beta release.
- the beta release always raise just the last version number, following this format:
react-tooltip@{__VERSION__}-beta.{__PR_NUMBER__}.{__BETA_VERSION__}->[email protected] - before merging the PR we will need to set the package.json version to the one we desire
- to skip the workflow we need to add the following words into the commit message:
[skip ci]
[ci skip]
[no ci]
[skip actions]
[actions skip]
https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-runs
https://www.npmjs.com/package/auto-beta-release?activeTab=versions
Beta version released with the last commit 🚀
yarn add [email protected]
or
npm install [email protected]
Beta version released with the last commit 🚀
yarn add [email protected]
or
npm install [email protected]
The gh-actions commit (9319c87 for instance) seems to be "hiding" the last checks that were run.
Expected to see the checks, like this.
that's weird, I didn't realize it before, thanks for letting me know, do you have any idea on how to fix it?
Beta version released with the last commit 🚀
yarn add [email protected]
or
npm install [email protected]
Beta version released with the last commit 🚀
yarn add [email protected]
or
npm install [email protected]
https://github.com/orgs/community/discussions/55906
Beta version released with the last commit 🚀
yarn add [email protected]
or
npm install [email protected]
Beta version released with the last commit 🚀
yarn add [email protected]
or
npm install [email protected]
This pull request is stale because it has not seen activity in 30 days. Remove the stale label or comment within 14 days, or it will be closed.
Walkthrough
The recent updates focus on enhancing GitHub workflows and scripts for better automation and maintenance of a software project. Key changes include the introduction of a new workflow for beta releases, updates to node versions and actions in existing workflows, and adjustments in scripts for beta version management. These modifications streamline development processes and improve the deployment pipeline.
Changes
| Files | Summary |
|---|---|
.github/workflows/beta-release.yaml, beta-release.js |
Introduced and configured beta release automation. |
.github/workflows/.../bundlesize.yaml, .github/workflows/.../lint.yaml |
Updated action versions, renamed workflows, and expanded node versions. |
.github/workflows/.../pull-request.yaml |
Added a job for beta releases. |
.github/workflows/.../stale.yml |
Adjusted indentation in workflow file. |
package.json |
Added minimist dependency. |
Poem
🐇💻
In the warren of code, under digital skies,
A rabbit hops forth, where the software lies.
With a flick and a click, new workflows align,
Beta releases dance, in a code-laced design.
Cheers to changes, both big and small,
In the heart of the code, the rabbit sees all. 🌟
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?
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 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
@coderabbitaiin 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
@coderabbitaiin 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 and render them as a table.@coderabbitai show all the console.log statements in this repository.@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.
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 pauseto pause the reviews on a PR.@coderabbitai resumeto resume the paused reviews.@coderabbitai reviewto trigger a review. This is useful when automatic reviews are disabled for the repository.@coderabbitai resolveresolve all the CodeRabbit review comments.@coderabbitai helpto 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.yamlfile 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.
Beta version released with the last commit 🚀
yarn add [email protected]
or
npm install [email protected]