shipshapecode/ember-assign-polyfill

A polyfill for Ember.assign in <= 2.4

ember-assign-polyfill's Issues

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

Version 3.1.0 of ember-cli-eslint just got published.

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

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

As ember-cli-eslint 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](https://travis-ci.org/shipshapecode/ember-assign-polyfill/builds/228477079?utm_source=github_status&utm_medium=notification)

---

Release Notes

v3.1.0

• Use new group option of broccoli-lint-eslint by default (#176)

Commits

The new version differs by 50 commits0.

• 21be33a 3.1.0
• 67a0cc5 3.1.0-beta.2
• 5e256a0 Merge pull request #180 from Turbo87/auto-dist-tag
• 10465b0 CI: Use "auto-dist-tag" for deployment
• 2ea7d00 Merge pull request #171 from cibernox/update-to-latest-ember-cli-beta
• 56a3b48 Update to ember-cli 2.13
• f6e86ba 3.1.0-beta.1
• 0ece8a2 Update CHANGELOG
• 1e8eeec README: Add "Configuration" section
• 41962c4 Merge pull request #176 from Turbo87/group-option
• 4abd4c1 Use new "group" option by default
• 80d820a Use new create() factory function
• 69e25b1 Adjust expected console output
• a043763 Remove unused "js-string-escape" dependency
• 61fdfbc Use built-in "broccoli-lint-eslint" test generators

There are 50 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 🌴

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

Version 1.3.1 of ember-cli-htmlbars just got published.

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

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

As ember-cli-htmlbars 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

---

Commits

The new version differs by 4 commits0.

• b46eb48 v1.3.1
• f0c03ec Merge pull request #109 from ember-cli/use-non-deprecated-version-checker-api
• faf7f25 Add yarn.lock.
• 1b27f67 Update ember-cli-version-checker use to avoid deprecated APIs.

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 ember-cli-babel is breaking the build 🚨

Version 6.3.0 of ember-cli-babel just got published.

Branch	Build failing 🚨
Dependency	ember-cli-babel
Current Version	6.2.0
Type	dependency

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

ember-cli-babel 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

---

Commits

The new version differs by 1 commits.

• ca6e8eb release v6.3.0 🎉

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 loader.js is breaking the build 🚨

Version 4.2.0 of loader.js just got published.

Branch	Build failing 🚨
Dependency	loader.js
Current Version	4.1.0
Type	devDependency

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

As loader.js 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

Commits

The new version differs by 14 commits .

• cc53069 release v4.2.0
• 1a453d3 Merge pull request #104 from trentmwillis/redefine
• 93478ef Improve redefinition scenarios
• e289916 Fix test:dev command
• 287a487 Merge pull request #105 from trentmwillis/clarify
• cda1c29 Clarify prime comment
• 562ecf1 Merge pull request #100 from jrowlingson/master
• 6a9b916 remove petal references
• b609262 Merge pull request #95 from chadhietala/heimdall-instrumentation
• c49296d Instrument with heimdall
• 453fe8c Merge pull request #97 from Turbo87/ci-deploy
• 37fef79 CI: Enable automatic NPM deployment for tags
• c4f0755 Merge pull request #96 from chadhietala/dict-registry
• 8a34296 Use dict for registery and seen to avoid filling IC cache

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 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

An in-range update of ember-cli-version-checker is breaking the build 🚨

Version 1.3.0 of ember-cli-version-checker just got published.

Branch	Build failing 🚨
Dependency	ember-cli-version-checker
Current Version	1.2.0
Type	dependency

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

ember-cli-version-checker 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](https://travis-ci.org/shipshapecode/ember-assign-polyfill/builds/224959288)

---

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 🌴

Version

Looks like the true polyfill conversion was never versioned. Can you publish so that the README reflects latest.

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

Version 6.0.0-beta.10 of ember-cli-babel just got published.

Branch	Build failing 🚨
Dependency	ember-cli-babel
Current Version	6.0.0-beta.9
Type	dependency

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

As ember-cli-babel 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

Commits

The new version differs by 6 commits .

• ffff43b release v6.0.0-beta.10 🎉
• 3b43841 Merge pull request #131 from babel/expose-addon-powerz
• 15644f8 lock file
• 117a409 expose addon.buildBabelOptions and addon.transpileTree(tree, options) so that add ons can have additional powerz
• 4ab3d4a Merge pull request #128 from babel/rwjblue-patch-1
• 96e03e8 First pass at README updates for 6.

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 loader.js is breaking the build 🚨

Version 4.5.0 of loader.js just got published.

Branch	Build failing 🚨
Dependency	loader.js
Current Version	4.4.1
Type	devDependency

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

As loader.js 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

---

Commits

The new version differs by 7 commits.

• 094e20b release v4.5.0 🎉
• db2f6a6 Merge pull request #126 from ember-cli/moduleId
• 204838b rename mod.name => mod.id
• 4fa0fe0 add require.moduleId to allow a module to know its ID
• f62bc54 Merge pull request #121 from ember-cli/define-exports
• d963886 Update README.md
• 928e18f add define.exports

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 ember-cli-babel is breaking the build 🚨

Version 6.4.1 of ember-cli-babel just got published.

Branch	Build failing 🚨
Dependency	ember-cli-babel
Current Version	6.4.0
Type	dependency

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

ember-cli-babel 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

---

Commits

The new version differs by 6 commits.

• 63045ce v6.4.1
• 6e8bc39 Merge pull request #154 from rwjblue/provide-annotation-to-babel-transpiler
• 465353d Refactor README.
• 79e5604 Update babel-plugin-debug-macros to avoid message building when test passes.
• c53b873 Add convienient broccoli debug tooling.
• 4e523f5 Provide annotation to broccoli-babel-transpiler.

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 🌴

NPM does not allow ads to be displayed on installation

When running yarn install in a project using this polyfill, the console outputs the following advertisement:

NPM's policies prohibit the display of advertisements by packages during installation. From NPM's Open Source Policies:

These kinds of commercial content generally aren't acceptable:
...
2. Packages that display ads at runtime, on installation, or at other stages of the software development lifecycle, such as via npm scripts.

NPM's CTO made some additional comments regarding this issue about a year ago when this policy was put into place: https://www.zdnet.com/article/npm-bans-terminal-ads/

It looks like the offending code was added 2 months ago by #60, I assume unaware that this behavior had already been banned by NPM?

An in-range update of loader.js is breaking the build 🚨

Version 4.3.0 of loader.js just got published.

Branch	Build failing 🚨
Dependency	loader.js
Current Version	4.2.3
Type	devDependency

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

As loader.js 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

Commits

The new version differs by 3 commits .

• d247367 release v4.3.0 🎉
• 31ddcee Merge pull request #117 from ember-cli/runspired-patch-1
• 5ae21dc Remove lib/ from published files.

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 ember-cli-htmlbars-inline-precompile is breaking the build 🚨

Version 0.4.0 of ember-cli-htmlbars-inline-precompile just got published.

Branch	Build failing 🚨
Dependency	ember-cli-htmlbars-inline-precompile
Current Version	0.4.0-beta.2
Type	devDependency

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

As ember-cli-htmlbars-inline-precompile 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](https://travis-ci.org/shipshapecode/ember-assign-polyfill/builds/224668204)

---

Commits

The new version differs by 2 commits0.

• ae552eb 0.4.0
• 133cd0a Release 0.4.0 final.

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 🌴

SyntaxError: Expected an identifier but found '.' instead

I tried updating to 2.0.0 in another addon but got a Travis CI error for the ember-lts-2.4 scenario. Reverting back to 1.0.0 resolves the issue. Not sure what's going on here, new to Travis CI so I'm not sure how to see what vendor.js:66484 is..

SyntaxError: Expected an identifier but found '.' instead