updated the action to modify the release build assets

[mguptahub]

Description

APP_RELEASE in the release assets (docker-compose.yml and variables.env) will default to the release version created

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Improvement (change that would cause existing functionality to not work as expected)
• Code refactoring
• Performance improvements
• Documentation update

Screenshots and Media (if applicable)

Test Scenarios

References

Summary by CodeRabbit

• Chores
  • Streamlined the release process by consolidating asset handling during publishing.
  • Updated environment configuration settings to ensure the release version is correctly applied.

[coderabbitai]

Walkthrough

The changes remove the attach_assets_to_build job from the GitHub Actions workflow in the build-branch file. Additionally, the publish_release job has been updated by removing the dependency on the removed job and adding two sed commands to update the docker-compose.yml and variables.env files with the release version during a Release build.

Changes

File(s)	Change Summary
.github/workflows/build-branch.yml	- Job Removal: Removed the attach_assets_to_build job previously responsible for attaching assets to a release build. - Job Update: In the publish_release job, removed the dependency on the removed job and added two sed commands to update docker-compose.yml and variables.env with the release version.

Sequence Diagram(s)

sequenceDiagram
    participant CI as GitHub Actions
    participant PR as publish_release Job
    CI->>PR: Trigger release build (Release type)
    Note right of PR: Removed dependency on attach_assets_to_build
    PR->>PR: Update docker-compose.yml via sed command
    PR->>PR: Update variables.env via sed command
    PR-->>CI: Complete release process

Loading

Possibly related PRs

• fix: Modified Branch-Build to support Release #5803: Involves similar changes with regard to the asset attachment job and modifications within the publish_release job.
• improvement: build action improvement #6248: Addresses workflow configuration updates in the same file, specifically targeting job dependencies and release process modifications.

Suggested labels

🏠self-hosted

Suggested reviewers

• sriramveeraghanta

Poem

Hop, hop, I’m a bunny coder on the run,
Trimming workflows to make our release fun.
Assets now handled with a simple sed twist,
No extra job to manage—nothing is missed!
With whiskers twitching, I celebrate this clean run 🐰!
Enjoy the hop into a leaner, brighter build!

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • 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 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 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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/build-branch.yml (1)

324-327: Refactor Sed Commands for Enhanced Readability and Correct Variable Expansion

Currently, the sed commands in the "Update Assets" step are written with a mix of single quotes and inline variable concatenation. This approach can be error-prone and slightly confusing when it comes to ensuring that the shell correctly expands variables such as REL_VERSION. Using double quotes consistently will simplify the commands and reduce potential quoting issues.

Suggested Diff:

-          sed -i 's/${APP_RELEASE:-stable}/${APP_RELEASE:-'${REL_VERSION}'}/g' deploy/selfhost/docker-compose.yml
-          sed -i 's/APP_RELEASE=stable/APP_RELEASE='${REL_VERSION}'/g' deploy/selfhost/variables.env
+          sed -i "s/\${APP_RELEASE:-stable}/\${APP_RELEASE:-${REL_VERSION}}/g" deploy/selfhost/docker-compose.yml
+          sed -i "s/APP_RELEASE=stable/APP_RELEASE=${REL_VERSION}/g" deploy/selfhost/variables.env

This refactoring not only improves clarity but also ensures reliable variable expansion, which is key for correctly updating the release assets.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between aa0b2c0 and 214285c.

📒 Files selected for processing (1)

• .github/workflows/build-branch.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Analyze (javascript)
• GitHub Check: Analyze (python)