Skip to content

Conversation

@kolipakakondal
Copy link
Collaborator

@kolipakakondal kolipakakondal commented Jul 25, 2025

Description

Please include a summary of the change and which issue is fixed.

Fixes # (IEP-XXX)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How has this been tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Test Configuration:

  • ESP-IDF Version:
  • OS (Windows,Linux and macOS):

Dependent components impacted by this PR:

  • Component 1
  • Component 2

Checklist

  • PR Self Reviewed
  • Applied Code formatting
  • Added Documentation
  • Added Unit Test
  • Verified on all platforms - Windows,Linux and macOS

Summary by CodeRabbit

  • Chores
    • Removed the "Beta builds" workflow from the automated build system.
    • Updated the release workflow to handle both stable and beta releases, ensuring beta builds are uploaded and accessible under a dedicated "beta" path.

@coderabbitai
Copy link

coderabbitai bot commented Jul 25, 2025

Walkthrough

The "Beta builds" GitHub Actions workflow was deleted, removing automated beta build and deployment. The main release workflow was updated to handle both stable and beta tags, dynamically adjusting S3 upload and redirect paths based on the release type, and consolidating beta and stable asset handling into a single pipeline.

Changes

File(s) Change Summary
.github/workflows/ci_beta.yml Deleted the entire "Beta builds" workflow, removing all beta build, sign, notarize, and upload steps.
.github/workflows/ci_release.yml Updated to support both stable and beta tags; added logic to set S3/upload paths based on tag type.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

The beta bunny hops away,
No more double builds today!
Now one flow for all our tags—
Beta or stable, it swiftly drags
Each artifact to its proper den,
Release and beta, both with zen.
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch IEP-1606

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🔭 Outside diff range comments (1)
.github/workflows/ci_release.yml (1)

323-332: Hard-coded bucket name espdldata bypasses ${{ secrets.DL_BUCKET }}
Earlier commands honor the secret bucket variable; these four aws s3api put-object calls do not.
If the bucket ever changes, the redirects will silently break.

-        aws s3api put-object --acl=public-read --bucket espdldata --key ...
+        aws s3api put-object --acl=public-read --bucket ${{ secrets.DL_BUCKET }} --key ...
🧹 Nitpick comments (2)
.github/workflows/ci_release.yml (2)

58-59: Trailing whitespace – please clean up for linting compliance
Line 58 contains only indentation + spaces; YAML-lint flags it.
Not functional, but it breaks yamllint -d relaxed.


260-277: Minor shell-safety improvements for version parsing block

  1. Wrap variable expansions in double-quotes to avoid word-splitting problems if the tag is ever malformed.
  2. IS_BETA can be exported directly instead of using an intermediate variable.
-        TAG="${GITHUB_REF##*/}"
-        VERSION="${TAG#v}"
+        TAG="${GITHUB_REF##*/}"
+        VERSION="${TAG#v}"

         if [[ "$TAG" == *"-beta"* ]]; then
-          IS_BETA="true"
+          IS_BETA=true
           UPLOAD_PATH="beta"
           REDIRECT_PATH="beta"
         else
-          IS_BETA="false"
+          IS_BETA=false
           UPLOAD_PATH="latest"
           REDIRECT_PATH="latest"
         fi

Not critical, but it tightens the script.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4ca55bc and 985f115.

📒 Files selected for processing (2)
  • .github/workflows/ci_beta.yml (0 hunks)
  • .github/workflows/ci_release.yml (4 hunks)
💤 Files with no reviewable changes (1)
  • .github/workflows/ci_beta.yml
🧰 Additional context used
🪛 actionlint (1.7.7)
.github/workflows/ci_release.yml

7-7: character '' is invalid for branch and tag names. only special characters [, ?, +, *, , ! can be escaped with . see man git-check-ref-format for more details. note that regular expression is unavailable. note: filter pattern syntax is explained at https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet

(glob)


7-7: character '' is invalid for branch and tag names. only special characters [, ?, +, *, , ! can be escaped with . see man git-check-ref-format for more details. note that regular expression is unavailable. note: filter pattern syntax is explained at https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet

(glob)

🪛 YAMLlint (1.37.1)
.github/workflows/ci_release.yml

[error] 58-58: trailing spaces

(trailing-spaces)


[error] 316-316: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build_macos
🔇 Additional comments (1)
.github/workflows/ci_release.yml (1)

302-306: aws s3 rm wipes the whole channel before upload – risk of race conditions
If two workflows (e.g., two parallel beta builds) run concurrently, the second job can delete assets uploaded by the first.
Consider either:
• using versioned folders only, and keeping latest/beta as redirects, or
• moving the rm call after a successful cp --recursive with the --exclude "*" --include "*.tmp" pattern.

Flagging for your awareness.

Comment on lines 5 to 8
tags:
- "v[0-9]+.[0-9]+.[0-9]+"
- "v[0-9]+\\.[0-9]+\\.[0-9]+-beta"

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Tag-filter glob is syntactically invalid – workflow will never trigger on beta tags
GitHub Actions push.tags uses simple glob patterns, not regex.
Characters like + and the escaped \. are illegal in this context and will be rejected by the runner (actionlint already flags this).

-      - "v[0-9]+\\.[0-9]+\\.[0-9]+-beta"
+      - "v*-beta"

If you really want to constrain the number of numeric sections, you can use:

- "v[0-9]*.[0-9]*.[0-9]*-beta"

but keep the asterisks and drop the backslashes & plus signs.
Failing to fix this will block every beta release.

🧰 Tools
🪛 actionlint (1.7.7)

7-7: character '' is invalid for branch and tag names. only special characters [, ?, +, *, , ! can be escaped with . see man git-check-ref-format for more details. note that regular expression is unavailable. note: filter pattern syntax is explained at https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet

(glob)


7-7: character '' is invalid for branch and tag names. only special characters [, ?, +, *, , ! can be escaped with . see man git-check-ref-format for more details. note that regular expression is unavailable. note: filter pattern syntax is explained at https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet

(glob)

🤖 Prompt for AI Agents
In .github/workflows/ci_release.yml around lines 5 to 8, the tag filter uses
invalid regex syntax with plus signs and escaped dots, which GitHub Actions does
not support for push.tags. Replace the regex patterns with valid glob patterns
by removing plus signs and backslashes, and use asterisks instead, for example,
change "v[0-9]+\\.[0-9]+\\.[0-9]+-beta" to "v[0-9]*.[0-9]*.[0-9]*-beta" to
ensure the workflow triggers correctly on beta tags.

@kolipakakondal kolipakakondal merged commit 58212c5 into master Jul 29, 2025
2 of 5 checks passed
@kolipakakondal kolipakakondal deleted the IEP-1606 branch July 29, 2025 08:19
kolipakakondal added a commit that referenced this pull request Jul 29, 2025
* ci: update the beta workflow and merge release&beta ci
@coderabbitai coderabbitai bot mentioned this pull request Sep 24, 2025
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants