You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The v1.2.0 release doesn't contain pre-built binaries b/c markdown link check failed here and that's a prerequisite for version bump (which is a prerequisite for goreleaser)
Proposal
Remove markdown-linter as a prerequisite from version bump
Note: we can only re-run the CI workflow on v1.2.0 without modifications and I don't expect that to succeed so we'd have to do something hacky to get pre-built binaries attached to v1.2.0. We can fix this so we don't hit it on subsequent releases.
The text was updated successfully, but these errors were encountered:
Part of #2749
The markdown-linter job contains markdown-link-check which is super
flakey. If it fails on a release then the pre-built binaries won't be
generated and attached to the release.
Part of #2749
Note: we've discussed avoiding backporting docs changes so we can close
this PR if we're okay with markdown link check failing on the v1.x
branch from now on.
## Testing
On the v1.x branch, locally `make markdown-link-check` passes
Problem
The v1.2.0 release doesn't contain pre-built binaries b/c markdown link check failed here and that's a prerequisite for version bump (which is a prerequisite for goreleaser)
Proposal
markdown-linter
as a prerequisite from version bumpcelestia-app/.github/workflows/ci-release.yml
Lines 52 to 53 in c0743df
Note: we can only re-run the CI workflow on v1.2.0 without modifications and I don't expect that to succeed so we'd have to do something hacky to get pre-built binaries attached to v1.2.0. We can fix this so we don't hit it on subsequent releases.
The text was updated successfully, but these errors were encountered: