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
Hi,
I'm in the process of proposing a simpler and cross platform approach to enable a lychee pre-commit hook which uses the pre-built binaries. For that to work cross platform, the filenames of the release assets need a fix. linux assets are all consistent but differ from macos and windows assets.
I prepared a PR which renames the windows and mac assets to match the linux pattern. I figured while I'm at it, I could also strip the version from the filenames. This unlocks the possibility to offer a permalink to the latest release, without having to know the version:
Hi,
I'm in the process of proposing a simpler and cross platform approach to enable a lychee pre-commit hook which uses the pre-built binaries. For that to work cross platform, the filenames of the release assets need a fix.
linux
assets are all consistent but differ frommacos
andwindows
assets.I prepared a PR which renames the windows and mac assets to match the linux pattern. I figured while I'm at it, I could also strip the version from the filenames. This unlocks the possibility to offer a permalink to the latest release, without having to know the version:
https://docs.github.com/en/repositories/releasing-projects-on-github/linking-to-releases#linking-to-the-latest-release
This makes it trivial for downstream consumers to automate the download of the latest binary (after weighting the pro's and con's of course 😉).
The text was updated successfully, but these errors were encountered: