-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
publish libs to crates.io
on release tags
#1142
publish libs to crates.io
on release tags
#1142
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another option is to run it on every new tag https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#running-your-workflow-only-when-a-push-of-specific-tags-occurs
name: GitHub Release
on:
push:
tags:
- "v*.*.*"
851381e
to
0905feb
Compare
crates.io
on manual triggercrates.io
on release
0905feb
to
23e8897
Compare
crates.io
on releasecrates.io
on release tags
462714d
to
13abac4
Compare
during the review of #1143, @jbesraa asked:
on the header of stratum/.github/workflows/release-libs.yaml Lines 1 to 9 in 7665958
I believe those notes were originally written by @Fi3 . The part that really gets my attention is:
@Fi3 have you ever seen this happen in practice? Or did you read this information somewhere? Anyways, if that is the case, I think that we should also have a |
a1b1167
to
c7916d0
Compare
c7916d0
to
dd78c29
Compare
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 1 ALERT: Threshold Boundary Limit exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 2 ALERTS: Threshold Boundary Limits exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 2 ALERTS: Threshold Boundary Limits exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
currently,
release-libs.yaml
will publish the libs tocrates.io
every time we merge tomain
, which is the main event for releaseswith the new conventions proposed in #1124, we want to avoid that, since not every merge to
main
will be a releasethis PR makes
release-libs.yaml
only be able to run: