mrkmg / node-generate-release Goto Github PK

View Code? Open in Web Editor NEW

37.0 3.0 7.0 325 KB

Generate a release for a project following semver using nodejs and gitflow

License: MIT License

JavaScript 40.01% TypeScript 59.99%

git flow node relase git-flow semver nodejs git-stream

node-generate-release's Issues

Some ideas

After using the generate-relase module here are some ideas and features which would be nice to have 😉

Instead of creating an extra file .release.json it would be nice put options in the config of the package.json.

{
  config: {
    release: {
      no_confirm: false,
      skip_git_pull: false,
      skip_git_push: false,
      // etc ...
    }
  }
}

It would be cool to have a option to set your own default release message.

release_message: "My release message for {version}"

An in-range update of nyc is breaking the build 🚨

Version 10.3.0 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	10.2.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/mrkmg/node-generate-release/builds/227079771?utm_source=github_status&utm_medium=notification),- ❌ **dependency-ci** Failed dependency checks [Details](https://dependencyci.com/builds/202419)

Commits

The new version differs by 4 commits ahead by 4, behind by 2.

55e826d chore(release): 10.3.0
89dc7a6 chore: explicit update of istanbul dependnecies (#562)
1887d1c feat: add support for --no-clean, to disable deleting raw coverage output (#558)
ff73b18 fix: source-maps were not being cached in the parent process when --all was being used (#556)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Unknown Git Plugin

Hello,

I get the following error:

$ npm run release

> [email protected] release
> generate-release

? Release Type patch
? Are you sure you want to update the release from 1.0.0 to 1.0.1 Yes
 ⫸  GIT: Pull from Origin                                  
 ⫸  GIT: Start Release                                     
 ⫸  Files: Write New Version                               
 ⫸  Commands: Pre Commit                                   
 ⫸  GIT: Commit Files                                      
 ⫸  Commands: Post Commit                                  
 ⫸  GIT: Finish Release                                    
 ⫸  GIT: Push to Origin                                    
 ⫸  Commands: Post Complete                                
There was an unknown error.
Unknown Git Plugin

I have git-flow installed. Any idea what's going wrong?

Kind regards
Patrick

An in-range update of sinon is breaking the build 🚨

Version 2.3.8 of sinon just got published.

Branch	Build failing 🚨
Dependency	sinon
Current Version	2.3.7
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As sinon is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
✅ coverage/coveralls First build on greenkeeper/sinon-2.3.8 at 85.802% Details

Release Notes

Fix #1474: stub#usingPromise and stub#onNthCall have unexpected interactions

This release fixes #1474

Commits

The new version differs by 6 commits.

717ebf7 Update docs/changelog.md and set new release id in docs/_config.yml
4f1bcc0 Add release documentation for v2.3.8
083632e 2.3.8
0b5bd48 Update Changelog.txt and AUTHORS for new release
7512258 Merge pull request #1484 from HugoMuller/issue-1474
d14d296 propagates promiseLibrary to new stub behaviors

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Change commit message

Hello @mrkmg , how are you?

I'm trying to change the commit message to conform to @commitlint/config-conventional requirements.

I tried it: generate-release -t patch -m build: {version}

But got an error, the version was not in commit message.

⧗   input: build:
✖   subject may not be empty [subject-empty]
✖   type may not be empty [type-empty]

The input: expected was like: build: 0.0.1

Would you help me?

Thanks

An in-range update of mocha is breaking the build 🚨

Version 3.5.1 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.5.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
✅ coverage/coveralls First build on greenkeeper/mocha-3.5.1 at 85.759% Details

Release Notes

v3.5.1

3.5.1 / 2017-09-09

📰 News

📣 Mocha is now sponsoring PDXNode! If you're in the Portland area, come check out the monthly talks and hack nights!

🐛 Fixes

#2997: Fix missing xit export for "require" interface (@solodynamo)
#2957: Fix unicode character handling in XUnit reporter failures (@jkrems)

🔩 Other

#2986: Add issue and PR templates (@kungapal)
#2918: Drop bash dependency for glob-related tests (@ScottFreeCode)
#2922: Improve --compilers coverage (@ScottFreeCode)
#2981: Fix tpyos and spelling errors (@jsoref)

Commits

The new version differs by 14 commits.

4070a44 Release v3.5.1
466ba73 update CHANGELOG.md for v3.5.1 [ci skip]
1cc0fc0 import/require xit, fixes #2972
74fa66f update nyc to latest; remove workaround in travis script
aa52933 update coveralls strategy; closes #2984
73a5338 Spelling (#2981)
9f403bf Add utils.escape tests and fix unicode escaping
800acbc whitelist "developer-experience" tag for stalebot [ci skip]
5895671 Added issue, pull request templates. (#2869)
075bd51 Merge pull request #2918 from mochajs/no-shell-test
8710438 Work around Node 0.10 Windows flake when testing
13b8340 Ensure that compiler lookup works and not just that transpilation works (#2922)
26d337a Add tests for double-star behavior
c0e6b68 Eliminate glob.sh

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Can't generate release

Running, doesn't pull

# generate-release
? Release Type? patch
? Are you sure you want to update the release from 0.0.1 to 0.0.2 Yes
[Generate Release] GIT: Pull from Origin                          Pulling 
[Generate Release] GIT: Start Release                                     
[Generate Release] Files: Write New Version                               
[Generate Release] Commands: Pre Commit                                   
[Generate Release] GIT: Commit Files                                      
[Generate Release] Commands: Post Commit                                  
[Generate Release] GIT: Finish Release                                    
[Generate Release] GIT: Push to Origin                                    
[Generate Release] Commands: Post Complete

Example gifs

This issue will be a holder for example gifs

An in-range update of inquirer is breaking the build 🚨

Version 3.3.0 of inquirer just got published.

Branch	Build failing 🚨
Dependency	inquirer
Current Version	3.2.3
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

inquirer is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
✅ coverage/coveralls First build on greenkeeper/inquirer-3.3.0 at 85.759% Details

Release Notes

v3.3.0

Added prefix and suffix options to question object to allow you to edit the ? prefix or add a custom suffix.

Commits

The new version differs by 3 commits.

dcf3110 3.3.0
f859745 Added prefix and suffix custom option (#571)
e44b4f3 Update ansi-escapes to the latest version 🚀 (#584)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of nyc is breaking the build 🚨

Version 11.2.0 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	11.1.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
✅ coverage/coveralls First build on greenkeeper/nyc-11.2.0 at 85.759% Details

Commits

The new version differs by 7 commits.

b2ff72d chore(release): 11.2.0
97b962e chore: explicit update of istanbul-lib-instrument (#662)
0dcceda feat: allow cwd to be configured see #620
0fc6d8f chore: add support for --cwd (#542) (#620)
658dba4 fix: remove excluded files from coverage before writing (#649)
dd40dc5 feat: add possibility to filter coverage-maps (#637)
fb3ab92 docs: add link to community slack (#639)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Can't release

Running takes too long for pull and push

$ generate-release -t patch
? Are you sure you want to update the release from 0.0.2 to 0.0.3 Yes
[Generate Release] GIT: Pull from Origin                          Pulling 
[Generate Release] GIT: Start Release                                     
[Generate Release] Files: Write New Version                               
[Generate Release] Commands: Pre Commit                                   
[Generate Release] GIT: Commit Files                                      
[Generate Release] Commands: Post Commit                                  
[Generate Release] GIT: Finish Release                                    
[Generate Release] GIT: Push to Origin                                    
[Generate Release] Commands: Post Complete

An in-range update of mocha is breaking the build 🚨

Version 3.4.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.3.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v3.4.0

Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

This week's highlights:

allowUncaught added to commandline as --allow-uncaught (and bugfixed)
warning-related Node flags

🎉 Enhancements

#2793, #2697: add --allowUncaught to Node.js (@lrowe)
#2733: Add --no-warnings and --trace-warnings flags (@sonicdoe)

🐛 Fixes

#2793, #2697: fix broken allowUncaught (@lrowe)

🔩 Other

#2778: Add license report and scan status (@xizhao)
#2794: no special case for macOS running Karma locally (@boneskull)
#2795: reverts use of semistandard directly ([#2648]) (@boneskull)

Commits

The new version differs by 9 commits0.

7554b31 Add Changelog for v3.4.0
9f7f7ed Add --trace-warnings flag
92561c8 Add --no-warnings flag
ceee976 lint test/integration/fixtures/simple-reporter.js
dcfc094 Revert "use semistandard directly"
93392dd no special case for macOS running Karma locally
4d1d91d --allow-uncaught cli option
fb1e083 fix allowUncaught in browser
4ed3fc5 Add license report and scan status

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

git-flow versiontag

If I specify a versiontag in my git-flow options, I have noticed two issues:

The versiontag is prepended to the version written into my package.json. I don't think that should be.
The tag created in git has the versiontag prepended twice. ex: if my versiontag is 'REL-', my git tags look like 'REL-REL-x.x.x'. I don't think this should be either, it is probably a side effect of prepending the versiontag and putting that value in options.next_version.

Release command fails

I just tried to generate a release however, the package.json gets not updated or commited and i get this error message. Any suggestions?

An in-range update of nyc is breaking the build 🚨

Version 10.3.2 of nyc just got published.

Branch	Build failing 🚨
Dependency	nyc
Current Version	10.3.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ coverage/coveralls Coverage pending from Coveralls.io Details,- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 2 commits0.

e062a86 chore(release): 10.3.2
213206f fix: we should not create a cache folder if cache is false (#567)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of inquirer is breaking the build 🚨

Version 3.1.0 of inquirer just got published.

Branch	Build failing 🚨
Dependency	inquirer
Current Version	3.0.6
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ coverage/coveralls Coverage pending from Coveralls.io Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v3.1.0

password prompt can now rendered hidden input (Unix style)
filter function now also receive the current answers as argument
Smaller package size

Commits

The new version differs by 17 commits.

e612cc5 3.1.0
148cb71 Update eslint-config-xo-space to the latest version 🚀 (#516)
3b93dd5 call chalk.reset() after message prompt (#544)
3ff39a6 chore(package): update chai to version 4.0.1 (#541)
76f1bfe upgrade external-editor to 2.0.4 (#535)
da4eceb pass current answers hash to filter (#533)
f99b398 Use rx-lite-aggregates instead of full rx (#532)
20119a2 fix(package): update ansi-escapes to version 2.0.0 (#527)
e294e16 Update validate fn param docs (#526)
5b3a4a2 Add masked password example
9de81a8 Fix linting of tests
d7db156 Add some tests
50a9beb Switch conditionals
379e0aa Inform user that input is hidden
bf28e76 Password prompt should display no characters

There are 17 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Problem regex GIT_CLEAN_REGEX

Good night, I can not say if it could be considered a bug, but always I run the command to generate the release, the error message was displayed: 'Working directory is not clean, not ready for release'

I noticed that installing git on ubuntu via apt-get translated the reply messages into my language.

So the regex did not work. I changed the regex and everything worked perfectly.

Excellent project

getopt does not support spaces in arguments on Mac OS X

[Generate Release] GIT: Pull from Origin
[Generate Release] GIT: Pull from Origin                         Complete
[Generate Release] GIT: Start Release                            Complete
[Generate Release] Files: Write New Version                      Complete
[Generate Release] Commands: Pre Commit                          Complete
[Generate Release] GIT: Commit Files                             Complete
[Generate Release] Commands: Post Commit                         Complete
[Generate Release] GIT: Finish Release                          Finishing
[Generate Release] Commands: Post Complete
git flow release finish -m Release 0.3.0 0.3.0 returned 2.

 Output:

 flags:FATAL the available getopt does not support spaces in options

I get a problem when running the command on OSX.
There is a bug about this on gitflow.

Can you add it so that FLAGS_GETOPT_CMD is used if it exists?
Or how to solve this error?

mrkmg / node-generate-release Goto Github PK

node-generate-release's Issues

Version 10.3.0 of nyc just got published.

Version 2.3.8 of sinon just got published.

Version 3.5.1 of mocha just got published.

3.5.1 / 2017-09-09

📰 News

🐛 Fixes

🔩 Other

Version 3.3.0 of inquirer just got published.

Version 11.2.0 of nyc just got published.

Version 3.4.0 of mocha just got published.

🎉 Enhancements

🐛 Fixes

🔩 Other

Version 10.3.2 of nyc just got published.

Version 3.1.0 of inquirer just got published.

Recommend Projects

Recommend Topics

Recommend Org