This file provides additional information for maintainers and contributors.
Nothing special or automated yet. For the time being, try at least:
- Build the nupkg package, install it and watch out for errors and warnings:
cd ./chocolatey-sendkeys.extension choco pack choco install sendkeys.extension --source='.\' --force RefreshEnv
- Import the PowerShell module directly, do some function calls and watch out for errors. See the
README.md
"Usage" section for details.
- Do proper Testing. Continue only if everything is fine.
- Determine the next version number. This project adheres to Semantic Versioning. Unlike other Chocolatey packages, there is no underlying software's version to match.
- Update the
CHANGELOG.md
. Insert a section for the new release. Do not forget the comparison link at the end of the file. - If everything is fine: commit the changes, tag the release and push:
If something minor went wrong (like missing
git tag v<version> <commit> -m "version <version>" git show v<version> git push origin main --follow-tags
CHANGELOG.md
update), delete the tag and start over:This is only possible if the package was not already pushed to the community package feed. Use a new patch version number otherwise.git tag -d v<version> # delete the old tag locally git push origin :refs/tags/v<version> # delete the old tag remotely
- Pack the
.nupkg
and push it to the community package feed:choco pack choco apikey add -s "https://push.chocolatey.org/" -k="..." choco push sendkeys.extension.<version>.nupkg --source "https://push.chocolatey.org/"
- Generally: Use UTF-8 encoding with
LF
(Line Feed\n
) line endings. - All
*.ps1
,psm1
and*.nuspec
files: Please follow Chocolatey's character encoding rules. Add a Byte Order Mark (BOM) and useCRLF
(Carriage Return\r
and Line Feed\n
) line endings as Chocolatey's general context is Microsoft Windows, Powershell and .NET.