(doc) Document updating manual packages #2671

pauby · 2025-05-12T15:56:07Z

Description

document how manual packages are updated and pushed.

It isn't documented and maintainers need to know how to do it.

I did this task this morning and it worked as expected. This is just documenting it.

N/A

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Migrated package (a package has been migrated from another repository)

My pull request is not coming from the master branch.
My code follows the code style of this repository.
My change requires a change to documentation (this usually means the notes in the description of a package).
I have updated the documentation accordingly (this usually means the notes in the description of a package).
I have updated the package description and it is less than 4000 characters.
All files are up to date with the latest Contributing Guidelines
The added/modified package passed install/uninstall in the Chocolatey Test Environment. Note that we don't support the use of any other environment.
The changes only affect a single package (not including meta package).

COMMITTERS.md

pauby force-pushed the doc/push-manual-package branch from 43fcb55 to babc599 Compare May 12, 2025 15:58

corbob reviewed May 13, 2025

View reviewed changes

COMMITTERS.md Outdated Show resolved Hide resolved

pauby force-pushed the doc/push-manual-package branch from babc599 to 260426b Compare May 14, 2025 19:33

(doc) Document updating manual packages

8c3c9f4

pauby force-pushed the doc/push-manual-package branch from 260426b to 8c3c9f4 Compare May 14, 2025 19:34