First of all thanks for this package (looks very useful), This is a question actually not a bug.

I want to run publish-release from my build system in this case i would like to use all the defaults from package.json and not be prompted by the wizzard. Is this possible with the current version?

Create automated tests to make application easier to grow

• API
• CLI

Hi there! I'm trying to use this library to automatically create GitHub releases and upload assets as a CI step. I've noticed that when reuseRelease and reuseDraftOnly are true, a duplicate draft release gets created if there's already a published release by the same name.

Here's what I'm trying to accomplish:

• Create a draft release for version v1.0.0 if one doesn't already exist and there's no published release by the same name
• If a draft v1.0.0 release exists, update the release and replace its assets
• If a published v1.0.0 release exists, don't create a new draft release for v1.0.0 and don't update existing assets

It doesn't seem possible to do this currently since using reuseRelease and reuseDraftOnly causes a new draft release to be created if one doesn't already exist with the same name.

Is this the intended behavior? If not, could I send a PR for a new parameter that will skip draft release creation if there's already a published release with the same name?

Thanks!

There should be an option to push a release with the same tag i.e. overwrite existing release.

• Cant re-upload or delete if connection is closed in the middle of the upload.
• Red symbol appear next to the asset inside the release.
• This asset is only listed inside the edit mode of the release.

Description

When you check for reuseRelease, it returns a list of releases and only check the latest one.
If you want to reuse a release that is in the middle of road, you will probably receive an error, because it will try to create a new one.

Expected behavior

Search using Get release by tag name.

Can't use "Get a release by tag name" because "tag name" means existing git tag, but we draft release and don't create git tag.

What we can do

Search for each by the given tag

Problem

You can't get draft release with Get release by tag name.

Every time that there's a problem uploading a release, it throws an TypeError: Cannot read property 'split' of undefined error at

There are a couple of ways this could be achieved:

1. Fail-fast with a nice error message if EDITOR has not been defined.
2. Ask the developer to enter the path to their editor in lieu of EDITOR not being defined.

Ideally, my preference would be for option 2, as I plan to use publish-release within the postpublish hook of all our modules, and this would allow developers who run npm publish to still have things work, rather than requiring them to define EDITOR, then re-run npm run postpublish.

When an asset is missing the release is partially published. It should be all-or-nothing.

Once in a while, when uploading an asset, upload would hang with no event being emitted. The theory is that sometimes uploadAssets never calls the callback or emits any events. In that case, events logged would look like:

...

19:50:47 event upload-progress test-asset.pkg {
  percentage: 0.49955797361536614,
  transferred: 332384,
  length: 66535621,
  remaining: 66203237,
  eta: 199,
  runtime: 0,
  delta: 332384,
  speed: 332384
}

19:50:47  upload-progress test-asset.pkg {
  percentage: 1.5830317417492805,
  transferred: 1053280,
  length: 66535621,
  remaining: 65482341,
  eta: 62,
  runtime: 0,
  delta: 720896,
  speed: 1053280
}

19:50:47 event duplicated-asset test-asset.pkg

20:50:47 Error: Timeout reached while executing task publishReleaseAsync

The last line at 20:50:47 is a timeout check wrapper workaround that is used to identify upload has stalled.

I am asking because of the assets path.

Hi

i am using below command to publish release. tag published successfully but in release tab i cant see publish release it showing as pre-release/draft

publish-release --target_commitish master --draft true --prerelease true --name title --notes "Release notes here" --repo xxx --owner xxxx --tag "v5"

how i can publish saved draft ?

i just want to publish a assets

see aluxian/gulp-github-release#3

I have fixed this bug in this project and in https://github.com/Aluxian/gulp-github-release and will create the Pull requests.

Basically this code as an EventEmitter should emit 'error' events.
It also needed to handle the case where createRelease had a http error status code , ie >= 400, because although it handled a request err request does not think a 400 code is an error... it is correct beacuse it is a valid http response :-).

However if the createRelease gets a 400 or above (eg 401 not authorised, due to bad token) then it need to flag an error or else the downstream uploadAssets gets a bogus body object and fails.

Anyway, PR coming shortly.

Description

By now, you can only reuse a release to:

• Overwrite assets.

Expected behavior

Use option called editRelease, defaults false

When editRelease === true, it will overwrite all options bellow:

• release name
• release notes
• release type
• release target_commitish

release tag: to also edit release tag it would be necessary to have another input tag like newReleaseTag, because it uses the tag to reuse the release and edit it

Options

editRelease - defaults false
deleteEmptyTag - defaults false

Notes

reuseRelease or/and reuseDraftOnly need to be true or pass through the condition

Allow to

• Edit name of release
• Edit release notes
• Change release type from draft to prerelease or release
• Change release type from prerelease/release to release/prerelease or draft*
  *If any release goes from prerelease or release to draft the tag will be left alone
  • deleteEmptyTag - Delete tag if it's edditing from prerelease or release to draft (include an option to enable or not)

Emits

edit-release: Emits when will edit a release. Emits the actual release object.
edited-release: Emits after edit a release. Emits the modified object.
deleted-tag-release: Emits after editing release from prerelease or release to draft, preventing from leaving an empty tag for a edited release. Emits the deleted tag name string.

Why return the object?
Allow to compare the old one with the new one, showing the changes to the interface

Documentation

• Update README.md
• Update cli
• Update help.txt

Needed first

• #31

Check before creating a release that all the assets are ready, and if not raise an error.

Hey guys,

just beginning to use this package. It's kinda strange, everything works except the release name. I input it properly (and I can console.log it out correctly), but it get's prefixed with four hyphens when uploaded.

Is this a known issue?

Thanks for your help!

Currently publish-release defaults the name of assets to it's file name, but in our case we have many assets that represent different things and therefore require more descriptive names.

Github's API allows you to specify a label query param when uploading an asset: https://developer.github.com/v3/repos/releases/#upload-a-release-asset. It would be great to be able to specify this value from the options.

Could this feature please be added?

> np major --no-publish --yolo && release

 ✔ Prerequisite check
 ✔ Git
 ✔ Bumping version
 ✔ Pushing tags

 wifi-tracker 1.0.0 published 🎉
✔ Checking if release already exists
✖ Loading commit history

Error! The first release should be created manually.

Why should the first release be created manually?

Is possible to pass md file as argument to --notes option?

Seems GitHub releases are in fact tags with steroids, so it would be cool to have a boolean flag to create easily a tag or a release.

My use case is to create releases only on NodeOS master branch, but also allow to make releases for the commits in other branchs that pass the tests, but instead of doing full releases, I want to do "tag releases" so they are hidden from the list of "official" releases (the ones from the master branch).

When throwing publish-release prints all available configuration, including the Authorization header. This leaks credentials as the header holds Github private access tokens in most cases, e.g.:
https://travis-ci.org/sinnerschrader/sinnerschrader-website-static/builds/179470281#L1625.

(Token is refreshed)

Assuming reuseRelease: true, what is the expected behaviour of running release twice? At the moment the message Uploading asset MyApp.zip is displayed but the asset is not actually uploaded or replaced the second time the program runs.

I think this should replace the assets with the same name, eventually with a parameter to disable this behaviour and throw an error instead.

Adding this package causes audit to report 3 vulnerabilties because the version of inquirer used the package uses an old version of lodash. Could you update inquirer to fix this?

Soo... sorry for my radio silence! I'm not the greatest at keeping up with a bunch of open source projects.

I'm not actively using this project myself anymore, so I'd like to find some new maintainers who use this a bit more, and let them handle this module how they wish to.

@aluxian @maxcnunes I already have you two as collaborators on this repo; if you'd like, I'll add you to the npm package as well, so you can publish new versions. If you're interested, just put your npm username and I'll add you to the package ASAP.

If there are any other active users who'd like to become maintainers, leave a comment here. Thanks!

Instead of only allow a list of strings, allow an object where keys are the assets and the value the name they will have when uploaded. As a plus, allow a list of objects too, so both objects and strings (when the name will be the same) can be combined.

Please, update lodash to fix some vulnerabilities (reported by npm) for this package. Thanks