-
Notifications
You must be signed in to change notification settings - Fork 117
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
Configuration file reading is broken in 3.11.0 #246
Comments
I think this is caused by updating markdown-link-check/markdown-link-check Lines 94 to 98 in 114b966
|
Can only confirm that it's broken and fails silently. cc @tcort if you haven't seen the issue yet ❤️ |
Link check is broken due to tcort/markdown-link-check#246, pinning previous version until it's fixed
Can confirm |
Confirming that |
…cker (#218) * Add missing Slack scope for audit reporting * Use older markdown link checker See tcort/markdown-link-check#246
I can also confirm the issue. Both running via mega-linter, or using the markdown-link-check directly, do not use the igorePatterns as specified in the .markdown-link-check.json. This also does not work when explicitly providing the config file location via the -c option. This currently break my build, so I will try to use a previous image that does not contain the bug. |
In response to user feedback, I downgraded markdown-link-check to v3.10.3 in MegaLinter v6.22.0. We will unpin markdown-link-check once a fix to this issue is released. |
should be fixed in 3.11.1. If not, please re-open. |
No specified config file now returns an error in 3.11.1
|
I am getting this error on the latest version. MacOS install with pnpm. |
Link check is broken due to tcort/markdown-link-check#246, pinning previous version until it's fixed
Link check is broken due to tcort/markdown-link-check#246, pinning previous version until it's fixed
After updating to V3.11.0, the
-c
or--config
option no longer works. It is just ignored, and hence any configuration options (like links to ignore) are uneffective.The tool doesn't even attempt to read the config file. Running
does not produce an error about a missing json file (but only because there's a broken link in that file in my case).
Reverting back to V3.10.3 fixes this.
The text was updated successfully, but these errors were encountered: