Skip to content
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

Jump to bottom

An in-range update of ember-cli is breaking the build 🚨 #59

Closed
greenkeeper bot opened this issue Apr 22, 2017 · 6 comments
Closed

An in-range update of ember-cli is breaking the build 🚨 #59

greenkeeper bot opened this issue Apr 22, 2017 · 6 comments
Labels
greenkeeper

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Apr 22, 2017

Version 2.12.2 of ember-cli just got published.

Branch Build failing 🚨
Dependency ember-cli
Current Version 2.12.1
Type devDependency

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

As ember-cli 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](https://travis-ci.org/datafruits/datafruits/builds/224666802)
Release Notes Kema Kosassa

Setup

  1. npm uninstall -g ember-cli -- Remove old global ember-cli
  2. npm cache clean -- Clear NPM cache
  3. bower cache clean -- Clear Bower cache
  4. npm install -g ember-cli@2.12.2 -- Install new global ember-cli

Project Update

  1. rm -rf node_modules bower_components dist tmp -- Delete temporary development folders.
  2. npm install --save-dev ember-cli@2.12.2 -- Update project's package.json to use latest version.
  3. npm install -- Reinstall NPM dependencies.
  4. bower install -- Reinstall bower dependencies.
  5. ember init -- This runs the new project blueprint on your projects directory. Please follow the prompts, and review all changes (tip: you can see a diff by pressing d). The most common source of upgrade pain is missing changes in this step.

Changelog

The following changes are required if you are upgrading from the previous
version:

Community Contributions

Thank you to all who took the time to contribute!

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 🌴
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Apr 29, 2017

Version 2.12.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes options, options, options, ...

Setup

  1. npm uninstall -g ember-cli -- Remove old global ember-cli
  2. npm cache clean -- Clear NPM cache
  3. bower cache clean -- Clear Bower cache
  4. npm install -g ember-cli@2.12.3 -- Install new global ember-cli

Project Update

  1. rm -rf node_modules bower_components dist tmp -- Delete temporary development folders.
  2. npm install --save-dev ember-cli@2.12.3 -- Update project's package.json to use latest version.
  3. npm install -- Reinstall NPM dependencies.
  4. bower install -- Reinstall bower dependencies.
  5. ember init -- This runs the new project blueprint on your projects directory. Please follow the prompts, and review all changes (tip: you can see a diff by pressing d). The most common source of upgrade pain is missing changes in this step.

Changelog

The following changes are required if you are upgrading from the previous
version:

Community Contributions

Thank you to all who took the time to contribute!

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Apr 29, 2017

Version 2.13.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes Tower of Babel

Setup

  1. npm uninstall -g ember-cli -- Remove old global ember-cli
  2. npm cache clean -- Clear NPM cache
  3. bower cache clean -- Clear Bower cache
  4. npm install -g ember-cli@2.13.0 -- Install new global ember-cli

Project Update

  1. rm -rf node_modules bower_components dist tmp -- Delete temporary development folders.
  2. npm install --save-dev ember-cli@2.13.0 -- Update project's package.json to use latest version.
  3. npm install -- Reinstall NPM dependencies.
  4. bower install -- Reinstall bower dependencies.
  5. ember init -- This runs the new project blueprint on your projects directory. Please follow the prompts, and review all changes (tip: you can see a diff by pressing d). The most common source of upgrade pain is missing changes in this step.

Changelog

The following changes are required if you are upgrading from the previous
version:

Community Contributions

Thank you to all who took the time to contribute!

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 2, 2017

Version 2.13.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes Hexachlorocyclohexane

Setup

  1. npm uninstall -g ember-cli -- Remove old global ember-cli
  2. npm cache clean -- Clear NPM cache
  3. npm install -g ember-cli@2.13.1 -- Install new global ember-cli

Project Update

  1. rm -rf node_modules dist tmp -- Delete temporary development folders.
  2. npm install --save-dev ember-cli@2.13.1 -- Update project's package.json to use latest version.
  3. npm install -- Reinstall NPM dependencies.
  4. ember init -- This runs the new project blueprint on your projects directory. Please follow the prompts, and review all changes (tip: you can see a diff by pressing d). The most common source of upgrade pain is missing changes in this step.

Changelog

The following changes are required if you are upgrading from the previous
version:

Community Contributions

Thank you to all who took the time to contribute!

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jun 25, 2017

Version 2.13.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jul 5, 2017

Version 2.14.0 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes House Elves Don't Work Here

Setup

  1. npm uninstall -g ember-cli -- Remove old global ember-cli
  2. npm cache clean -- Clear NPM cache
  3. npm install -g ember-cli@2.14.0 -- Install new global ember-cli

Project Update

  1. rm -rf node_modules dist tmp -- Delete temporary development folders.
  2. npm install --save-dev ember-cli@2.14.0 -- Update project's package.json to use latest version.
  3. npm install -- Reinstall NPM dependencies.
  4. ember init -- This runs the new project blueprint on your projects directory. Please follow the prompts, and review all changes (tip: you can see a diff by pressing d). The most common source of upgrade pain is missing changes in this step.

Changelog

The following changes are required if you are upgrading from the previous
version:

Community Contributions

Thank you to all who took the time to contribute!

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Apr 5, 2019

  • The devDependency ember-cli was updated from 3.8.1 to 3.8.2.

Your tests are still failing with this version. Compare changes

Release Notes for Grenoble

Setup

npm install -g ember-cli@3.8.2 -- Install new global ember-cli

Project Update

  1. Run npx ember-cli-update --to 3.8.2 -- This will update your app or addon to the latest ember-cli release. You will probably encounter merge conflicts that you should resolve in your normal git workflow.
  2. Run npx ember-cli-update --run-codemods -- This will let you pick codemods to run against your project, to ensure you are using the latest patterns and platform features.

Changelog

Blueprint Changes

Community Contributions

Thank you to all who took the time to contribute!

hergaiety pushed a commit to hergaiety/datafruits that referenced this issue Feb 5, 2020
@brandynbennett
Fix options clobbering (datafruits#59)
8e33a50 
If you passed in `options` hash to a one-way-mask component it would
clobber all defaults instead of only overridding the ones specified.

Made an internal `_options` argument to differentiate between the
external one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
greenkeeper
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mcfiredrill