Downloads:
23,826
Downloads of v 0.7.0:
252
Last Update:
26 Feb 2018
Package Maintainer(s):
Software Author(s):
- GitTools Contributors
Tags:
github release notes create export- Software Specific:
- Software Site
- Software License
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
GitReleaseManager
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
23,826
Downloads of v 0.7.0:
252
Software Author(s):
- GitTools Contributors
GitReleaseManager
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
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 rejected on 21 Dec 2018. The reviewer chocolatey-ops has listed the following reason(s):
Tool for creating and exporting releases for software applications hosted on GitHub
md5: 7768C955885D7035249112CB38240A42 | sha1: E122FBAFBF85289D1E5891B1C6CF61880774A7FC | sha256: 47C19BC706C33767BC2B64E11A9167E89C840BA41EDEA96C3EE5F1A72020BA15 | sha512: CA27E1EB887DAF635748419205DA309170095C845BB502B8D8C22AB7542653244D3FCCEC9399BD54EA7ADEE0CAAA6351AADEE07BDA7856BE89A88F519AD8841B
md5: 0BA2B27A78553CC3093FD10123393912 | sha1: 911BC31DDEE3CD447006027A8FD9B8A3D750A034 | sha256: DF77415271220071D682D39916DAA6E8F2E4C7EDB3788CEF5A0E98EB0BA7CD7C | sha512: 1283CE8B63EC692159D6754858A1DA5A8D07BD343060ECCE7241F27B525641290386D1A4A4076888032AA2019EE7BBCF583826A4C8BAE763BFA6561A4A838AED
md5: FF6A2AEB005200F5CFB009ACD664552E | sha1: 088E3470CBD8F1328066EEA9FFB748BE1ADD4BE2 | sha256: FCDEB50218D20AB505134331F111B5CCD3951562FCF44D0B383D8D2317A92549 | sha512: 2D68F156393DDD67FA398BDD01A9769371B6F2D208E2413C4A1FD082F07016022F3B1CCA993C387092E6DA69A470401103354633294B85859780A97B7A449E3A
md5: 364020A1BA073CFB0A5EF4E7D7287703 | sha1: 934F0CCF7ECEB440FFECE4A6C9A0B26328DB08EF | sha256: BB127B186091E654DC71CEA577697BA02510B688E95D2EEB37B88F51AD49F2A4 | sha512: D21D68636BA9ACF1B135FDF6A4F1D7CCB29DC1CCC7A33D914F56FD7BDE1CA03B19866E76178F9C12FD9B35405E0177E2018E42441A513B76250B67C0C396BB8B
md5: BB900F61EF4BFD13617AA06EFE1E464D | sha1: 6B991787AF9A33523EA40685C28704C1649E4839 | sha256: 4847F997F6CE6D9F4249612B5156E0BBE13CFCF31B12FD51A5B23439334905C9 | sha512: 0036CEFD04BC88824978CA17E2F55C2AB4430267A463AB5339F0DA2108352AD607BE5909C7178C34A5D7EC5299A4354714DA0DC4F3F5ED0A793271CE6D570AED
Remove-BinFile "grm" "$packageFolder\Tools\GitReleaseManager.exe"
Log in or click on link to see number of positives.
- CommandLine.dll (4847f997f6ce) - ## / 64
- gitreleasemanager.portable.0.7.0.nupkg (8df6acddc2d0) - ## / 62
- GitReleaseManager.Core.dll (bb127b186091) - ## / 67
- GitReleaseManager.exe (fcdeb50218d2) - ## / 68
- Octokit.dll (df7741527122) - ## / 62
- YamlDotNet.dll (47c19bc706c3) - ## / 64
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 |
---|---|---|---|---|
GitReleaseManager 0.17.0 | 58 | Saturday, March 9, 2024 | Approved | |
GitReleaseManager 0.16.0 | 85 | Tuesday, November 14, 2023 | Approved | |
GitReleaseManager 0.15.0 | 86 | Wednesday, August 23, 2023 | Approved | |
GitReleaseManager 0.14.0 | 43 | Tuesday, August 22, 2023 | Approved | |
GitReleaseManager 0.13.0 | 640 | Monday, January 31, 2022 | Approved | |
GitReleaseManager 0.12.1 | 390 | Monday, September 20, 2021 | Approved | |
GitReleaseManager 0.12.0 | 474 | Monday, May 31, 2021 | Approved | |
GitReleaseManager 0.11.0 | 3201 | Monday, March 16, 2020 | Approved | |
GitReleaseManager 0.10.3 | 495 | Saturday, January 25, 2020 | Approved | |
GitReleaseManager 0.10.2 | 265 | Wednesday, January 15, 2020 | Approved | |
GitReleaseManager 0.10.0 | 167 | Monday, January 13, 2020 | Approved | |
GitReleaseManager 0.9.0 | 481 | Tuesday, November 19, 2019 | Approved | |
GitReleaseManager 0.8.0 | 4082 | Sunday, December 30, 2018 | Approved | |
GitReleaseManager 0.7.1 | 3558 | Saturday, May 19, 2018 | Approved | |
GitReleaseManager 0.5.0 | 8563 | Sunday, July 10, 2016 | Approved | |
GitReleaseManager 0.4.0 | 521 | Saturday, January 9, 2016 | Approved | |
GitReleaseManager 0.3.0 | 465 | Friday, July 10, 2015 | Approved |
Copyright 2015
This package has no dependencies.
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.
gittools (maintainer) on 26 Feb 2018 10:42:09 +00:00:
User 'gittools' (maintainer) submitted package.
gittools (maintainer) on 26 Feb 2018 10:45:09 +00:00:
User 'gittools' (maintainer) submitted package.
chocolatey-ops (reviewer) on 26 Feb 2018 11:17:22 +00:00:
gitreleasemanager.portable has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
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...Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
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 26 Feb 2018 11:36:06 +00:00:
gitreleasemanager.portable has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/828dfe501bce39dadc5bf396514c6751 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 18 Mar 2018 11:40:28 +00:00:
We've found gitreleasemanager.portable v0.7.0 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.
chocolatey-ops (reviewer) on 21 Dec 2018 10:32:09 +00:00:
Unfortunately there has not been progress to move gitreleasemanager.portable v0.7.0 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.
Status Change - Changed status of package from 'submitted' to 'rejected'.