feat: download purely using octokit

[klaernie]

In my understanding octokit automatically uses authentication, but the
real download was done using fetch directly, hence without
authentication.

This approach now uses octokit's getReleaseAsset() to download the
asset, which should use proper authentication, hence allowing
potentially higher rate limits.

Closes: #419

[klaernie]

@vbode: I understand from #425 that you have an environment frequently affected by rate limiting from GitHub - could you please test if this branch works better?

[theoludwig]

nitpick (not blocking at all), but just saying, we should use the convention of the language for naming variables and in JavaScript it's camelCase.

[klaernie]

good point. I probably chose that name from the GitHub API call parameter where assetId is ultimately being used. Ideally I'd have passed the entire asset but I'm currently not clever enough for understanding how to either define or find out the proper typescript type for that..

[vbode]

@klaernie I can gladly test this branch, but am having some difficulty installing the branch with NPM. I've never had to do this before, but from Stackoverflow I found that I should be able to use:

npm install "https://github.com/editorconfig-checker/editorconfig-checker.git#octokit-down
load" --save

But this does not seem to work:
vincentb@WS-HST8PG3:/mnt/c/Repositories/build/test$ npm install "https://github.com/editorconfig-checker/editorconfig-checker.git#octokit-down load" --save npm error code 1 npm error The git reference could not be found npm error command git --no-replace-objects checkout octokit-download npm error error: pathspec 'octokit-download' did not match any file(s) known to git npm error A complete log of this run can be found in: /home/vincentb/.npm/_logs/2025-06-30T05_33_20_198Z-debug-0.log

[theoludwig]

Well, we can release a beta if needed. First we need to update betawith master at least, and then merge this branch in the beta branch, then it will automatically release a new beta version on npm to try. If everything is good, then we can merge back beta in main and it will release it as stable.

@klaernie

[theoludwig]

I would say, we can even directly release this as stable. CI is green, and everything seems to work fine. We can always revert it, if really needed.

[github-actions]

🎉 This PR is included in version 6.1.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀