Release candidates

[samcday]

As part of #141 we want to join the Phosh release train. Which is pulling away from the station right just meow: 0.53_rc1 tag was just cut in the main Phosh repo.

[samcday]

/oc what gaps in our release machinery (.github/workflows/release.yml and friends) to handle prerelease/release-candidate-y things like this?

[opencode-agent]

Here’s what I see as the current gaps for prerelease/RC handling in .github/workflows/release.yml and related flows:

• release.yml publishes a release for every tag and never marks prereleases; softprops/action-gh-release supports prerelease: true but it’s not set, so 0.53_rc1 would look like a full release. File: .github/workflows/release.yml
• Tag matching is '*', so any tag (including non-version tags) triggers release creation; there’s no semver or RC pattern gate to avoid accidental releases. File: .github/workflows/release.yml
• The build workflow runs on release published, and the demo artifacts are uploaded for any published release, including RCs; you may want RCs to publish but not update release assets or the README demo reference (if you want those reserved for stable). File: .github/workflows/build.yml
• There’s no explicit linkage between tag naming conventions (0.53_rc1 vs 0.53.0-rc.1) and release metadata, so RCs won’t show as prerelease unless you set prerelease: ${{ contains(github.ref_name, 'rc') }} or a tighter regex. File: .github/workflows/release.yml
• No explicit changelog gating or “RC vs stable” note in the release body; release notes are always auto-generated, which can be fine but may be noisy for release trains. File: .github/workflows/release.yml

If you want, I can propose concrete changes (e.g., tag filters and prerelease detection for _rc/-rc formats, plus optional demo upload gating).

opencode session  |  github run

[samcday]

/oc aight raise a PR that does the needful to set prerelease: correctly based on _rc[0-9]+ suffix of tag.

I recently introduced this silly little justfile in another project:

# smoo development tasks

# Bump version across all packaging files
bump version:
    #!/usr/bin/env bash
    set -euo pipefail

    echo "Bumping smoo to {{version}}"

    # Cargo.toml workspace version
    sed -i 's/^version = ".*"/version = "{{version}}"/' Cargo.toml

    # RPM spec
    sed -i 's/^Version:        .*/Version:        {{version}}/' smoo.spec

    # Alpine APKBUILD (set base version, keep _git suffix for dev builds)
    sed -i 's/^pkgver=.*_git$/pkgver={{version}}_git/' APKBUILD

    # Debian changelog (add new entry)
    sed -i '1s/.*/smoo ({{version}}) UNRELEASED; urgency=medium/' debian/changelog

    # Update lockfile
    cargo generate-lockfile

    echo "Done. Files updated:"
    echo "  Cargo.toml"
    echo "  smoo.spec"
    echo "  APKBUILD"
    echo "  debian/changelog"
    echo ""
    echo "Next steps:"
    echo "  1. Review changes: git diff"
    echo "  2. Commit: git commit -am 'v{{version}}'"
    echo "  3. Tag: git tag v{{version}}"
    echo "  4. Push: git push && git push --tags"

The idea is to trivialize the "version bump" across the project. Add something like this in your PR, but make it also support the _rc notion of the version string, and skip bumping the README.md demo video URL in that case (I've just been manually bumping that each release).

We'll keep doing autogenerated notes for now because I am exceedingly lazy.

[opencode-agent]

Created PR #158

opencode session  |  github run