Links to directories from Markdown local files are reported as 404 even when they exist

pi@pi:~/lnb $ node --version
v14.15.3
pi@pi:~/lnb $ npm ls --depth 0
/home/pi/lnb
└── linkinator@2.8.2
pi@pi:~/lnb $ cat issue.md 
[Link to file](test/file.md)
[Link to directory, works fine in GitHub README](test)
[Alternate link to directory, just curious](test/)
pi@pi:~/lnb $ ./node_modules/.bin/linkinator issue.md --markdown
🏊‍♂️ crawling issue.md
[200] http://localhost:5920/issue.md
[200] http://localhost:5920/test/file.md
[404] http://localhost:5920/test/
[404] http://localhost:5920/test



  [200] http://localhost:5920/issue.md
http://localhost:5920/issue.md
  [200] http://localhost:5920/test/file.md
  [404] http://localhost:5920/test/
  [404] http://localhost:5920/test
ERROR: Detected 2 broken links. Scanned 4 links in 0.269 seconds.
pi@pi:~/lnb $ 

[DavidAnson]

This is workaround-able, so not blocking. However, Markdown link destinations are explicitly allowed to be relative (this isn’t specific to GitHub):

• https://daringfireball.net/projects/markdown/syntax#link
• https://spec.commonmark.org/0.29/#example-481

I’m using the --markdown parameter, so there seems not to be ambiguity about the scenario. But I’m fine if you close this as being out of scope for the tool.

[github-actions[bot]]

🎉 This issue has been resolved in version 2.12.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀