-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
[error]failed to parse title: invalid semver #16
Comments
"technically" this is correct behavior... GitHub Actions uses the an action could point to ignoring for a second that this action is triggered on a pull request to update the action itself ... because it's getting too meta! in this auto-merge action, I could squint my eyes and see a possibility of attempting to "fix" the version ( but first I wanted to explain the workflow and show that's working as expected here without causing failures |
Oh I see. It's a bit tricky because the "unexpected error" is being used as a form of "safe failure". Ideal would be a warning instead "##[warning] Incompatible semver versions. Can't compare, so needs human eyes" :) This notation of I'll leave it to you to "squint your eyes". But for now, I'll just merge mine :) |
|
as for your merging that PR, you can also just set it to unless you want those ... |
I am so sorry for being a pain but... I could understand how it could error on
As seen here: https://github.com/mdn/yari/pull/1243/checks?check_run_id=1100241207 So meta! It's a PR to upgrade your/this action from 2.0.1 to 2.0.4. |
so very meta!
upgrade to latest ( |
Still a bug in 2.0.4.
It failed to upgrade from |
mdn/yari#1231 failed because of this error:
https://github.com/mdn/yari/pull/1231/checks?check_run_id=1094792761
Workflow here
The text was updated successfully, but these errors were encountered: