Skip to content

Update nodeshift to the latest version 🚀 #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented May 25, 2018

Version 1.8.0 of nodeshift was just published.

Dependency nodeshift
Current Version 1.7.3
Type devDependency

The version 1.8.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of nodeshift.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


Release Notes 1.8.0 release

1.8.0 (2018-05-25)

Features

Commits

The new version differs by 3 commits.

  • 611d3de chore(release): 1.8.0
  • 65af051 chore(package): Greenkeeper/openshift rest client 1.3.0 (#229)
  • 74c482c feat: add the --deploy.env flag (#226)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper bot 🌴

@ghost ghost added the in progress label May 25, 2018
@ghost ghost assigned lholmquist May 25, 2018
@ghost ghost added review and removed in progress labels May 25, 2018
@coveralls
Copy link

Coverage Status

Coverage remained the same at 95.313% when pulling 22a0240 on greenkeeper/nodeshift-1.8.0 into 24bf54e on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 95.313% when pulling 22a0240 on greenkeeper/nodeshift-1.8.0 into 24bf54e on master.

greenkeeper bot added a commit that referenced this pull request May 25, 2018
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 25, 2018

Version 1.8.1 just got published.

Update to this version instead 🚀

Release Notes 1.8.1 release

1.8.1 (2018-05-25)

Bug Fixes

  • README: remove the section talking about default environment variables being added to the DeploymentConfig (14cfb74), closes #231
Commits

The new version differs by 2 commits.

  • 5e7eb71 chore(release): 1.8.1
  • 14cfb74 fix(README): remove the section talking about default environment variables being added to the DeploymentConfig

See the full diff

greenkeeper bot added a commit that referenced this pull request Jun 7, 2018
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jun 7, 2018

Version 1.9.0 just got published.

Update to this version instead 🚀

Commits

The new version differs by 7 commits.

  • efc4d3e chore(release): 1.9.0
  • f98cad4 feat(ingress): create an Ingress if there is one in the .nodeshift directory (#244)
  • e952c44 chore(package): Update tap-spec to the latest version 🚀 (#240)
  • afa232e chore(package): Update openshift-rest-client to the latest version 🚀 (#241)
  • 717379b chore(package): update nyc to version 12.0.2 (#243)
  • 938ec7d fix: travis-ci should use npm install instead of npm ci (#242)
  • 13e5316 feat: add the namespace flag (#234)

See the full diff

@ghost ghost added the in progress label Jun 8, 2018
lholmquist added a commit that referenced this pull request Jun 8, 2018
@ghost ghost removed the in progress label Jun 8, 2018
@greenkeeper greenkeeper bot deleted the greenkeeper/nodeshift-1.8.0 branch June 8, 2018 15:07
lholmquist added a commit that referenced this pull request Jun 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants