✨ Update create-release.yml to remove windup-shim from release

[dymurray]

Summary by CodeRabbit

• Chores
  • Streamlined the release workflow by removing redundant steps, reducing release time and complexity.
  • No changes to product functionality; all other release components continue unaffected.

[coderabbitai]

Walkthrough

Removed two steps from the GitHub Actions release workflow: the windup-shim release step and the subsequent wait-for-windup-shim step. All other release steps remain unchanged.

Changes

Cohort / File(s)	Summary
Release workflow updates \.github/workflows/create-release.yml	Removed windup-shim release step and the following wait-for-windup-shim step from the release-bases job; retained other release steps (rulesets, static-report, java-analyzer-bundle, analyzer-lsp, tackle2-addon-analyzer, tackle2-addon-discovery, tackle2-addon-platform).

Sequence Diagram(s)

sequenceDiagram
  participant GH as GitHub Actions
  participant Job as release-bases job

  Note over GH,Job: Previous flow (before)
  GH->>Job: run rulesets
  GH->>Job: run static-report
  GH->>Job: run java-analyzer-bundle
  GH->>Job: run analyzer-lsp
  GH->>Job: run windup-shim  <<removed>>
  GH->>Job: wait-for-windup-shim  <<removed>>
  GH->>Job: run tackle2-addon-analyzer
  GH->>Job: run tackle2-addon-discovery
  GH->>Job: run tackle2-addon-platform

  rect #eef7ff
  Note over GH,Job: Current flow (after)
  GH->>Job: run rulesets
  GH->>Job: run static-report
  GH->>Job: run java-analyzer-bundle
  GH->>Job: run analyzer-lsp
  GH->>Job: run tackle2-addon-analyzer
  GH->>Job: run tackle2-addon-discovery
  GH->>Job: run tackle2-addon-platform
  end

Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I snipped two hops from the release-time vine,
A brisker path, still orderly, fine.
Thump-thump go paws on YAML’s trail—
Steps removed, no other tale.
Carrots cached, the pipelines chime,
Ship it swift, in bunny time! 🥕🚀

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.
Title Check	✅ Passed	The PR title accurately and directly summarizes the main change in the diff—updating create-release.yml to remove the windup-shim release steps—so it clearly communicates the primary intent to reviewers. It is concise and specific enough for scanning history, with the emoji being purely cosmetic.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dymurray-patch-1

---

📜 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 c486e8a and c06ee7b.

📒 Files selected for processing (1)

• .github/workflows/create-release.yml (0 hunks)

💤 Files with no reviewable changes (1)

• .github/workflows/create-release.yml

⏰ 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: build-operator-bundle

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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