Version 7.2.3 of babel-eslint just got published.

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

As babel-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 💪

Your Greenkeeper Bot 🌴

Hi! Is there any release doc for 2.x release?

I think having this could be useful:

(sum sectionTotal1 sectionTotal2)

The tree-shaking via only and except configuration options does not seem to work anymore in 4.0.0. I think it was dropped when converting the addon to v2 in #945.

I assume this was done by accident as the feature is still documented:

This breaking change is also not listed in the changelog:

I noticed this when investigating if we can convert Ember Bootstrap to a v2 addon without dropping support for tree-shaking through configuration.

Version 6.1.2 of ember-cli-sass just got published.

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

As ember-cli-sass 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 💪

Your Greenkeeper Bot 🌴

Hi!

I installed this addon in an ember-addon with ember install ember-math-helpers. It put it under the devDependencies section of the package.json. When I tried to run my application it couldn't find the helpers. If I put it under dependencies and do an npm install again, it works. Should the ember install handle this by default?

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

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 💪

Your Greenkeeper Bot 🌴

Version 6.1.3 of ember-cli-sass just got published.

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

As ember-cli-sass 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 💪

Your Greenkeeper Bot 🌴

I can't provide a range of versions so I don't know up until which version this error occurs, but for Ember 3.7 you'll need ember-math-helpers <= 2.10.0.

Ember installations with ember-math-helpers in package.json configured as ^2.10.0 will break when doing a fresh npm install.

Build Error (broccoli-persistent-filter:Babel > [Babel: ember-math-helpers]) in ember-math-helpers/helpers/abs.js

Cannot read property 'getHash' of null

Please see this issue: emberjs/ember.js#14653

Removing ember-math-helpers from my project deals with this failed assertion, but I'd obviously like to keep using this package.

If division is possible, floor and ceil should be present

granted rounding has some difficulty (what to do at xxx.5 and whether to do account rounding)

The current round helper rounds to the nearest integer using Math.round(), it could be useful to have a helper that rounds to a given decimal point...

{{round a decimals=2}}

Good or bad idea?

Version 2.13.1 of ember-source just got published.

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

As ember-source 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 💪

Your Greenkeeper Bot 🌴

Version 1.1.0 of ember-cli-shims just got published.

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

As ember-cli-shims 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 💪

Your Greenkeeper Bot 🌴

Version 6.2.0 of ember-cli-sass just got published.

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

As ember-cli-sass 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 💪

Your Greenkeeper Bot 🌴

Although i have "only" add, mult and sub, all the reexports of the addon's app tree are visible in the consuming app:

Note: the actual helpers in the addon tree seem to be correctly filtered.

I'll see if I can come up with a PR...

I run into the following type error when using ember-math-helpers with types provided by Ember natively.

node_modules/ember-math-helpers/declarations/helpers/sub.d.ts:21:50 - error TS2694: Namespace '"@ember/component/helper"' has no exported member 'EmptyObject'.

21         Named: import("@ember/component/helper").EmptyObject;
                                                    ~~~~~~~~~~

I'm using the following versions:

• ember-math-helpers 4.0.0
• ember-source: 5.4.0
• typescript: 5.2.2
• @glint/core: 1.2.1

ember-math-helpers currently has a 6/10 on Ember Observer.

• I think it's pretty easy to fix. It looks like the contents in Box A should be moved to Box B
• This should fix the error described in Box C and get you up to a 8+/10

🚨 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.