docs: note bundle is still needed for rhoai branch

[kahowell]

Description

How Has This Been Tested?

Screenshot or short clip

Merge criteria

• You have read the contributors guide.
• Commit messages are meaningful - have a clear and concise summary and detailed explanation of what was changed and why.
• Pull Request contains a description of the solution, a link to the JIRA issue, and to any dependent or related Pull Request.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work
• The developer has run the integration test pipeline and verified that it passed successfully

E2E test suite update requirement

When bringing new changes to the operator code, such changes are by default required to be accompanied by extending and/or updating the E2E test suite accordingly.

To opt-out of this requirement:

1. Please inspect the opt-out guidelines, to determine if the nature of the PR changes allows for skipping this requirement
2. If opt-out is applicable, provide justification in the dedicated E2E update requirement opt-out justification section below
3. Check the checkbox below:

• Skip requirement to update E2E test suite for this PR

4. Submit/save these changes to the PR description. This will automatically trigger the check.

E2E update requirement opt-out justification

docs change

Summary by CodeRabbit

• Documentation
  • Added guidance to the release workflow clarifying that generated bundles must be regenerated in downstream sync pull requests because the main branch no longer retains most generated files.

[coderabbitai]

Walkthrough

Added a step to the release workflow guide instructing that the release bundle must be regenerated in sync PRs because the main branch no longer keeps most generated files while downstream rhoai branch builds still require bundle contents.

Changes

Cohort / File(s)	Summary
Documentation update docs/release-workflow-guide.md	Added a new step explaining bundle regeneration in sync PRs (references PR #2329) and clarifies branch responsibilities for generated files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Possible minor copy edits in docs/release-workflow-guide.md (verify spelling/grammar, e.g., "Regenerate").

Poem

🐰 I hopped through branches, neat and sound,
Found bundles hiding, not where they're bound,
In sync PRs I give them light,
So downstream builds run just right,
A tidy hop — the release is found! 📦✨

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the main documentation change—adding a note about bundle regeneration being needed for the rhoai branch.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f889796 and f492d22.

📒 Files selected for processing (1)

• docs/release-workflow-guide.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/release-workflow-guide.md

⏰ 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: golangci-lint

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9fd7486 and f889796.

📒 Files selected for processing (1)

• docs/release-workflow-guide.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/release-workflow-guide.md

[grammar] ~59-~59: Ensure spelling is correct
Context: ...iption to include the ticket link. 3. Renegerate the bundle: As of [#2329](https://git...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

⏰ 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: golangci-lint

🔇 Additional comments (1)

docs/release-workflow-guide.md (1)

54-62: Documentation addition looks good.

The new step correctly documents the bundle regeneration requirement in sync PRs, provides clear rationale (referencing #2329 and explaining the downstream dependency), and fits naturally into the upstream workflow sequence.

[zdtsw]

should we also mention, if PR touches API config etc should not use "cherrypick" bot instead of create manual PR?

[kahowell]

It should still be fine in that case, as the API change will cherry-pick cleanly.

It simply won't pass CI checks, specifically, the one in .github/workflows/test-required-files-updated.yaml, so it will require an extra step.

FYI I also have red-hat-data-services#13421 open to remove the need to maintain bundle in the repo in rhoai branch.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zdtsw

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [zdtsw]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[zdtsw]

i'd prefer this goes in ODH 3.1 release