refactor(ci): replace release workflows with release-pilot

[Arthurdw]

Summary

Integrates release-pilot to simplify release management, replacing 3 custom workflows with a single action + config file.

Changes

• Add .github/release-pilot.yml configuration for multi-crate workspace
• Replace dev_release.yml, weekly_release.yml, and deploy.yml with unified release.yml
• Enable auto-update of version references in README on release
• 78% code reduction: ~580 → ~130 lines of workflow code

Release Behavior (unchanged)

Trigger	Mode	Result
Push to main	dev	Pre-release (e.g., 1.2.1-dev.ml2fz8yd)
Wednesday 9AM UTC	stable	Stable release with version bump
Manual dispatch	choice	Either dev or stable

Features

• PR labels (release:major/minor/patch) determine version bump
• Crates published in dependency order: arri_common → ronky_derive → arri_repr → ronky
• 30s delay between crate publishes for crates.io indexing
• Auto-generated GitHub release notes
• README version references auto-updated on release

Summary by CodeRabbit

Release Notes

• New Features

  • Added manual release triggering with mode selection (stable/dev) alongside scheduled releases.

• Chores

  • Updated release automation infrastructure with new GitHub Release Pilot system for improved version management and publishing workflows.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This refactoring consolidates release automation across the ronky workspace by replacing multiple custom GitHub Actions workflows with a unified release-pilot configuration. Three workflows are removed and the primary release workflow is restructured to use the new release-pilot action with configurable release modes.

Changes

Cohort / File(s)	Summary
Release Pilot Configuration \.github/release-pilot\.yml	New configuration file defining cargo crates, release ordering, versioning policy (patch default with dev releases), git operations, publishing options, and README version auto-update via pattern replacement.
Removed Release Workflows \.github/workflows/deploy\.yml, \.github/workflows/dev_release\.yml, \.github/workflows/weekly_release\.yml	Deleted three workflows: deploy.yml (crates.io publication), dev_release.yml (dev release pipeline with version calculation and GitHub pre-releases), and weekly_release.yml (scheduled weekly release automation with PR label aggregation).
Refactored Main Release Workflow \.github/workflows/release\.yml	Replaced tag-based triggering with branch-based/scheduled triggers and manual dispatch with mode input (stable/dev). Removed build and version extraction steps. Introduced mode-determination logic and replaced gh-release with a-line-services/release-pilot action. Added pull-requests read permission.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

• fix(ci): collect ALL PR labels since last STABLE release #252: Updates dev_release.yml and weekly_release.yml to use last stable release detection and PR label aggregation—while this PR removes those same workflows in favor of release-pilot configuration.
• fix(ci): fix release detection with correct gh api syntax #253: Modifies dev_release.yml and weekly_release.yml release-detection logic—overlaps with workflows being removed in this PR.
• fix(ci): fix PR label detection and add dev releases #250: Adds/fixes dev_release.yml and weekly_release.yml functionality—opposite direction from this PR which removes/consolidates those workflows.

Poem

🐰 Release pipelines now align,
One config makes workflows shine so fine,
No more scattered yaml here and there,
Release-pilot handles the care! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title directly and accurately describes the main change: replacing three custom release workflows with the release-pilot tool and adding its configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/release-pilot-integration

---

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