-
Notifications
You must be signed in to change notification settings - Fork 227
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
chore(ci): make sure to only make new releases if tests pass #764
Conversation
Things happened in the correct order here - And release was skipped, but only showed up after the other jobs completed |
This reverts commit 5adaf25.
a failing test made no difference, it only said "skipped" still. Let's trust it works 😛 https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds |
Sorry, I didn't realize we'd switched up CI like that - that explains why it released. I played with the workflow event myself last month and couldn't find a way to have it only run on success |
Switched up? We've been using GH actions since Oct 2019 to make releases. And if you meant changes in #689 you did comment on them 😛 |
I meant #689 - the only comment j made in that PR was just now :) (Unless the mobile UI is bidding previous comments?) Still, no harm no foul 🤷♂️ |
I've also deprecated the broken release |
Cheers - sorry again for the hassle 😓 |
No worries, I'm the one who set up the broken automation 😀 |
Btw while I've got you, would you be good to turn on automatic deleting of head branches? |
🎉 This PR is included in version 24.1.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
https://github.com/jest-community/eslint-plugin-jest/runs/1914618070?check_suite_focus=true made a release even though tests were failing. #689 obviously didn't work, so let's bloat up a single file instead
I also added a
prepare-yarn-cache
job which ensures all other jobs have an updated cache before running