EFForg/rayhunter

A full release workflow

Open

#1,031 opened on May 12, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (431 forks)github user discovery
enhancementhelp wantedmaintenance

Repository metrics

Stars
 (5,271 stars)
PR merge metrics
 (PR metrics pending)

Description

Prerequisites

What problem does this feature solve or what does it enhance?

there are too many manual steps in the release process described in CONTRIBUTING.md:

  1. the sed call there has been out of date many times, and it actually only works on macos right now (had to make changes to run it on ubuntu)
  2. naming your own tag and pushing it is a lot

Proposed Solution

release.yml workflow should cover the entire thing:

  1. make a PR with the necessary changes
  2. after approval, trigger another workflow to auto-merge and make the tag, push the tag automatically
  3. make the github release (this is the part that already exists)

Not hellbent on this exact solution, but the more we can automate, the better

Whoever picks this up can fork the rayhunter repo onto their private account and manually test the workflow there.

Alternatives Considered

no

Contributor guide

Research direction
Review CONTRIBUTING.md for the existing release steps and design a GitHub Actions workflow that automates the entire release process, including version bump, tagging, and releasing. Test the workflow on a fork.
Tech stack
rust
Domain
devopsci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70