Closed antedeguemon closed 1 month ago
I think we should use a specific exit code for outdated certs. We use exceptions to stop the task in case of some error and they always set the exit code to 1. So as long as we use a different than 0 or 1 and check for that exit code specifically in outdated.sh
we should be good.
@antedeguemon Would you be interested in sending a PR with a fix?
@ericmj I sure am! I will try to push a fix this week. ๐
@antedeguemon ping ๐
@whatyouhide oops, my apologies for the delay - life got a bit more busy these past months.
We can close this issue since @vshev4enko already handled it in https://github.com/elixir-mint/castore/pull/71. Thank you all! ๐ซถ
Hey folks!
As noted by @cgrothaus in https://github.com/elixir-mint/castore/pull/67#issuecomment-2068543434, the
Outdated
CI pipeline mistakenly bumps the library version and creates a new release whenever the curl command fails: https://github.com/elixir-mint/castore/actions/runs/8761722399/job/24048599140This happens because the exit code of
mix certdata --check-outdated
is the same when there are outdated certificates and when some failure occurs with fetching the certificates.