Skip to content

Commit 802ee42

Browse files
committed
chore: just automate binary publishing for now
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...
1 parent 3da945d commit 802ee42

File tree

1 file changed

+5
-26
lines changed

1 file changed

+5
-26
lines changed

.github/workflows/release.yaml

+5-26
Original file line numberDiff line numberDiff line change
@@ -1,34 +1,13 @@
1-
name: Release
1+
name: Upload Binaries
22

33
on:
4-
push:
5-
tags:
6-
- console-subscriber-v[0-9]+.*
7-
- console-api-v[0-9]+.*
8-
- tokio-console-v[0-9]+.*
4+
release:
5+
types: [published]
96

107
jobs:
11-
create-release:
12-
# only publish from the origin repository
13-
if: github.repository_owner == 'tokio-rs'
14-
runs-on: ubuntu-latest
15-
steps:
16-
- uses: actions/checkout@v2
17-
- name: extract tag
18-
id: tag
19-
run:
20-
echo ::set-output name=TAG::$(echo $GITHUB_REF | sed -r 's/.*(console-subscriber|console-api|tokio-console).*/\1/')
21-
- uses: taiki-e/create-gh-release-action@v1
22-
with:
23-
changelog: ${{ steps.tag.outputs.TAG }}/CHANGELOG.md
24-
branch: main
25-
env:
26-
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
27-
288
upload-bins:
29-
# only upload binaries if we're on the origin repository and if the tag is a
30-
# `tokio-console` release
31-
if: ${{ github.repository_owner == 'tokio-rs' && contains(github.ref, 'tokio-console') }}
9+
# only upload binaries if the tag is a`tokio-console` release
10+
if: contains(github.ref, 'tokio-console')
3211
strategy:
3312
matrix:
3413
os: [ubuntu-latest, macos-latest, windows-latest]

0 commit comments

Comments
 (0)