🐛 Remove windup-shim from create-release changelog generation

[jmontleon]

Summary by CodeRabbit

• Chores
  • Updated release workflow configuration by removing an unused component from the batch release process.

[coderabbitai]

Walkthrough

Removed konveyor/windup-shim from the GitHub Actions release workflow, specifically deleting it from the unified changelog repository list and the release-components matrix. This prevents the repository from being included in batch release processes.

Changes

Cohort / File(s)	Summary
Release Workflow Configuration \..github/workflows/create-release.yml	Removed konveyor/windup-shim from the changelog repository list and release-components matrix, eliminating it from the automated release pipeline

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single file modification with straightforward removal of two repository references from workflow configuration
• No logic changes or control-flow modifications

Possibly related PRs

• ✨ Update create-release.yml to remove windup-shim from release #473: Removes konveyor/windup-shim from the same GitHub Actions release workflow
• ✨ Update create-release.yml to remove duplicate kantra repo #475: Modifies the same workflow file to remove duplicate entries from the release-components matrix

Suggested labels

cherry-pick/release-0.8

Suggested reviewers

• djzager
• aufi

Poem

🐰 One shimmer removed from the release machine,
No more windup echoes in the workflow scene,
Cleaner pipelines, simpler flows,
Where the release process gracefully goes!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately and specifically describes the main change: removing windup-shim from the create-release changelog generation workflow.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

Tip

📝 Customizable high-level summaries are now available!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  - Provide custom instructions to shape the summary (bullet lists, tables, contributor stats, etc.).
  - Use `high_level_summary_in_walkthrough` to move the summary from the description to the walkthrough section.

  Example:

  > "Create a concise high-level summary as a bullet-point list. Then include a Markdown table showing lines added and removed by each contributing author."

  Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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.}

[fabianvf]

Have we dropped conversion support? I think this was used by the hub to convert old windup rules to the new format. Lgtm if we've stopped supporting the old rules though

[jmontleon]

Maybe I am mistaken. I thought we stopped using it. Do we instead need to do something to generate a release for the repo so it doesn't stop up the release process when it tries to generate a changelog?

[fabianvf]

I think you're right @jmontleon