Git Product home page Git Product logo

haraka-plugin-accounting-files's People

Contributors

acharkizakaria avatar greenkeeper[bot] avatar msimerson avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar

Forkers

vincenthfrance indrajithbandara benjeappl msimerson k2s vishnus

haraka-plugin-accounting-files's Issues

An in-range update of eslint-plugin-node is breaking the build 🚨

Version 5.1.0 of eslint-plugin-node just got published.

Branch Build failing 🚨
Dependency eslint-plugin-node
Current Version 5.0.0
Type devDependency

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

As eslint-plugin-node 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
  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details
Commits

The new version differs by 6 commits.

  • af4737e 5.1.0
  • 04e0cf7 Chore: update travis.yml
  • 4f4e216 Chore: remove package-lock.json
  • 9931ded Chore: upgrade dependencies
  • d34e09c Chore: refactoring
  • 47e0cc2 Update: add resolvePaths option to no-missing-require (#84)

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 eslint-plugin-node is breaking the build 🚨

Version 5.2.0 of eslint-plugin-node just got published.

Branch Build failing 🚨
Dependency eslint-plugin-node
Current Version 5.1.1
Type devDependency

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

As eslint-plugin-node 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
  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details
Release Notes v5.2.0

Bug fixes

Commits

The new version differs by 5 commits.

  • 7189722 5.2.0
  • e7878e9 Update: fix missing deprecated APIs in v6 (fixes #92)
  • 52ceb11 Chore: rm superfluous argument. (#93)
  • 69dc50a Chore: update .travis.yml
  • effdd10 Fix: fix tests for linter.reset

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 eslint is breaking the build 🚨

Version 4.1.0 of eslint just got published.

Branch Build failing 🚨
Dependency eslint
Current Version 4.0.0
Type devDependency

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

As 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/appveyor/branch AppVeyor build failed Details
  • ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
Release Notes v4.1.0
  • e8f1362 Docs: Remove wrong descriptions in padded-block rule (#8783) (Plusb Preco)
  • 291a783 Update: enforceForArrowConditionals to no-extra-parens (fixes #6196) (#8439) (Evilebot Tnawi)
  • a21dd32 New: Add overrides/files options for glob-based config (fixes #3611) (#8081) (Sylvan Mably)
  • 879688c Update: Add ignoreComments option to no-trailing-spaces (#8061) (Jake Roussel)
  • b58ae2e Chore: Only instantiate fileEntryCache when cache flage set (perf) (#8763) (Gyandeep Singh)
  • 9851288 Update: fix indent errors on multiline destructure (fixes #8729) (#8756) (Victor Hom)
  • 3608f06 Docs: Increase visibility of code of conduct (fixes #8758) (#8764) (Kai Cataldo)
  • 673a58b Update: support multiple fixes in a report (fixes #7348) (#8101) (Toru Nagashima)
  • 7a1bc38 Fix: don't pass default parserOptions to custom parsers (fixes #8744) (#8745) (Teddy Katz)
  • c5b4052 Chore: enable computed-property-spacing on ESLint codebase (#8760) (Teddy Katz)
  • 3419f64 Docs: describe how to use formatters on the formatter demo page (#8754) (Teddy Katz)
  • a3ff8f2 Chore: combine tests in tests/lib/eslint.js and tests/lib/linter.js (#8746) (Teddy Katz)
  • b7cc1e6 Fix: Space-infix-ops should ignore type annotations in TypeScript (#8341) (Reyad Attiyat)
  • 46e73ee Fix: eslint --init installs wrong dependencies of popular styles (fixes #7338) (#8713) (Toru Nagashima)
  • a82361b Chore: Prevent package-lock.json files from being created (fixes #8742) (#8747) (Teddy Katz)
  • 5f81a68 New: Add eslintIgnore support to package.json (fixes #8458) (#8690) (Victor Hom)
  • b5a70b4 Update: fix multiline binary operator/parentheses indentation (#8719) (Teddy Katz)
  • ab8b016 Update: fix MemberExpression indentation with "off" option (fixes #8721) (#8724) (Teddy Katz)
  • eb5d12c Update: Add Fixer method to Linter API (#8631) (Gyandeep Singh)
  • 26a2daa Chore: Cache fs reads in ignored-paths (fixes #8363) (#8706) (Victor Hom)
Commits

The new version differs by 22 commits.

  • 7d9e3be 4.1.0
  • e727b7b Build: changelog update for 4.1.0
  • e8f1362 Docs: Remove wrong descriptions in padded-block rule (#8783)
  • 291a783 Update: enforceForArrowConditionals to no-extra-parens (fixes #6196) (#8439)
  • a21dd32 New: Add overrides/files options for glob-based config (fixes #3611) (#8081)
  • 879688c Update: Add ignoreComments option to no-trailing-spaces (#8061)
  • b58ae2e Chore: Only instantiate fileEntryCache when cache flage set (perf) (#8763)
  • 9851288 Update: fix indent errors on multiline destructure (fixes #8729) (#8756)
  • 3608f06 Docs: Increase visibility of code of conduct (fixes #8758) (#8764)
  • 673a58b Update: support multiple fixes in a report (fixes #7348) (#8101)
  • 7a1bc38 Fix: don't pass default parserOptions to custom parsers (fixes #8744) (#8745)
  • c5b4052 Chore: enable computed-property-spacing on ESLint codebase (#8760)
  • 3419f64 Docs: describe how to use formatters on the formatter demo page (#8754)
  • a3ff8f2 Chore: combine tests in tests/lib/eslint.js and tests/lib/linter.js (#8746)
  • b7cc1e6 Fix: Space-infix-ops should ignore type annotations in TypeScript (#8341)

There are 22 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 eslint-plugin-haraka is breaking the build 🚨

Version 1.0.6 of eslint-plugin-haraka just got published.

Branch Build failing 🚨
Dependency eslint-plugin-haraka
Current Version 1.0.5
Type devDependency

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

As eslint-plugin-haraka 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
  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details
Commits

The new version differs by 6 commits.

  • 99d1051 bump version
  • 0906a4a reduce no-useless-escape to warn only
  • 968b392 SublimeLint breaks if you don't use full path (#4)
  • d6ab389 add node env to .eslintrc
  • c04dd99 add .eslintrc.json
  • 508f6b7 version bump 1.0.5

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 eslint-plugin-haraka is breaking the build 🚨

Version 1.0.7 of eslint-plugin-haraka just got published.

Branch Build failing 🚨
Dependency eslint-plugin-haraka
Current Version 1.0.6
Type devDependency

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

As eslint-plugin-haraka 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
  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details
Commits

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

  • 0b5414d Merge pull request #7 from haraka/fix_rules_section
  • 34d28f5 Add example of how to use 'rules' section
  • 10a6d1e Fix format of plugin and bump version.
  • 6736c4a reduce no-useless-escape to warn only (#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 🌴

EACCES: permission denied

Getting error in Haraka log:

Plugin accounting-files failed: Error: EACCES: permission denied, open '/haraka/accounting-files/deferred/

An in-range update of haraka-constants is breaking the build 🚨

Version 1.0.3 of haraka-constants just got published.

Branch Build failing 🚨
Dependency haraka-constants
Current Version 1.0.2
Type dependency

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

haraka-constants 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 is in progress Details
  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details
Commits

The new version differs by 2 commits.

  • 9fa1973 update for eslint 4 compat
  • 4948583 Add Greenkeeper badge 🌴 (#3)

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 haraka-test-fixtures is breaking the build 🚨

Version 1.0.19 of haraka-test-fixtures just got published.

Branch Build failing 🚨
Dependency haraka-test-fixtures
Current Version 1.0.18
Type devDependency

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

As haraka-test-fixtures 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
  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details
Commits

The new version differs by 1 commits.

  • fedba2a remove version from haraka-results

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 eslint-plugin-node is breaking the build 🚨

Version 5.1.1 of eslint-plugin-node just got published.

Branch Build failing 🚨
Dependency eslint-plugin-node
Current Version 5.1.0
Type devDependency

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

As eslint-plugin-node 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
  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details
Commits

The new version differs by 2 commits.

  • 3045e95 5.1.1
  • 0295a7f Fix: no-deprecated-api crash in self-assign (fixes #87)

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 mocha is breaking the build 🚨

Version 3.5.0 of mocha just got published.

Branch Build failing 🚨
Dependency mocha
Current Version 3.4.2
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/appveyor/branch AppVeyor build failed Details
  • ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
Release Notes free-as-in-freezing

3.5.0 / 2017-07-31

📰 News

  • Mocha now has a code of conduct (thanks @kungapal!).
  • Old issues and PRs are now being marked "stale" by Probot's "Stale" plugin. If an issue is marked as such, and you would like to see it remain open, simply add a new comment to the ticket or PR.
  • WARNING: Support for non-ES5-compliant environments will be dropped starting with version 4.0.0 of Mocha!

🔒 Security Fixes

🎉 Enhancements

  • #2696: Add --forbid-only and --forbid-pending flags. Use these in CI or hooks to ensure tests aren't accidentally being skipped! (@charlierudolph)
  • #2813: Support Node.js 8's --napi-modules flag (@jupp0r)

🔩 Other

Commits

The new version differs by 34 commits.

  • 82d879f Release v3.5.0
  • bf687ce update mocha.js for v3.5.0
  • ec73c9a update date for release of v3.5.0 in CHANGELOG [ci skip]
  • 1ba2cfc update CHANGELOG.md for v3.5.0 [ci skip]
  • 065e14e remove custom install script from travis (no longer needed)
  • 4e87046 update karma-sauce-launcher URL for npm@5
  • 6886ccc increase timeout for slow-grepping test
  • 2408d90 Make dependencies use older version of readable-stream to work around incompatibilities introduced by 2.3.0 on June 19th
  • 68a1466 Try not clearing the env for debug in the integration test and see if that fixes Node 0.10 on AppVeyor; if need be, some other fix/workaround can be applied to handle whatever was up with debug without causing this issue
  • 958fbb4 Update new tests to work in browser per test hierarchy reorganization
  • 1df7c94 Merge pull request #2704 from seppevs/increase_test_coverage_of_mocha_js
  • 1f270cd Stop timing out (#2889)
  • 27c7496 upgrade to [email protected]; closes #2859 (#2860)
  • 50fc47d fix CI; closes #2867 (#2868)
  • 1b1377c Add test for ignoreLeaks and fix descriptions

There are 34 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 mocha is breaking the build 🚨

The devDependency mocha was updated from 6.0.0 to 6.0.1.

🚨 View failing branch.

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

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Release Notes for v6.0.1

6.0.1 / 2019-02-21

The obligatory round of post-major-release bugfixes.

🐛 Fixes

These issues were regressions.

  • #3754 - Mocha again finds test.js when run without arguments (@plroebuck)
  • #3756 - Mocha again supports third-party interfaces via --ui (@boneskull)
  • #3755 - Fix broken --watch (@boneskull)
  • #3759 - Fix unwelcome deprecation notice when Mocha run against languages (CoffeeScript) with implicit return statements; returning a non-undefined value from a describe callback is no longer considered deprecated (@boneskull)

📖 Documentation

Commits

The new version differs by 9 commits.

  • 6d3d6b4 Release v6.0.1
  • 2146ece update CHANGELOG.md for v6.0.1
  • 7c9221d backout deprecation of value returned from suite; closes #3744
  • b7cfceb fix --watch not finding any files to execute; closes #3748
  • b836d73 Upgrade docdash version - issue #3663
  • 7926f47 fix --ui issues, closes #3746
  • 00f2ed9 dev dep upgrades from "npm audit" and "npm upgrade"
  • 34afb1a fix(cli/run.js): Revert default glob to match Mocha-5.2
  • 6d5a0db Bring the example congfiguration file in line with the documentation. (#3751)

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 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.