chore(ci): retire 3 workflows violating python-app type spec

[williaby]

Removes workflows that violate the python-app type specification or provide zero value:

• release.yml: python-app repos are exempt from release workflows
• sbom.yml: python-app repos are exempt from SBOM workflows
• repo-health.yml: echo-only stub with no functionality

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow configuration files; removed SBOM validation workflow and made adjustments to release and health check workflows for internal CI/CD processes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 092f8a31-b7c7-4ff1-8c22-fd228a50af59

📥 Commits

Reviewing files that changed from the base of the PR and between dd37ec0 and 8106635.

📒 Files selected for processing (3)

• .github/workflows/release.yml
• .github/workflows/repo-health.yml
• .github/workflows/sbom.yml

💤 Files with no reviewable changes (3)

• .github/workflows/repo-health.yml
• .github/workflows/release.yml
• .github/workflows/sbom.yml

---

📝 Walkthrough

Walkthrough

This PR removes three GitHub Actions workflow files: release publishing, repository health checking, and SBOM generation. Each workflow had previously automated specific tasks on pushes and pull requests to the main branch.

Changes

Workflow Removals

Layer / File(s)	Summary
Deleted Workflows .github/workflows/release.yml, .github/workflows/repo-health.yml, .github/workflows/sbom.yml	Three workflows are removed: release publishing (54 lines), repository health checking (15 lines), and SBOM generation (68 lines).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A rabbit hops through workflows old,
Three pipelines fold and disappear,
Release, health, and SBOM stories told—
Clean paths remain, the way is clear! 🐰✨

🚥 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 clearly and concisely describes the main change: retiring three GitHub Actions workflows that violate the python-app type specification.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/retire-excess-workflows

---

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

[Copilot]

🔵 Needs a closer look

The removed sbom.yml workflow is still referenced by other repository files (e.g., CI failure report template and YAML lint file list), which should be updated to avoid stale references.

Pull request overview

This PR retires GitHub Actions workflows (release.yml, sbom.yml, repo-health.yml) that reportedly violate the python-app type specification or provide no meaningful CI value, simplifying the repository’s CI/CD surface area.

Changes:

• Removed the SBOM generation/validation workflow (.github/workflows/sbom.yml).
• Removed the semantic-release automation workflow (.github/workflows/release.yml).
• Removed an echo-only repo health workflow (.github/workflows/repo-health.yml).

File summaries

File	Description
.github/workflows/sbom.yml	Deletes the SBOM workflow from this repo.
.github/workflows/repo-health.yml	Deletes a stub “repo health” workflow with no functional checks.
.github/workflows/release.yml	Deletes the semantic-release workflow from this repo.

Review details

Suppressed comments (1)

.github/workflows/sbom.yml:1

• Removing this workflow leaves a few stale references to sbom.yml elsewhere in the repo (e.g. .github/ISSUE_TEMPLATE/ci-failure-report.md checklist and scripts/lint-yaml.txt file list). Those should be updated/removed in the same PR to avoid confusing CI-failure reports and any tooling that iterates that list.

• Files reviewed: 3/3 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.