

-
One other recommendation, seeing as the package manifest repo on github seems to use json files, it could be useful to cooperate with the Bucket maintainers for scoop (lukesampson and Ash258 are the most active in that front, at least). They already have rather large repos, and some good tooling for tracking (and in some cases verifying them):
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
The current release is called 1.0.0, which normally is used for stable release (Semantic versioning). You may consider changing this to avoid confusions.
-
That's a great suggestion. I have created an issue for this here and will definitely try to implement this as soon as I can in the next release.
-
Just an FYI, the lessmsi project may be worth a look for those trickier installers; its been fairly reliable in my experience! It can be used to extract the msi like you would a zip
-
-
At least if the manifest format were standardized, it could help reduce work for making new "repos". Since Scoop uses the The Unlicense, there shouldn't be issues collaborating code-wise.