chore: address Chocolatey package guidelines#396
Conversation
Chocolatey moderation flagged three guideline items on the first submission. Fix in the GoReleaser chocolatey config: - add package_source_url (packageSourceUrl) so the package source is linked - use a descriptive title instead of one matching the package id exactly projectSourceUrl already points to the software source, so it is kept.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Summary by CodeRabbit
WalkthroughThis pull request updates Chocolatey package metadata in the 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Addresses the Guideline items the Chocolatey automated review flagged on the first
lfksubmission (0.10.4). All are Guidelines (non-blocking), fixed in the GoReleaserchocolateysconfig:packageSourceUrl(package_source_url) — links to where the package source lives, distinct fromprojectSourceUrl.title—"LFK (Lightning Fast Kubernetes navigator)"instead of"lfk", which matched the package id exactly.projectSourceUrlalready points to the software source on GitHub, so it is kept as-is. The maintainer-equals-author item is a Note (no action — I am the software author).Context
The moderator offered to reject the queued 0.10.4 so a version matching the current software (0.14.1) can be pushed. These config fixes apply to that resubmission.
Test plan
goreleaser checkvalidates the config