(maintainertoolkit) Adds new maintainertoolkit package by steviecoaster · Pull Request #2778 · chocolatey-community/chocolatey-packages

steviecoaster · 2026-03-10T19:04:12Z

Description

maintainertoolkit is a metapackage to provide a set of development tools to aid in the creation and ongoing maintenance of Chocolatey packages. Primarily for the Chocolatey Community Repository, this package can also provide value to organizations looking to author and maintain packages internally.

Motivation and Context

Fixes #2777

How Has this Been Tested?

Developed and tested in a Windows Sandbox VM

Screenshot (if appropriate, usually isn't needed):

Types of changes

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)

Checklist:

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).

AdmiringWorm

I few things to update, and from the look of the description, you haven't ensured that the description is below 4 000 characters (I haven't checked either), that the package is up to date with our Contribution Guidelines, nor that the package works as expected in the Chocolatey Test Environment.

Those three are required to have been done before merging in a PR.

AdmiringWorm · 2026-03-11T11:40:44Z

manual/maintainertoolkit/tools/chocolateyInstall.ps1

+        Description = 'Framework for keeping packages automatically up to date. Most community packages use this.'
+    }
+    [PSCustomObject]@{
+        Name        = 'JSONPath/Fiddler / Browser DevTools'


Is there meant to be a space between the JSONPath and Fiddler and the slash?

Similar to what you have between Fiddler and Browser

I think simplifying to just 'Fiddler' makes sense here!

AdmiringWorm · 2026-03-11T11:42:28Z

manual/maintainertoolkit/maintainertoolkit.nuspec

+    <id>maintainertoolkit</id>
+    <version>1.0.0</version>
+    <packageSourceUrl>https://github.com/chocolatey-community/chocolatey-packages/blob/master/manual/maintainertoolkit/</packageSourceUrl>
+    <owners>chocolatey-community</owners>


It is preferable to have at least one more user specified in the nuspec file, other than the chocolatey-community user.

Suggested change

<owners>chocolatey-community</owners>

<owners>chocolatey-community,steviecoaster</owners>

AdmiringWorm · 2026-03-11T11:43:40Z

manual/maintainertoolkit/maintainertoolkit.nuspec

+    <packageSourceUrl>https://github.com/chocolatey-community/chocolatey-packages/blob/master/manual/maintainertoolkit/</packageSourceUrl>
+    <owners>chocolatey-community</owners>
+    <title>Chocolatey Package Maintenance Toolkit</title>
+    <authors>Chocolatey</authors>


Should this maybe be:

Suggested change

<authors>Chocolatey</authors>

<authors>Chocolatey Software</authors>

Normally, i would suggest Chocolatey Software, Inc, but since it isn't handled correctly on CCR, I think teh above is a better value.

AdmiringWorm · 2026-03-11T11:45:28Z

manual/maintainertoolkit/maintainertoolkit.nuspec

+    <licenseUrl>https://github.com/chocolatey-community/chocolatey-packages/blob/master/manual/maintainertoolkit/LICENSE.md</licenseUrl>
+    <mailingListUrl>https://ch0.co/community</mailingListUrl>
+    <bugTrackerUrl>https://github.com/chocolatey-community/chocolatey-packages/issues</bugTrackerUrl>
+    <tags>maintainertoolkit packaging developer</tags>


The tags doesn't match the obligitary tags in this repository, can you please have a look at the contribution guidelines, and make the appropriate changes to this?

https://github.com/chocolatey-community/chocolatey-packages/blob/master/CONTRIBUTING.md#obligatory-tags-and-categories

AdmiringWorm · 2026-03-11T11:47:32Z

manual/maintainertoolkit/ReadMe.md

I don't mind including this file, but just want to note that it won't be used anywhere in our systems. A ReadMe is only imported to the nuspec file when running the package creation/updating through AU.

This commit addresses chocolatey-community#2777 and adds a new manual package called maintainertoolkit, a metapackage to provide a set of development tools to aid in the creation and ongoing maintenance of Chocolatey packages. Primarily for the Chocolatey Community Repository, this package can also provide value to organizations looking to author and maintain packages internally.

- Fixes tags in nuspec - Fixes Author in nuspec - Fixes git dependency version number - Adds second maintainer name - Clarifies output in install script

steviecoaster · 2026-03-12T15:40:01Z

@AdmiringWorm, this works in the chocolatey-test-environment, but only if the VSCode package installs first. The vscode-powershell package doesn't include a dependency path that ensures vscode is installed, so it can fail to install the package.

Re-running the install is successful, since at that point the VS Code package was installed; the VS Code-Powershell package is fine. Unsure how to handle this in this package, since we can't guarantee the dependency order. I could just remove the vscode-powershell package, but I don't really want to.

corbob · 2026-03-12T15:46:08Z

@AdmiringWorm, this works in the chocolatey-test-environment, but only if the VSCode package installs first. The vscode-powershell package doesn't include a dependency path that ensures vscode is installed, so it can fail to install the package.

Re-running the install is successful, since at that point the VS Code package was installed; the VS Code-Powershell package is fine. Unsure how to handle this in this package, since we can't guarantee the dependency order. I could just remove the vscode-powershell package, but I don't really want to.

You could just issue the code command to install the extension in a chocolateyinstall.ps1...

The vscode-powershell package doesn't take a dependency because it could be user or system install and stable or insiders.

steviecoaster self-assigned this Mar 10, 2026

steviecoaster requested review from AdmiringWorm and corbob March 10, 2026 19:09

steviecoaster force-pushed the gh2777 branch from a30e27f to 6b748e5 Compare March 10, 2026 19:12

AdmiringWorm requested changes Mar 11, 2026

View reviewed changes

steviecoaster force-pushed the gh2777 branch from 6b748e5 to 49abd84 Compare March 12, 2026 14:53

((maintainertoolkit) changes from PR review

f2a5527

- Fixes tags in nuspec - Fixes Author in nuspec - Fixes git dependency version number - Adds second maintainer name - Clarifies output in install script

steviecoaster force-pushed the gh2777 branch from d3a4241 to f2a5527 Compare March 12, 2026 15:36

steviecoaster marked this pull request as ready for review March 12, 2026 15:37

steviecoaster requested a review from AdmiringWorm March 12, 2026 15:37

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

(maintainertoolkit) Adds new maintainertoolkit package#2778

(maintainertoolkit) Adds new maintainertoolkit package#2778
steviecoaster wants to merge 2 commits intochocolatey-community:masterfrom
steviecoaster:gh2777

steviecoaster commented Mar 10, 2026 •

edited

Loading

Uh oh!

AdmiringWorm left a comment

Uh oh!

AdmiringWorm Mar 11, 2026

Uh oh!

steviecoaster Mar 12, 2026

Uh oh!

AdmiringWorm Mar 11, 2026

Uh oh!

AdmiringWorm Mar 11, 2026

Uh oh!

AdmiringWorm Mar 11, 2026

Uh oh!

AdmiringWorm Mar 11, 2026

Uh oh!

steviecoaster commented Mar 12, 2026

Uh oh!

corbob commented Mar 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	<owners>chocolatey-community</owners>
	<owners>chocolatey-community,steviecoaster</owners>

	<authors>Chocolatey</authors>
	<authors>Chocolatey Software</authors>

Conversation

steviecoaster commented Mar 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Motivation and Context

How Has this Been Tested?

Screenshot (if appropriate, usually isn't needed):

Types of changes

Checklist:

Uh oh!

AdmiringWorm left a comment

Choose a reason for hiding this comment

Uh oh!

AdmiringWorm Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

steviecoaster Mar 12, 2026

Choose a reason for hiding this comment

Uh oh!

AdmiringWorm Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

AdmiringWorm Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

AdmiringWorm Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

AdmiringWorm Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

steviecoaster commented Mar 12, 2026

Uh oh!

corbob commented Mar 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

steviecoaster commented Mar 10, 2026 •

edited

Loading