Skip to content

Commit

Permalink
chore: just automate binary publishing for now
Browse files Browse the repository at this point in the history
Looks like Taiki's action can't currently handle tags with prefixes,
so they have to be _just_ version strings (see
taiki-e/create-gh-release-action#1).

So, we can consider automatically generating the release when it
supports tags of the format we're using (separate prefixes for each
workspace crate). For now, let's just automate the building and
uploading of release binaries, and manually create the releases...
  • Loading branch information
hawkw committed Dec 17, 2021
1 parent 3da945d commit c3a7660
Showing 1 changed file with 4 additions and 26 deletions.
30 changes: 4 additions & 26 deletions .github/workflows/release.yaml
Original file line number Diff line number Diff line change
@@ -1,34 +1,12 @@
name: Release
name: Upload Binaries

on:
push:
tags:
- console-subscriber-v[0-9]+.*
- console-api-v[0-9]+.*
- tokio-console-v[0-9]+.*
release:

jobs:
create-release:
# only publish from the origin repository
if: github.repository_owner == 'tokio-rs'
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: extract tag
id: tag
run:
echo ::set-output name=TAG::$(echo $GITHUB_REF | sed -r 's/.*(console-subscriber|console-api|tokio-console).*/\1/')
- uses: taiki-e/create-gh-release-action@v1
with:
changelog: ${{ steps.tag.outputs.TAG }}/CHANGELOG.md
branch: main
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

upload-bins:
# only upload binaries if we're on the origin repository and if the tag is a
# `tokio-console` release
if: ${{ github.repository_owner == 'tokio-rs' && contains(github.ref, 'tokio-console') }}
# only upload binaries if the tag is a`tokio-console` release
if: contains(github.ref, 'tokio-console')
strategy:
matrix:
os: [ubuntu-latest, macos-latest, windows-latest]
Expand Down

0 comments on commit c3a7660

Please sign in to comment.