Skip to content

chore: align machine-exec version with che-code version at release - #780

Open
mkuznyetsov wants to merge 1 commit into
mainfrom
machine-exec-release
Open

chore: align machine-exec version with che-code version at release#780
mkuznyetsov wants to merge 1 commit into
mainfrom
machine-exec-release

Conversation

@mkuznyetsov

@mkuznyetsov mkuznyetsov commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

If machine-exec's newest version is meant to be used in the same version of the code.
Then release script should update the reference during release commit creation.

This PR should be merged after #748

What issues does this PR fix?

How to test this PR?

Does this PR contain changes that override default upstream Code-OSS behavior?

  • the PR contains changes in the code folder (you can skip it if your changes are placed in a che extension )
  • the corresponding items were added to the CHANGELOG.md file
  • rules for automatic git rebase were added to the .rebase folder

Summary by CodeRabbit

  • Chores
    • Release packaging now automatically keeps the container image version aligned with the selected release version.

Signed-off-by: Mykhailo Kuznietsov <mkuznets@redhat.com>
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Click here to review and test in web IDE: Contribute

@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: da8803cd-b001-459f-9062-c719ecc62cc7

📥 Commits

Reviewing files that changed from the base of the PR and between 9961a7d and acaafc2.

📒 Files selected for processing (1)
  • make-release.sh

📝 Walkthrough

Walkthrough

After updating package.json, make-release.sh updates the che-machine-exec image tag in build/dockerfiles/assembly.Dockerfile to ${VERSION}.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: rgrunber, azatsarynnyy, vitaliy-guliy, romannikitenko

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Rebase Rules For Upstream Changes ❓ Inconclusive Repository clone failed, so this custom check could not run with code access. Retry the review run. If this persists, inspect pre-merge custom-check logs for infrastructure or agent runtime failures.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title is concise, uses the imperative verb "align," and clearly describes the release version update.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch machine-exec-release

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

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

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