GitHubReleaseNotes

1.0.5.3 | Updated: 27 Mar 2020

Downloads:

652

Downloads of v 1.0.5.3:

99

Maintainer(s):

Software Author(s):

  • Stef Heyenrath

GitHubReleaseNotes 1.0.5.3

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

To uninstall GitHubReleaseNotes, 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 https://chocolatey.org/api/v2. 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 https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade githubreleasenotes -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 githubreleasenotes -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure githubreleasenotes installed
  win_chocolatey:
    name: githubreleasenotes
    state: present
    version: 1.0.5.3
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

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


chocolatey_package 'githubreleasenotes' do
  action    :install
  version  '1.0.5.3'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: githubreleasenotes,
    Version: 1.0.5.3,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller githubreleasenotes
{
   Name     = 'githubreleasenotes'
   Ensure   = 'Present'
   Version  = '1.0.5.3'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'githubreleasenotes':
  provider => 'chocolatey',
  ensure   => '1.0.5.3',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install githubreleasenotes version="1.0.5.3" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 27 Mar 2020.

Description

Generate Release Notes from a GitHub project.


tools\chocolateyinstall.ps1
Generate-BinFile "ghrn" "$packageFolder\Tools\GitHubReleaseNotes.exe"
tools\chocolateyuninstall.ps1
Remove-BinFile "ghrn" "$packageFolder\Tools\GitHubReleaseNotes.exe"
tools\GitHubReleaseNotes.exe
md5: BE4447A2C49D28D15DCFC9BF2A58604C | sha1: 416873AF1BFADE17F218F8A3C6AA53CC12BAB68A | sha256: FB9A4CE55FB78FF45C8E96BA6EE7EA6472E4F163A031193CA05E56FF0D6EA4D7 | sha512: 7DE1A521B6B6E917C51B75468FC248870CB9E589A6D432C3EEBE8DD2F5D40866287125FA44E891962082D090C0FCF1A601E3541D47D2F1CFE111DAC805AE7711
tools\LICENSE.txt
From: https://raw.githubusercontent.com/StefH/GitHubReleaseNotes/master/LICENSE

LICENSE

MIT License

Copyright (c) 2018-2020 Stef Heyenrath

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
tools\ReleaseNotes.md
# 1.0.5.2 (25 December 2019)
- [#11](https://github.com/StefH/GitHubReleaseNotes/pull/11) - Fix file load exception [bug] contributed by [StefH](https://github.com/StefH)

# 1.0.5.0 (25 December 2019)
- [#9](https://github.com/StefH/GitHubReleaseNotes/pull/9) - Exclude tags [feature] contributed by [StefH](https://github.com/StefH)
- [#10](https://github.com/StefH/GitHubReleaseNotes/pull/10) - Fix for `-` in project name. [bug] contributed by [StefH](https://github.com/StefH)

# 1.0.4.0 (21 January 2019)
- [#8](https://github.com/StefH/GitHubReleaseNotes/pull/8) - Add token and login+password authentication [feature] contributed by [StefH](https://github.com/StefH)

# 1.0.3.0 (18 November 2018)
- [#7](https://github.com/StefH/GitHubReleaseNotes/pull/7) - Add Labels and command-line option to provide your own template [feature] contributed by [StefH](https://github.com/StefH)
- [#6](https://github.com/StefH/GitHubReleaseNotes/issues/6) - Group issues by label

# 1.0.2.0 (30 October 2018)
- [#5](https://github.com/StefH/GitHubReleaseNotes/pull/5) - Added additional commandline options --version, --language and --skip-empty-releases contributed by [StefH](https://github.com/StefH)
- [#2](https://github.com/StefH/GitHubReleaseNotes/issues/2) - Release notes seems to leave the last merged PR out of the version

# 1.0.1.0 (29 October 2018)
- [#1](https://github.com/StefH/GitHubReleaseNotes/pull/1) - Chocolatey contributed by [StefH](https://github.com/StefH)
- [#3](https://github.com/StefH/GitHubReleaseNotes/pull/3) - Chocolatey contributed by [StefH](https://github.com/StefH)
- [#4](https://github.com/StefH/GitHubReleaseNotes/pull/4) - Fix for Release Notes seems to leave the last merged PR out of the version contributed by [StefH](https://github.com/StefH)

tools\VERIFICATION.txt
VERIFICATION

To verify this package, follow these steps:

1] Right click the GitHubReleaseNotes.exe in Windows file explorer and go to the "Details" tab and check the following properties:
   - File description   GitHubReleaseNotes
   - Type               Application
   - File version       1.0.5.3
   - Product name       GitHubReleaseNotes
   - Product version    1.0.5.3
   - Copyright          Stef Heyenrath
   - Size               0.98 MB
   - Date modified      2020-03-27 10:10
   - Language           Language Neutral
   - Original filename  GitHubReleaseNotes.exe

2] Verify the SHA256 from the GitHubReleaseNotes.exe file (7zip can be used for this)
   - SHA256             FB9A4CE55FB78FF45C8E96BA6EE7EA6472E4F163A031193CA05E56FF0D6EA4D7

3] For the changes in this release, see ReleaseNotes.md

Note that this application is build with the .NET 4.5.2 framework and uses Fody and Fody.Costura to include all dependencies to generate a single exe file.

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
GitHubReleaseNotes 1.0.5.2 96 Wednesday, December 25, 2019 Approved
GitHubReleaseNotes 1.0.4.0 137 Monday, January 21, 2019 Approved
GitHubReleaseNotes 1.0.3.0 94 Sunday, November 18, 2018 Approved
GitHubReleaseNotes 1.0.2.0 54 Sunday, November 18, 2018 Approved
GitHubReleaseNotes 1.0.1.0 79 Monday, October 29, 2018 Approved
GitHubReleaseNotes 1.0.0.0 78 Monday, October 29, 2018 Approved

See ReleaseNotes.md


This package has no dependencies.

Discussion for the GitHubReleaseNotes Package

Ground Rules:

  • This discussion is only about GitHubReleaseNotes and the GitHubReleaseNotes 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 GitHubReleaseNotes, 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