[DO NOT MERGE] Build CheCode editor image to test PR-363

[vrubezhny]

Opened to create a CheCode editor image to test:

• feat: Enhanced CLI Watcher with automatic terminal process monitoring eclipse-che/che-machine-exec#363

What does this PR do?

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
  • Updated the container image used during the build assembly process to a newer version, which may improve build reliability and consistency.

[github-actions]

Click here to review and test in web IDE:

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c629a322-98df-47c6-9429-44a88c68b6fd

📥 Commits

Reviewing files that changed from the base of the PR and between 5a55387 and eadc22a.

📒 Files selected for processing (1)

• build/dockerfiles/assembly.Dockerfile

---

📝 Walkthrough

Walkthrough

The base image for the machine-exec build stage in assembly.Dockerfile was changed from quay.io/eclipse/che-machine-exec:7.56.0 to quay.io/vrubezhny/che-machine-exec:PR-363. No other Dockerfile logic was modified.

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

Related issues: None specified.

Related PRs: None specified.

Suggested labels: dependencies, build

Suggested reviewers: None specified.

Poem:
A rabbit hopped through Docker's lane,
Swapped one tag, then hopped again,
From eclipse to vrubezhny's fork,
A single line to test the work,
PR-363 now takes the stage! 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is concise, imperative, and clearly relates to building the CheCode editor image for PR-363 testing.
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.
Rebase Rules For Upstream Changes	✅ Passed	Diff vs origin/main changes only build/dockerfiles files; no code/ paths changed, so rebase rules/CHANGELOG/checklist updates aren’t required.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[tolusha]

Hi! I'm che-ai-assistant — I help with your pull requests.

Available commands:

• /che-ai-assistant generate-che-doc — Generate a documentation PR based on this PR's changes
• /che-ai-assistant ok-pr-review — Run a comprehensive PR review (summary, code review, deep review, impact analysis)
• /che-ai-assistant check-pr-test-failures — Analyze failing CI checks, identify root causes, and suggest fixes
• /che-ai-assistant help — Show this help message

[github-actions]

Pull Request images published ✨

Editor amd64: quay.io/che-incubator-pull-requests/che-code:pr-742-amd64
Editor arm64: quay.io/che-incubator-pull-requests/che-code:pr-742-arm64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-742-dev-amd64