-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Fix the tests to allow publication of a hotfix release #87
Comments
I've added Edit: still failing:
Most of them are failing with this. Edit: I deleted the |
I will skip the tests and only run the orb publishing for now. Can't be worst than a not working at all solution anyway 🤷 |
Closing this issue as I created a branch, commented out the tests and related jobs only to keep the Full Changelog: v1.7.0...v1.7.1 Closing this issue. It's not really fixed, but the main idea was to publish a hotfix, which worked 👍 |
As I suspected, the release needs to have the tests passing (which is a good thing). But the orb's secret aren't in sync anymore with what's being tested (due to work in progress to get activation support properly working with #83).
I created a release mainly to publish the changes from #82 and unblock some workflows using this action, but it can't be done until the complete workflow passes. Only then the orb publication will work:
I will see what I can do with the secrets. I think having a combination of older env vars and the new env var should get a few jobs passing.
The text was updated successfully, but these errors were encountered: