chore: remove rolling dev pre-release in favor of explicit alpha/beta tags

[wassupluke]

Summary

• Deletes prerelease.yml — the rolling dev build on every push to main
• release.yml already handles alpha/beta: any v* tag with a hyphen is automatically marked as a pre-release
• Updates README with verified-release workflow (always tag after PR merge on GitHub)
• Deleted the dev release and tag from GitHub

Why

Rolling dev builds are redundant when explicit versioned pre-releases exist. They clutter the releases page and give testers no useful version signal.

Summary by Sourcery

Document and enforce an explicit tag-based release and pre-release process while removing the unused rolling prerelease workflow.

CI:

• Remove the prerelease GitHub Actions workflow in favor of the existing tag-driven release workflow.

Documentation:

• Update README to describe tagging merged main commits for verified stable and pre-release builds, and clarify how tags trigger the release workflow.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Removes the rolling dev prerelease workflow in favor of explicit, tagged alpha/beta prereleases, and updates the README to describe the new, verified release and prerelease tagging process that drives the existing release workflow.

File-Level Changes

Change	Details	Files
Document a GitHub-verified release and prerelease tagging workflow using versioned tags on merged commits.	Replaces generic local tagging instructions with a workflow that checks out and pulls main after merging on GitHub. Shows explicit examples for stable release tags (e.g., v1.0.0) and pre-release tags (e.g., v1.0.0-alpha) and how to push them. Explains that any v* tag triggers the existing release workflow and that tags containing a hyphen are automatically marked as pre-releases.	README.md
Remove the rolling dev prerelease GitHub Actions workflow in favor of tagged prereleases handled by the existing release workflow.	Deletes the .github/workflows/prerelease.yml workflow file so pushes to main no longer create an automatic dev prerelease build. Relies on .github/workflows/release.yml (unchanged in this diff) to handle both stable and pre-release builds triggered by version tags. Aligns the CI configuration with the documented alpha/beta tagging strategy and the manual deletion of the old dev release/tag in GitHub.	.github/workflows/prerelease.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}