Downloads of v 0.4.0:


Last Update:

09 Jan 2016

Package Maintainer(s):

Software Author(s):

  • GitTools Contributors


github release notes create export


This is not the latest version of GitReleaseManager available.

0.4.0 | Updated: 09 Jan 2016



Downloads of v 0.4.0:



Software Author(s):

  • GitTools Contributors

GitReleaseManager 0.4.0

This is not the latest version of GitReleaseManager available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install GitReleaseManager, run the following command from the command line or from PowerShell:


To upgrade GitReleaseManager, run the following command from the command line or from PowerShell:


To uninstall GitReleaseManager, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade gitreleasemanager.portable -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade gitreleasemanager.portable -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure gitreleasemanager.portable installed
    name: gitreleasemanager.portable
    state: present
    version: 0.4.0
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'gitreleasemanager.portable' do
  action    :install
  version  '0.4.0'
  source   'STEP 3 URL'

See docs at

    Name: gitreleasemanager.portable,
    Version: 0.4.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller gitreleasemanager.portable
   Name     = 'gitreleasemanager.portable'
   Ensure   = 'Present'
   Version  = '0.4.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'gitreleasemanager.portable':
  provider => 'chocolatey',
  ensure   => '0.4.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install gitreleasemanager.portable version="0.4.0" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 24 Jun 2016.


Tool for creating and exporting releases for software applications hosted on GitHub

Generate-BinFile "grm" "$packageFolder\Tools\GitReleaseManager.exe"
Remove-BinFile "grm" "$packageFolder\Tools\GitReleaseManager.exe"
md5: 13B2F133F2884CC35A6E5A22BA78D3E2 | sha1: C951913610104E6B558AF0E45AB2F68901AA2794

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
GitReleaseManager 0.10.2 119 Wednesday, January 15, 2020 Approved
GitReleaseManager 0.10.0 28 Monday, January 13, 2020 Approved
GitReleaseManager 0.9.0 349 Tuesday, November 19, 2019 Approved
GitReleaseManager 0.8.0 3691 Sunday, December 30, 2018 Approved
GitReleaseManager 0.7.1 3380 Saturday, May 19, 2018 Approved
GitReleaseManager 0.5.0 8408 Sunday, July 10, 2016 Approved
GitReleaseManager 0.4.0 346 Saturday, January 9, 2016 Approved
GitReleaseManager 0.3.0 319 Friday, July 10, 2015 Approved

This package has no dependencies.

Discussion for the GitReleaseManager Package

Ground Rules:

  • This discussion is only about GitReleaseManager and the GitReleaseManager package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or GitReleaseManager, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus