-
Notifications
You must be signed in to change notification settings - Fork 24
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
feature: register releases to chocolatey #158
Comments
On Windows one can already install and update keymapper using Do you have experience with chocolatey package creation? I just had a quick look but did not find out how to get an API key one needs to push to the community feed. |
winget i havent used but i think it will suffice for my needs. Will try it on next release |
wow that was confusing.. found it by
|
Thanks, |
I was thinking you wanted to publish through a github pipeline script Publishing a .msi package for Windows to Chocolatey from a GitHub Action involves several steps. Here’s a detailed guide to achieve this: Prerequisites
Ensure you have the choco CLI tool installed on your local machine for testing. Test your package locally using choco pack and choco install commands.
Explanation Checkout Repository: Uses actions/checkout@v3 to check out the repository code. Set up Chocolatey: Installs Chocolatey on the runner. Pack Chocolatey Package: Packs the .nuspec file into a .nupkg. Push to Chocolatey: Pushes the .nupkg file to the Chocolatey repository using the API key stored in GitHub Secrets. Additional Tips Versioning: Ensure your .nuspec file version matches the tag name to avoid version conflicts. Testing: Before pushing to Chocolatey, thoroughly test your .msi and Chocolatey package locally. Error Handling: Add additional error handling and notifications in the workflow for better feedback. |
Thanks! Unfortunately this guide does not show how to patch the version and checksum inside keymapper.nuspec and chocolateyinstall.ps1 first. |
To patch the version and checksum inside keymapper.nuspec and chocolateyinstall.ps1 files before packaging and pushing the Chocolatey package, you can use a script within your GitHub Actions workflow. This script will dynamically update these files with the correct version and checksum values. Detailed Steps
name: Publish Chocolatey Package on: jobs:
oh btw this is 100% straight chatptg material ;) |
I knew it already after reading the highlighted phrase:
P.S. Before blindly posting GPT answers again, you might want to read this: https://daniel.haxx.se/blog/2024/01/02/the-i-in-llm-stands-for-intelligence/ 😉 |
@ristomatti already read it. currently im testing it out. like it really helped me with some error messages the other day and it can do some python coding - and stupid almost of-the-shelve github actions I would think it would do fairly well among me (us?) who dont know github actions. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
It is now available: https://community.chocolatey.org/packages/keymapper |
on windows chocolatery is a very convenient way to install and update software. similar to package managers on linux.
it would be great to have releases pushed to chocolatery https://docs.chocolatey.org/en-us/create/create-packages/
The text was updated successfully, but these errors were encountered: