velero-io/velero

Publish releases to winget-pkgs

Open

#9,093 opened on Jul 17, 2025

View on GitHub
 (8 comments) (5 reactions) (2 assignees)Go (1,550 forks)auto 404
Area/WindowsSupportGood first issue

Repository metrics

Stars
 (10,111 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the problem/challenge you have

Currently I need to use chocolatey to install the velero cli on windows if I don't want to take manual steps. For all other tools (kubectl, fluxcd, helm) I can use winget to install and keep it up to date.

Describe the solution you'd like

Publishing releases to the community winget repo, would allow people to reduce there dependencies by only relying on winget and not third-party package managers on windows.

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

  • :+1: for "The project would be better with this feature added"
  • :-1: for "This feature will not enhance the project in a meaningful way"

Contributor guide

Research direction
Explore how to add winget pkgs publishing to the release workflow. Look at existing similar projects that publish to winget, such as fluxcd or helm, and replicate their approach.
Tech stack
go
Domain
devopsrelease
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70