feat: add beta release workflow #1148

danielbarion · 2024-01-02T14:09:13Z

With the beta release workflow, all commits into the PR will trigger the beta release.

the beta release always release a new beta version, following this format:
react-tooltip@{__VERSION__}-beta.{__PR_NUMBER__}.rc.{__BETA_VERSION__} -> react-tooltip@v0.0.11-beta.1.rc.1
to skip the workflow we need to add the following words to 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

Summary by CodeRabbit

New Features
- Introduced automated workflows for beta releases, enhancing the release process.
- Updated Bundlesize GitHub Action to improve the reliability of bundle size checks.
- Expanded node version support in linting workflow to include the latest version.
Enhancements
- Streamlined naming for linting workflow for better clarity.
Documentation
- Adjusted workflow documentation to reflect updated action versions and configurations.
Dependencies
- Added a new dependency (minimist) to improve command line parsing capabilities.

github-actions · 2024-01-02T14:10:33Z

Beta version released with the last commit 🚀

yarn add react-tooltip@v5.25.2-beta.1148.0

or

npm install react-tooltip@v5.25.2-beta.1148.0

github-actions · 2024-01-02T16:53:01Z

Beta version released with the last commit 🚀

yarn add react-tooltip@v5.25.2-beta.1148.2

or

npm install react-tooltip@v5.25.2-beta.1148.2

gabrieljablonski · 2024-01-02T16:57:49Z

The gh-actions commit (9319c87 for instance) seems to be "hiding" the last checks that were run.

Expected to see the checks, like this.

gabrieljablonski

Approving to see if checks are re-run. If not, changes should be made,

gabrieljablonski

Nope 🤔

danielbarion · 2024-01-02T18:26:18Z

that's weird, I didn't realize it before, thanks for letting me know, do you have any idea on how to fix it?

.github/workflows/beta-release.yaml

github-actions · 2024-01-02T19:09:22Z

Beta version released with the last commit 🚀

yarn add react-tooltip@v5.25.2-beta.1148.3

or

npm install react-tooltip@v5.25.2-beta.1148.3

github-actions · 2024-01-02T19:11:57Z

Beta version released with the last commit 🚀

yarn add react-tooltip@v5.25.2-beta.1148.4

or

npm install react-tooltip@v5.25.2-beta.1148.4

danielbarion · 2024-01-02T19:14:27Z

https://github.com/orgs/community/discussions/55906

danielbarion · 2024-01-02T19:31:49Z

Beta version released with the last commit 🚀

yarn add react-tooltip@v5.25.2-beta.1148.5

or

npm install react-tooltip@v5.25.2-beta.1148.5

github-actions · 2024-01-02T19:41:58Z

Beta version released with the last commit 🚀

yarn add react-tooltip@v5.25.2-beta.1148.6

or

npm install react-tooltip@v5.25.2-beta.1148.6

github-actions · 2024-04-02T12:19:25Z

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.

coderabbitai · 2024-05-07T19:43:51Z

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?

Share

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 @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 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 pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai help to 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.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.

github-actions · 2024-05-07T19:45:01Z

Beta version released with the last commit 🚀

yarn add react-tooltip@5.26.4-beta.1148.rc.0

or

npm install react-tooltip@5.26.4-beta.1148.rc.0

coderabbitai

Actionable comments posted: 2

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 54aeda9 and b47e870.

Files ignored due to path filters (1)

yarn.lock is excluded by !**/*.lock

Files selected for processing (7)

.github/workflows/beta-release.yaml (1 hunks)
.github/workflows/bundlesize.yaml (3 hunks)
.github/workflows/lint.yaml (3 hunks)
.github/workflows/pull-request.yaml (1 hunks)
.github/workflows/stale.yml (1 hunks)
beta-release.js (1 hunks)
package.json (1 hunks)

Files skipped from review due to trivial changes (6)

.github/workflows/beta-release.yaml
.github/workflows/bundlesize.yaml
.github/workflows/lint.yaml
.github/workflows/pull-request.yaml
.github/workflows/stale.yml
package.json

Additional comments not posted (1)

beta-release.js (1)

12-18: The implementation of runCommand function looks good and properly handles command execution and output.

coderabbitai · 2024-05-07T19:48:32Z

beta-release.js

+const AutoBetaRelease = async () => {
+  // get all the versions of the package from npm
+  const { stdout } = await runCommand(`npm view . versions --json`)
+
+  // show npm published versions of this package
+  console.log(stdout)
+
+  // check if there is a beta release with the same issue number on published versions
+  const arrayOfBetaReleases = JSON.parse(stdout).filter((version) =>
+    version.includes(`${package.version}-beta.${issueNumber}`),
+  )
+
+  let fullLastBetaRelease = null
+
+  // if yes, get the latest beta release. Output: 1.0.0-beta.1.rc.0
+  if (arrayOfBetaReleases.length) {
+    fullLastBetaRelease = arrayOfBetaReleases[arrayOfBetaReleases.length - 1]
+  }
+
+  console.log('Last Beta Release: ', fullLastBetaRelease)
+
+  let nextBetaReleaseVersion = 0
+
+  if (fullLastBetaRelease) {
+    const lastBetaReleaseRCVersionArray = fullLastBetaRelease.match(/rc.+[0-9]+/g)
+
+    const lastBetaReleaseRCVersion =
+      lastBetaReleaseRCVersionArray && lastBetaReleaseRCVersionArray.length
+        ? lastBetaReleaseRCVersionArray[0]
+        : null
+
+    const lastBetaReleaseVersion = lastBetaReleaseRCVersion
+      ? lastBetaReleaseRCVersion.split('.')[1]
+      : 0
+
+    nextBetaReleaseVersion = parseInt(lastBetaReleaseVersion, 10) + 1
+  }
+
+  // next beta release version. Output: 1.0.0-beta.1.rc.1
+  const nextBetaReleaseVesionFull = `${package.version}-beta.${issueNumber}.rc.${nextBetaReleaseVersion}`
+
+  // update the beta version on package.json
+  const { error } = await runCommand(
+    `npm version ${nextBetaReleaseVesionFull} --no-git-tag-version`,
+  )
+
+  if (error) {
+    console.error(error)
+    return
+  }
+
+  // the beta version is already updated on package.json on the next line
+  console.log('Next Beta version: ', `${nextBetaReleaseVesionFull}`)
+
+  await runCommand(`echo "NEW_VERSION=${nextBetaReleaseVesionFull}" >> $GITHUB_ENV`)
+}


The AutoBetaRelease function is well-structured and handles the beta release process effectively. However, consider adding error handling for JSON parsing and command execution failures to enhance robustness.

+ try { + const arrayOfBetaReleases = JSON.parse(stdout).filter((version) => + version.includes(`${package.version}-beta.${issueNumber}`), + ); + } catch (error) { + console.error('Failed to parse JSON:', error); + return; + }

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

const AutoBetaRelease = async () => {

// get all the versions of the package from npm

const { stdout } = await runCommand(`npm view . versions --json`)

// show npm published versions of this package

console.log(stdout)

// check if there is a beta release with the same issue number on published versions

const arrayOfBetaReleases = JSON.parse(stdout).filter((version) =>

version.includes(`${package.version}-beta.${issueNumber}`),

)

let fullLastBetaRelease = null

// if yes, get the latest beta release. Output: 1.0.0-beta.1.rc.0

if (arrayOfBetaReleases.length) {

fullLastBetaRelease = arrayOfBetaReleases[arrayOfBetaReleases.length - 1]

}

console.log('Last Beta Release: ', fullLastBetaRelease)

let nextBetaReleaseVersion = 0

if (fullLastBetaRelease) {

const lastBetaReleaseRCVersionArray = fullLastBetaRelease.match(/rc.+[0-9]+/g)

const lastBetaReleaseRCVersion =

lastBetaReleaseRCVersionArray && lastBetaReleaseRCVersionArray.length

? lastBetaReleaseRCVersionArray[0]

: null

const lastBetaReleaseVersion = lastBetaReleaseRCVersion

? lastBetaReleaseRCVersion.split('.')[1]

: 0

nextBetaReleaseVersion = parseInt(lastBetaReleaseVersion, 10) + 1

}

// next beta release version. Output: 1.0.0-beta.1.rc.1

const nextBetaReleaseVesionFull = `${package.version}-beta.${issueNumber}.rc.${nextBetaReleaseVersion}`

// update the beta version on package.json

const { error } = await runCommand(

`npm version ${nextBetaReleaseVesionFull} --no-git-tag-version`,

)

if (error) {

console.error(error)

return

}

// the beta version is already updated on package.json on the next line

console.log('Next Beta version: ', `${nextBetaReleaseVesionFull}`)

await runCommand(`echo "NEW_VERSION=${nextBetaReleaseVesionFull}" >> $GITHUB_ENV`)

}

const AutoBetaRelease = async () => {

// get all the versions of the package from npm

const { stdout } = await runCommand(`npm view . versions --json`)

// show npm published versions of this package

console.log(stdout)

// check if there is a beta release with the same issue number on published versions

try {

const arrayOfBetaReleases = JSON.parse(stdout).filter((version) =>

version.includes(`${package.version}-beta.${issueNumber}`),

);

} catch (error) {

console.error('Failed to parse JSON:', error);

return;

}

let fullLastBetaRelease = null

// if yes, get the latest beta release. Output: 1.0.0-beta.1.rc.0

if (arrayOfBetaReleases.length) {

fullLastBetaRelease = arrayOfBetaReleases[arrayOfBetaReleases.length - 1]

}

console.log('Last Beta Release: ', fullLastBetaRelease)

let nextBetaReleaseVersion = 0

if (fullLastBetaRelease) {

const lastBetaReleaseRCVersionArray = fullLastBetaRelease.match(/rc.+[0-9]+/g)

const lastBetaReleaseRCVersion =

lastBetaReleaseRCVersionArray && lastBetaReleaseRCVersionArray.length

? lastBetaReleaseRCVersionArray[0]

: null

const lastBetaReleaseVersion = lastBetaReleaseRCVersion

? lastBetaReleaseRCVersion.split('.')[1]

: 0

nextBetaReleaseVersion = parseInt(lastBetaReleaseVersion, 10) + 1

}

// next beta release version. Output: 1.0.0-beta.1.rc.1

const nextBetaReleaseVesionFull = `${package.version}-beta.${issueNumber}.rc.${nextBetaReleaseVersion}`

// update the beta version on package.json

const { error } = await runCommand(

`npm version ${nextBetaReleaseVesionFull} --no-git-tag-version`,

)

if (error) {

console.error(error)

return

}

// the beta version is already updated on package.json on the next line

console.log('Next Beta version: ', `${nextBetaReleaseVesionFull}`)

await runCommand(`echo "NEW_VERSION=${nextBetaReleaseVesionFull}" >> $GITHUB_ENV`)

}

coderabbitai · 2024-05-07T19:48:33Z

beta-release.js

+  await runCommand(`echo "NEW_VERSION=${nextBetaReleaseVesionFull}" >> $GITHUB_ENV`)
+}
+
+AutoBetaRelease()


Consider wrapping the AutoBetaRelease function call in a condition or exporting it as a module to provide more control over its execution.

+ if (require.main === module) { + AutoBetaRelease(); + }

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

AutoBetaRelease()

if (require.main === module) {

AutoBetaRelease();

}

danielbarion added the Enhancement label Jan 2, 2024

danielbarion requested a review from gabrieljablonski January 2, 2024 14:09

gabrieljablonski approved these changes Jan 2, 2024

View reviewed changes

gabrieljablonski requested changes Jan 2, 2024

View reviewed changes

gabrieljablonski reviewed Jan 2, 2024

View reviewed changes

.github/workflows/beta-release.yaml Show resolved Hide resolved

danielbarion force-pushed the feat/automated-beta-releases branch from eb3d694 to ab3836b Compare January 2, 2024 19:40

github-actions bot added the Stale This has not seen activity in quite some time label Apr 2, 2024

danielbarion removed the Stale This has not seen activity in quite some time label Apr 2, 2024

danielbarion added 6 commits May 7, 2024 16:42

feat: add beta release workflow

f49c91c

fix: rename bot user name

521b350

fix: rename bot user name to daniel barion

264b711

ci: use personal token instead of github default

52591af

chore: bump version to v5.25.2-beta.1148.5

102cc19

chore: apply changes tested on auto-beta-releases repository

b47e870

danielbarion force-pushed the feat/automated-beta-releases branch from 477f2d1 to b47e870 Compare May 7, 2024 19:43

danielbarion requested a review from gabrieljablonski May 7, 2024 19:47

coderabbitai bot reviewed May 7, 2024

View reviewed changes

gabrieljablonski approved these changes May 8, 2024

View reviewed changes

danielbarion merged commit e59397c into master May 8, 2024
7 checks passed

seangwright mentioned this pull request Jul 8, 2024

[Snyk] Upgrade react-tooltip from 5.26.4 to 5.27.0 Kentico/xperience-by-kentico-azure-ai-search#22

Merged

Matej4545 mentioned this pull request Jul 8, 2024

[Snyk] Upgrade react-tooltip from 5.26.4 to 5.27.0 Kentico/xperience-by-kentico-algolia#48

Open

larinam mentioned this pull request Jul 17, 2024

[Snyk] Upgrade react-tooltip from 5.26.4 to 5.27.0 larinam/vacal#58

Closed

Matej4545 mentioned this pull request Jul 25, 2024

[Snyk] Upgrade react-tooltip from 5.27.0 to 5.27.1 Kentico/xperience-by-kentico-azure-ai-search#23

Merged

filipeoliveiraa mentioned this pull request Aug 4, 2024

[Snyk] Upgrade react-tooltip from 5.10.1 to 5.27.1 filipeoliveiraa/gerev#4

Open

ZeroXClem mentioned this pull request Aug 12, 2024

[Snyk] Upgrade react-tooltip from 5.13.1 to 5.27.1 ZeroXClem/langflow#4

Closed

OKEAMAH mentioned this pull request Aug 26, 2024

[Snyk] Upgrade react-tooltip from 5.26.3 to 5.28.0 https-gitlab-com-OKEAMAH002/web3-Wallet-login#3

Merged

PierreGode mentioned this pull request Sep 4, 2024

[Snyk] Upgrade react-tooltip from 5.26.4 to 5.28.0 PierreGode/authentik#1

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: add beta release workflow #1148

feat: add beta release workflow #1148

danielbarion commented Jan 2, 2024 •

edited

Loading

github-actions bot commented Jan 2, 2024

github-actions bot commented Jan 2, 2024

gabrieljablonski commented Jan 2, 2024

gabrieljablonski left a comment

gabrieljablonski left a comment

danielbarion commented Jan 2, 2024

github-actions bot commented Jan 2, 2024

github-actions bot commented Jan 2, 2024

danielbarion commented Jan 2, 2024

danielbarion commented Jan 2, 2024

github-actions bot commented Jan 2, 2024

github-actions bot commented Apr 2, 2024

coderabbitai bot commented May 7, 2024 •

edited

Loading

Chat

CodeRabbit Commands (invoked as PR comments)

CodeRabbit Configration File (`.coderabbit.yaml`)

Documentation and Community

github-actions bot commented May 7, 2024

coderabbitai bot left a comment

coderabbitai bot May 7, 2024

coderabbitai bot May 7, 2024

-AutoBetaRelease()
+if (require.main === module) {
+  AutoBetaRelease();
+}

feat: add beta release workflow #1148

feat: add beta release workflow #1148

Conversation

danielbarion commented Jan 2, 2024 • edited Loading

Summary by CodeRabbit

github-actions bot commented Jan 2, 2024

github-actions bot commented Jan 2, 2024

gabrieljablonski commented Jan 2, 2024

gabrieljablonski left a comment

Choose a reason for hiding this comment

gabrieljablonski left a comment

Choose a reason for hiding this comment

danielbarion commented Jan 2, 2024

github-actions bot commented Jan 2, 2024

github-actions bot commented Jan 2, 2024

danielbarion commented Jan 2, 2024

danielbarion commented Jan 2, 2024

github-actions bot commented Jan 2, 2024

github-actions bot commented Apr 2, 2024

coderabbitai bot commented May 7, 2024 • edited Loading

Walkthrough

Changes

Poem

Chat

CodeRabbit Commands (invoked as PR comments)

CodeRabbit Configration File (.coderabbit.yaml)

Documentation and Community

github-actions bot commented May 7, 2024

coderabbitai bot left a comment

Choose a reason for hiding this comment

coderabbitai bot May 7, 2024

Choose a reason for hiding this comment

coderabbitai bot May 7, 2024

Choose a reason for hiding this comment

danielbarion commented Jan 2, 2024 •

edited

Loading

coderabbitai bot commented May 7, 2024 •

edited

Loading

CodeRabbit Configration File (`.coderabbit.yaml`)