Downloads:
2,308
Downloads of v 1.0.11:
6
Last Update:
06 Mar 2024
Published Date:
06 Mar 2024
Package Maintainer(s):
Software Author(s):
- Stef Heyenrath
Tags:
githubreleasenotes release releasenotes notes github generate octokit libgit2sharp markdown project- Software Specific:
- Software Site
- Software Source
- Software License
- Software Issues
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
GitHubReleaseNotes
(Waiting for Maintainer to take corrective action)
- 1
- 2
- 3
1.0.11 | Updated: 06 Mar 2024
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Issues
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
2,308
Downloads of v 1.0.11:
6
Published:
06 Mar 2024
Maintainer(s):
Software Author(s):
- Stef Heyenrath
GitHubReleaseNotes 1.0.11
(Waiting for Maintainer to take corrective action)
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.
- Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
- This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
- You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
- There are also no guarantees that it will be approved.
There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.
Generate Release Notes from a GitHub project.
Remove-BinFile "ghrn" "$packageFolder\Tools\GitHubReleaseNotes.exe"
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.
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.11.0
- Product name GitHubReleaseNotes
- Product version 1.0.11.0
- Copyright Stef Heyenrath
- Size 66,2 MB
- Date modified 2024-03-06 11:56
- Language Language Neutral
- Original filename GitHubReleaseNotes.exe
2] Verify the SHA256 from the GitHubReleaseNotes.exe file (7zip can be used for this)
- SHA256 A3E7148CFAAC7ADAEDBDAE3A2EC345038EE3B3B5DF1177B08E8D52BFC30B7447
3] For the changes in this release, see ReleaseNotes.md
Note that this application is build as a selfcontained .NET 8 executable.
# 1.0.10.1 (21 February 2024)
- [#29](https://github.com/StefH/GitHubReleaseNotes/pull/29) - Replace LibGit2Sharp by GitReader [feature] contributed by [StefH](https://github.com/StefH)
# 1.0.10.0 (15 February 2024)
- [#28](https://github.com/StefH/GitHubReleaseNotes/pull/28) - Convert GitHubReleaseNotes to a .NET 8 self contained executable [feature] contributed by [StefH](https://github.com/StefH)
# 1.0.9.0 (01 February 2024)
- [#27](https://github.com/StefH/GitHubReleaseNotes/pull/27) - Update method GetAllIssuesAndPullRequestsAsync [feature] contributed by [StefH](https://github.com/StefH)
# 1.0.8.0 (25 March 2023)
- [#26](https://github.com/StefH/GitHubReleaseNotes/pull/26) - Upgrade to .NET 6 [feature] contributed by [StefH](https://github.com/StefH)
# 1.0.7.1 (23 June 2021)
- [#20](https://github.com/StefH/GitHubReleaseNotes/pull/20) - Fix version from setup.exe [bug] contributed by [StefH](https://github.com/StefH)
- [#21](https://github.com/StefH/GitHubReleaseNotes/pull/21) - Replace LibGit2Sharp.Portable with latest LibGit2Sharp [bug] contributed by [StefH](https://github.com/StefH)
- [#22](https://github.com/StefH/GitHubReleaseNotes/pull/22) - Update generator for winpkg manifest [bug] contributed by [StefH](https://github.com/StefH)
- [#23](https://github.com/StefH/GitHubReleaseNotes/pull/23) - Fix ManifestVersion [bug] contributed by [StefH](https://github.com/StefH)
- [#18](https://github.com/StefH/GitHubReleaseNotes/issues/18) - Wrong Display Version in Windows [bug]
- [#19](https://github.com/StefH/GitHubReleaseNotes/issues/19) - LibGit2Sharp.Portable is deprecated and has issues running on Linux. [bug]
# 1.0.7 (20 February 2021)
- [#17](https://github.com/StefH/GitHubReleaseNotes/pull/17) - Fix issue where ssh remote urls don't work [bug] contributed by [jpann](https://github.com/jpann)
- [#16](https://github.com/StefH/GitHubReleaseNotes/issues/16) - String cannot be empty [bug]
# 1.0.6 (15 November 2020)
- [#14](https://github.com/StefH/GitHubReleaseNotes/pull/14) - Support tag prefix and create dotnet tool contributed by [StefH](https://github.com/StefH)
- [#15](https://github.com/StefH/GitHubReleaseNotes/pull/15) - Add WinGet project contributed by [StefH](https://github.com/StefH)
# 1.0.5.3 (27 March 2020)
- [#13](https://github.com/StefH/GitHubReleaseNotes/pull/13) - Fixed: "System.InvalidOperationException: Sequence contains no matching element" [bug] contributed by [StefH](https://github.com/StefH)
- [#12](https://github.com/StefH/GitHubReleaseNotes/issues/12) - System.InvalidOperationException: Sequence contains no matching element [bug]
# 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)
- [#8](https://github.com/StefH/GitHubReleaseNotes/pull/8) - Add token and login+password authentication [feature] contributed by [StefH](https://github.com/StefH)
- [#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)
md5: FF838E9D3637D5B21BAC443264D3E1D5 | sha1: 1652F08AF663F0884B3A7AA2B775EE2485D734BB | sha256: 5D812B11CED555394445CC93FB1D7AF262BA292017CA6EC1F3AD2DC5F0854BB6 | sha512: 192197E3F5D0014FEEEE38C12131898233B5E120DF0B00EDBAC0EAC91602C729C78D19F5017599ECD0568CDD354452C5FA536B37912296354308A1015948B3E0
Log in or click on link to see number of positives.
- githubreleasenotes.1.0.11.nupkg (f796e683798a) - ## / 65
- GitHubReleaseNotes.exe (5d812b11ced5) - ## / 71
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.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
GitHubReleaseNotes 1.0.11 | 6 | Wednesday, March 6, 2024 |
Waiting for Maintainer
|
|
GitHubReleaseNotes 1.0.9 | 29 | Thursday, February 1, 2024 | Approved | |
GitHubReleaseNotes 1.0.8.0 | 131 | Saturday, March 25, 2023 | Approved | |
GitHubReleaseNotes 1.0.7.1 | 190 | Wednesday, June 23, 2021 | Approved | |
GitHubReleaseNotes 1.0.7 | 161 | Saturday, February 20, 2021 | Approved | |
GitHubReleaseNotes 1.0.6 | 145 | Sunday, November 15, 2020 | Approved | |
GitHubReleaseNotes 1.0.5.3 | 271 | Friday, March 27, 2020 | Approved | |
GitHubReleaseNotes 1.0.5.2 | 221 | Wednesday, December 25, 2019 | Approved | |
GitHubReleaseNotes 1.0.4.0 | 256 | Monday, January 21, 2019 | Approved | |
GitHubReleaseNotes 1.0.3.0 | 232 | Sunday, November 18, 2018 | Approved | |
GitHubReleaseNotes 1.0.2.0 | 193 | Sunday, November 18, 2018 | Approved | |
GitHubReleaseNotes 1.0.1.0 | 214 | Monday, October 29, 2018 | Approved | |
GitHubReleaseNotes 1.0.0.0 | 201 | Monday, October 29, 2018 | Approved |
2018 - 2024 Stef Heyenrath
See ReleaseNotes.md
This package has no dependencies.
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.
stef (maintainer) on 06 Mar 2024 10:57:10 +00:00:
User 'stef' (maintainer) submitted package.
chocolatey-ops (reviewer) on 06 Mar 2024 11:28:38 +00:00:
githubreleasenotes has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 06 Mar 2024 12:31:33 +00:00:
githubreleasenotes has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/05e854efe9307ae02c1c7eaabe585f54 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 06 Mar 2024 12:47:28 +00:00:
githubreleasenotes has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.
chocolatey-ops (reviewer) on 22 Apr 2024 13:25:23 +00:00:
We've found githubreleasenotes v1.0.11 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.