feat: add release workflows (#22)

This commit is contained in:
Hikari (ひかり) 2024-01-27 15:58:19 -06:00 committed by GitHub
parent 331b91df35
commit d347071dde
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
4 changed files with 135 additions and 17 deletions

2
.github/CODEOWNERS vendored
View file

@ -1 +1 @@
* @gmpinder
* @gmpinder @akarui-hikarii

57
.github/workflows/post-release.yml vendored Normal file
View file

@ -0,0 +1,57 @@
name: Post-release version bump
# how to trigger: https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow
on:
workflow_dispatch:
env:
CARGO_TERM_COLOR: always
jobs:
ci:
if: github.repository == 'blue-build/cli'
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Install cargo-release
run: cargo install cargo-release
- name: Git setup
run: |
git config user.name github-actions
git config user.email github-actions@github.com
- name: Setup post-release version bump
run: |
# Read the current version from Cargo.toml
current_version=$(cargo metadata --format-version 1 --no-deps | \
jq --raw-output '.packages | .[] | select(.name == "blue-build").version')
# Sanity check: current version should be 0.X.Y
if ! grep -q '^0\.[0-9]\+\.[0-9]\+$' <<< "${current_version}"; then
echo "Invalid version (not in 0.X.Y format): ${current_version}"
exit 1
fi
minor_version=$(sed 's/^0\.\([0-9]\+\).*/\1/' <<< "${current_version}")
next_version=0.$((minor_version + 1)).0-dev
echo "Bumping version to ${next_version}"
# See release.yml for meaning of these arguments
cargo release "${next_version}" \
--workspace \
--no-publish \
--no-tag \
--no-confirm \
--no-push
- name: Create PR
uses: peter-evans/create-pull-request@v5
with:
delete-branch: true
base: "main"
title: "Bump Version after Release"
body: |
Bump version after release
This PR has been auto-generated

View file

@ -8,6 +8,7 @@ env:
jobs:
release:
if: github.repository == 'blue-build/cli'
runs-on: ubuntu-latest
permissions:
id-token: write
@ -18,10 +19,9 @@ jobs:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Git setup
run: |
git config user.name github-actions
git config user.email github-actions@github.com
- uses: chainguard-dev/actions/setup-gitsign@main
- uses: actions/cache@v4
with:
path: |
@ -32,17 +32,40 @@ jobs:
~/.cargo/registry/cache/
key: ${{ runner.os }}-cargo-build-stable-${{ hashFiles('**/Cargo.toml') }}
- uses: chainguard-dev/actions/setup-gitsign@main
# Pulling rust toolchain & install linux dependencies
- uses: dtolnay/rust-toolchain@stable
- name: Install cargo-release
uses: taiki-e/install-action@v1
with:
tool: cargo-smart-release
run: cargo install cargo-release
- name: Release
env:
CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
run: cargo smart-release -ue
- name: Git setup
run: |
git config user.name github-actions
git config user.email github-actions@github.com
# Leaving bevy comments here for us to discuss. Do we want to start tagging our pre-releases with `dev`?
- name: Setup release
run: |
# release: remove the dev suffix, like going from 0.X.0-dev to 0.X.0
# --workspace: updating all crates in the workspace
# --no-publish: do not publish to crates.io
# --execute: not a dry run
# --no-tag: do not push tag for each new version
# --no-push: do not push the update commits
# --dependent-version upgrade: change 0.X.0-dev in internal dependencies to 0.X.0
# --exclude: ignore those packages
cargo release release \
--workspace \
--no-publish \
--execute \
--no-tag \
--no-confirm \
--no-push \
--dependent-version upgrade
- name: Create PR
uses: peter-evans/create-pull-request@v5
with:
delete-branch: true
base: "main"
title: "Preparing Next Release"
body: |
Preparing next release
This PR has been auto-generated