Git Product home page Git Product logo

statetransition-mixin's Introduction

npm License Typed with TypeScript bundlejs downloads GitHub Issues Build Status Styled with prettier Commitizen friendly Known Vulnerabilities Coverage Status

statetransition-mixin

mixin to declare state transition methods like start & stop

start stop transition example

usage

import { StateTransitionMixin, prepareActions } = from 'statetransition-mixin';

const actions = prepareActions({
start: { // declare start() and call _start() internally
  stopped: { // can be called within stopped state
    target: "running",
    during: "starting",
    timeout: 10
  }
},
stop: { // declare stop() and call _stop() internally
  running: {. // can be called when running
    target: "stopped",
    during: "stopping",
    timeout: 5
  },
  starting: { // or when starting
    target: "stopped",
    during: "stopping",
    timeout: 10
  }
}
});

class BaseClass {}

class StatefullClass extends StateTransitionMixin(BaseClass, actions, 'stopped') {

  // will be called to go from stopped to running
  async _start() {
    return new Promise(resolve => setTimeout(() => resolve(), 10));
  }
}

let myObject = new StatefullClass();

console.log(myObject.state === 'stopped' ? "is stopped" : "hmm ?")

myObject.start().then( (o) => console.log('started == ${o.state}'));
console.log('starting == ${myObject.state}');

myObject.stop().then( (o) => console.log('stopped == ${o.state}'));
console.log('stopping == ${myObject.state}');

API

Table of Contents

TRANSITION

ongoing transition

TRANSITION_PROMISE

promise of the ongoing transition

Action

Type: Object

Properties

  • name string like 'start' or 'stop'
  • transitions Object possible transitions from the current state

Transition

Type: Object

Properties

prepareActions

Compile actions and states

Parameters

Examples

prepareActions({
start:{
 stopped: {
   target: 'running',
   during: 'starting'
}},
stop: {
 running: {
   target: 'stopped',
   during: 'stopping'
 }}});

Returns Array

StateTransitionMixin

Extends a class to support state transtions.

Parameters

clazz

Generated mixin class with support of state transtions.

rejectUnlessResolvedWithin

Rejects promise when it is not resolved within given timeout.

Parameters

Returns Promise

defineActionMethods

Defines methods to perform the state transitions. States are traversed in the following way:

current -> during -> final

If the step is not in one of the transitions current states and also not already in the transitions final state a rejecting promise will be delivered from the generated function. In the 'during' state a function named '_' + (sample: '_start()') will be called first.

It is expected that this function delivers a promise.

Special handling of consequent transitions

While in a during state the former delivered promise will be delivered again. This enshures that several consequent transitions in a row will be fullfiled by the same promise. There can only be one transition in place at a given point in time.

Parameters

  • object Object target object where we define the methods

  • actionsAndStates Object object describing the state transitions

    • actionsAndStates.0
    • actionsAndStates.1

Returns void

install

With npm do:

npm install statetransition-mixin

license

BSD-2-Clause

statetransition-mixin's People

Contributors

arlac77 avatar dependabot-preview[bot] avatar dependabot[bot] avatar greenkeeper[bot] avatar greenkeeperio-bot avatar

Watchers

 avatar  avatar  avatar  avatar

statetransition-mixin's Issues

An in-range update of esm is breaking the build 🚨

The devDependency esm was updated from 3.0.84 to 3.1.0.

🚨 View failing branch.

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

esm 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/travis-ci/push: The Travis CI build passed (Details).
  • ❌ codecov/project: 90.46% (-0.8%) compared to 9b2509d (Details).
  • βœ… codecov/patch: Coverage not affected when comparing 9b2509d...7a8fb2d (Details).

Commits

The new version differs by 424 commits.

  • 33ee0ac Bump to v3.1.0.
  • a84a624 Update deps.
  • 9110dd2 Cleanup readme.
  • 7adc4fd Make Package exposable through require().
  • c149647 Newline nit.
  • 885afd0 Add circular entry to esm loader fake compile data.
  • c7a5a1f Update getNativeSource() for latest Node master branch.
  • 8a3d1ce Remove unneeded catch param.
  • 8e8c354 Add more entry and package cache guards to env modules.
  • b77cf1a Don't cache entry or package instances in isSideloaded().
  • f326152 Fix wasm support regression.
  • fd47bfc Reset entry validation for repl.
  • 7869529 Remove validation dead code from vm hook for now.
  • 6ac3788 Cleanup done() handler.
  • 34c0624 Avoid multi-var assignments.

There are 250 commits in total.

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 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

An in-range update of ava is breaking the build 🚨

The devDependency ava was updated from 3.4.0 to 3.5.0.

🚨 View failing branch.

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

ava 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/travis-ci/push: The Travis CI build failed (Details).

Release Notes for 3.5.0

When using ava debug, you can now specify the address or hostname the inspector is available through by using the --host option. Thanks to @DYefimov for contributing this! 13d6651

See v3.4.0...v3.5.0 for all changes. Spoiler alert: it's just this one πŸ˜‰

Commits

The new version differs by 2 commits.

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 🌴

An in-range update of esm is breaking the build 🚨

The devDependency esm was updated from 3.2.20 to 3.2.21.

🚨 View failing branch.

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

esm 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/travis-ci/push: The Travis CI build passed (Details).
  • ❌ codecov/project: 90.77% (-0.16%) compared to 0e9096e (Details).
  • βœ… codecov/patch: Coverage not affected when comparing 0e9096e...eb85e8a (Details).
  • βœ… coverage/coveralls: First build on greenkeeper/esm-3.2.21 at 95.707% (Details).

Release Notes for 3.2.21
  • Ensured deep parse validation is performed before shallow (#768)
  • Ensured direct Module#_compile() calls are based on default options
  • Ensured .node files are stored in the real Module._cache in Jest (#765)
  • Fixed cache invalidation of re-published modules (#746)
  • Fixed dynamic import use in Puppeteer’s page.evaluate() (#762)
  • Fixed regression with ts-node/register (#769)
  • Fixed regression for packages with invalid "main" fields (#770)
  • Updated %s token of util.formatWithOptions()
Commits

The new version differs by 65 commits.

  • 3afa86c Bump to v3.2.21.
  • 603abaa Update deps.
  • 52615b5 Cleanup misc test descriptions.
  • 2f04cc9 Add CJS variable access tests.
  • 31b8077 Cleanup and comments.
  • 5717b58 Update util.formatWithOptions() inspection with %s.
  • 4da4091 Ensure .node extensions are stored on RealModule._cache. [closes #765]
  • 208b3bb Update deprecation warning code.
  • 25a5b78 Perform deep validation before shallow. [closes #768]
  • 950e741 Mask errors from main hook.
  • 9ede7cb Newline nits.
  • d049dcf Add isExtNode().
  • f9b27e4 Rename ext methods.
  • 1b204db Use more has().
  • 1e04110 More Entry cleanup.

There are 65 commits in total.

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 🌴

An in-range update of ava is breaking the build 🚨

The devDependency ava was updated from 2.0.0 to 2.1.0.

🚨 View failing branch.

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

ava 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/travis-ci/push: The Travis CI build failed (Details).

Release Notes for 2.1.0

Bug fixes

  • AVA's TypeScript definition now explicitly references the Node.js definition bb44da7

Enhancements

  • Did you know you can provide human-readable timeout values? We've now documented this. 486acaf
  • We're now including all stack trace lines in the TAP output (though we still pre-process them). ac212ba
  • Logs from successful hooks are now included in the TAP output. 007c7af
  • Our ESLint plugin helper has been updated to allow extensions and glob patterns to be overridden b3c9ea7

All changes

v2.0.0...v2.1.0

Thanks

Thank you @anishkny, @yovasx2 and @mihai-dinu. We couldn't have done this without you!

Get involved

We welcome new contributors. AVA is a friendly place to get started in open source. We have a great article on getting started contributing and a comprehensive contributing guide.

Commits

The new version differs by 9 commits.

  • 00d9517 2.1.0
  • 911d198 Tweak dependencies, CI
  • 52fc67a Fix package lock
  • bb44da7 Explicitly reference the Node.js type definition
  • b3c9ea7 Allow ESLint rules to override extensions and glob patterns
  • 7366a9d Store an error object in AssertionError rather than a stack trace
  • 007c7af Include logs from successful hooks in TAP output
  • ac212ba Include all (beautified) stack trace lines in TAP reporter output
  • 486acaf Document timeout units

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 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 15.13.17 to 15.13.18.

🚨 View failing branch.

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

semantic-release 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/travis-ci/push: The Travis CI build failed (Details).
  • βœ… coverage/coveralls: First build on greenkeeper/semantic-release-15.13.18 at 96.81% (Details).

Release Notes for v15.13.18

15.13.18 (2019-06-26)

Bug Fixes

Commits

The new version differs by 2 commits.

  • 6b3adf6 fix: revert to execa ^1.0.0
  • 228fed7 docs: document that plugins config is an override (#1216)

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 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

An in-range update of rollup is breaking the build 🚨

Version 0.47.5 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.47.4
Type devDependency

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

As rollup 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
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.47.5 at 89.362% Details
  • βœ… codecov/patch Coverage not affected when comparing 91e80a8...0510b1e Details
  • βœ… codecov/project 89.36% remains the same compared to 91e80a8 Details

Commits

The new version differs by 3 commits.

  • 9cfada0 -> v0.47.5
  • 714ae2d Merge pull request #1558 from rollup/gh-1532
  • 8ec3e0d use Promise.resolve in mapSequence, to ensure each item is thenable - fixes #1532

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

Version 11.1.0 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 11.0.3
Type devDependency

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

As nyc 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
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/nyc-11.1.0 at 89.362% Details
  • βœ… codecov/project 89.36% remains the same compared to 9f2fa8f Details
  • βœ… codecov/patch Coverage not affected when comparing 9f2fa8f...4fb7625 Details

Commits

The new version differs by 5 commits.

  • a3f033f chore(release): 11.1.0
  • a076951 chore: upgrade to latest version of istanbul-lib-instrument
  • 8768afe feat: upgrade to version of spawn-wrap that supports .EXE (#626)
  • 2d92501 chore: attempt to fix appveyor (#623)
  • bbadc1f feat: add support for per file coverage checking (#591)

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

Version 6.3.3 of documentation was just published.

Branch Build failing 🚨
Dependency documentation
Current Version 6.3.2
Type devDependency

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

documentation 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/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 4 commits.

  • 2b4612a chore(release): 6.3.3
  • 4e7673a chore(package): Update lodash, to keep david-dm from crying wolf about security (#1071)
  • acb9e34 chore(package): update fs-extra to version 6.0.1 (#1070)
  • 82c6de2 chore(package): update flow-bin to version 0.71.0 (#1069)

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 🌴

An in-range update of esm is breaking the build 🚨

The devDependency esm was updated from 3.2.22 to 3.2.23.

🚨 View failing branch.

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

esm 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/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 19 commits.

  • a2b7949 Bump to v3.2.23.
  • a50cb19 Update deps.
  • 6e5a22d Revert "Temporarily remove node-sleep until it builds on Node 12+."
  • dff4f0d Add support for public and private static class fields. [closes #801]
  • a0a21ac Align Node error objects with Node 12.2.0.
  • 25e6299 Fix REPL hook in Node 12. [closes #792]
  • 078f335 Update Node test matrix.
  • 82467e3 Move decoyProxy into OwnProxy().
  • 04cdca8 Fix mock scenario tests in Node 12.
  • 2207949 Temporarily remove node-sleep until it builds on Node 12+.
  • 3c50b83 Fix parsing of computed class fields. [closes #787]
  • c93add3 Revert partial package type support. [closes #784]
  • 8389f17 Fix namespace object inspection in Node 12.
  • c94675d Update deps.
  • 56c5f3a Fix fs.promises tests.

There are 19 commits in total.

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 🌴

An in-range update of c8 is breaking the build 🚨

The devDependency c8 was updated from 4.1.4 to 4.1.5.

🚨 View failing branch.

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

c8 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/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 4 commits.

  • 2cc73a6 chore(release): 4.1.5
  • ef28d0a chore: update deps
  • a465b65 fix: remove the unmaintained mkdirp dependency (#91)
  • a27b694 fix: exit with code 1 when report output fails (#92)

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 🌴

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 15.13.16 to 15.13.17.

🚨 View failing branch.

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

semantic-release 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/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v15.13.17

15.13.17 (2019-06-25)

Bug Fixes

  • package: update execa to version 2.0.0 (52c48be)
Commits

The new version differs by 2 commits.

  • 01a0b2d test: use regexp to check missing module message
  • 52c48be fix(package): update execa to version 2.0.0

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 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.47.1 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.47.0
Type devDependency

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

As rollup 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
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.47.1 at 89.362% Details
  • βœ… codecov/patch Coverage not affected when comparing ba0e464...917ae3c Details
  • βœ… codecov/project 89.36% remains the same compared to ba0e464 Details

Commits

The new version differs by 6 commits.

  • be426f4 -> v0.47.1
  • 08a4ed5 Merge branch 'master' of github.com:rollup/rollup
  • 1ccf54d Merge pull request #1548 from rollup/gh-1547
  • a61e61b squelch warning from chalk
  • f85ffe8 ignore external namespace imports when deshadowing - fixes #1547
  • 3c1b2ff update dependencies, lint

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 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

An in-range update of ava is breaking the build 🚨

The devDependency ava was updated from 3.3.0 to 3.4.0.

🚨 View failing branch.

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

ava 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/travis-ci/push: The Travis CI build failed (Details).

Release Notes for 3.4.0

Introducing the t.try() assertion

The new t.try() allows you to try assertions without causing the test to fail:

test('do the thing', async t => {
  const attempt = () => t.try(tt => {
    const result = await getResult()
    // getResult() can be flaky and sometimes throws :(
    tt.is(result, 'expected')
  })

const firstAttempt = await attempt()
if (firstAttempt.passed) return firstAttempt.commit()

t.log('Retrying (just once)')
firstAttempt.discard()
const secondAttempt = await attempt()
secondAttempt.commit()
})

You can use any test implementation with t.try(), including (arrays of) macros. You can decide what to do with attempts. You can even run attempts concurrently, so long as they don't use snapshot assertions.

This is great building block for handling all kinds of advanced test scenarios. We can't wait to see what you'll do with it! Find out more in the assertion documentation.

This feature was previously behind an experimental flag. That flag has now been removed. If you have enabled the flag you'll have to update your AVA config. Also note that as of this release, attempt titles are always prefixed with the title of the parent test 7ee3a0e.

Once again, thank you @qlonik for contributing this new assertion.

Other changes

  • The t.throws() and t.throwsAsync() assertions can now be called with undefined as the second argument. Previously, if you wanted to set an assertion message but did not want to provide any expectations for the thrown error you had to pass null. That's still allowed, of course. d0e2161 @stavalfi
  • ava.config.js files once again work with our @ava/typescript package f4d4edd
  • Our TypeScript definition no longer references @types/node 7a1dacf
  • We've improved the error message shown when test.cb() is used with asynchronous functions or observables f5a8c2b @toddkcarlson
  • The Vue recipe has been updated to use jsdom-global instead of browser-env 3f9c616 @Scrum
  • @fisker optimized how we detect ESM support 8831f54

See v3.3.0...v3.4.0 for all changes.

Commits

The new version differs by 13 commits.

  • 8630636 3.4.0
  • 12ba7bc Ship t.try() without requiring opt-in
  • f4d4edd Evaluate ava.config.js scripts in current context
  • 8831f54 Improve detection of ESM support
  • d0e2161 Support undefined as second argument to t.throws and t.throwsAsync
  • 324e45f Document t.try() (#2251)
  • da52e5f Bump dependencies
  • 55a3649 Ensure t.try() assigns unique titles when multiple implementations are passed
  • 7ee3a0e Prefix attempt titles with that of parent test
  • a69e4f2 Bump dependencies
  • 7a1dacf Remove @types/node reference
  • 3f9c616 Update Vue recipe to use JSDom rather than browser-env
  • f5a8c2b Improve error message when test.cb() is used with promises

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 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.46.2 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.46.1
Type devDependency

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

As rollup 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
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.46.2 at 89.362% Details
  • βœ… codecov/patch Coverage not affected when comparing 9478fc7...508e6d4 Details
  • βœ… codecov/project 89.36% remains the same compared to 9478fc7 Details

Commits

The new version differs by 7 commits.

  • 8e7cbe0 -> v0.46.2
  • 4451ee2 Merge pull request #1537 from rollup/gh-1480
  • 7a2a8d2 init rhs of for-in loop head with correct scope - fixes #1480
  • d0392e9 Merge pull request #1536 from rollup/gh-1533
  • a30f5a5 pass through all necessary options to bundle.write in rollup.watch (fixes #1533)
  • 834acb3 get test to pass
  • bd39fa3 allow passing interop through cli - true/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 documentation is breaking the build 🚨

The devDependency documentation was updated from 11.0.0 to 11.0.1.

🚨 View failing branch.

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

documentation 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/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 8 commits.

  • f111030 chore(release): 11.0.1
  • 14298bb fix: toc with children getting displayed as "note" (#1253)
  • b6901b4 refactor: remove unnecessary trailing slash (#1254)
  • 9ba3fd1 chore: Update split.js (#1250)
  • 7d12421 docs: HTTPS link to remark.js.org (#1251)
  • f0ed12e docs: fix a couple of URLs to prevent redirects (#1249)
  • 725f6bb docs: fix link to basscss.com (#1245)
  • e8734dd docs: Update URLs to prevent redirects (#1244)

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 🌴

An in-range update of esm is breaking the build 🚨

The devDependency esm was updated from 3.2.8 to 3.2.9.

🚨 View failing branch.

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

esm 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/travis-ci/push: The Travis CI build failed (Details).

Release Notes for 3.2.9
  • Fixed Module._cache initialization in Jest (#734)
Commits

The new version differs by 4 commits.

  • 7486662 Bump to v3.2.9.
  • 372f43a Update deps.
  • d372c49 Remove JEST environment variable.
  • daa6ca6 Initialize Module._cache with Jest's require.cache. [closes #734]

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 🌴

An in-range update of semantic-release is breaking the build 🚨

Version 15.6.1 of semantic-release was just published.

Branch Build failing 🚨
Dependency semantic-release
Current Version 15.6.0
Type devDependency

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

semantic-release 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/travis-ci/push The Travis CI build failed Details

Release Notes v15.6.1

15.6.1 (2018-06-26)

Bug Fixes

  • package: update yargs to version 12.0.0 (d4f68a5)
Commits

The new version differs by 1 commits.

  • d4f68a5 fix(package): update yargs to version 12.0.0

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 🌴

An in-range update of semantic-release is breaking the build 🚨

Version 7.0.2 of semantic-release just got published.

Branch Build failing 🚨
Dependency semantic-release
Current Version 7.0.1
Type devDependency

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

As semantic-release 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
  • ❌ bitHound - Code null Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/semantic-release-7.0.2 at 89.362% Details
  • ❌ bitHound - Dependencies null Details
  • βœ… security/snyk No new vulnerabilities Details
  • ❌ continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error Details
  • βœ… codecov/project 89.36% remains the same compared to 94c06b9 Details
  • βœ… codecov/patch Coverage not affected when comparing 94c06b9...86eea88 Details

Release Notes v7.0.2

7.0.2 (2017-08-16)

Bug Fixes

  • post: create v1.2.3 tag tag instead of branch (3f85597)

    Note that if a version was released with v7.0.1, you will run into the ENOTINHISTORY error :( To recover, follow these steps:

    1. Make sure you are on your main branch and pulled the latest changes from remote
    2. Edit the package.json file, set "version" to what ever should have been released. As an example, let's say the new version number would be 1.2.3. Save the change
    3. run npm publish to release the new version. Make sure to run any pre-publish tasks first if you have any
    4. revert the changes
    5. create a tag with git tag v1.2.3 (put in the same version as in step 2. Push the tag to GitHub with git push --tags
    6. Manually create a release for the tag

    This will fix the problem and everything will work automagically again from here on now.

Commits

The new version differs by 1 commits.

  • 0c79a9b fix(post): create git tag properly

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

Version 0.60.1 of rollup was just published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.60.0
Type devDependency

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

rollup 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/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 7 commits.

  • 264c867 0.60.1
  • d1b13f2 Merge branch 'large-var-count'
  • 647460f Merge branch 'ongenerate-fix'
  • fbde57e fix input validation after options hook
  • b0eda7c include fix for chunkId closure
  • 2b0b6c9 fix ongenerate signature regression
  • 662ee81 fix large variable count numbering

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 🌴

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 15.13.20 to 15.13.21.

🚨 View failing branch.

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

semantic-release 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/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v15.13.21

15.13.21 (2019-08-12)

Bug Fixes

  • package: update hosted-git-info to version 3.0.0 (391af98)
Commits

The new version differs by 3 commits.

  • 391af98 fix(package): update hosted-git-info to version 3.0.0
  • d45d8b6 docs: fix typo
  • 519df0d chore: remove commitizen from our dependencies

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 🌴

An in-range update of rollup is breaking the build 🚨

Version 0.46.3 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.46.2
Type devDependency

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

As rollup 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
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • βœ… continuous-integration/travis-ci/push The Travis CI build passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.46.3 at 89.362% Details
  • βœ… codecov/patch Coverage not affected when comparing 1bd02bb...b0f2ca6 Details
  • βœ… codecov/project 89.36% remains the same compared to 1bd02bb Details

Commits

The new version differs by 13 commits.

  • b7e1d49 -> v0.46.3
  • 55b2e46 install console-group for debugging convenience
  • c6af5c9 Merge pull request #1542 from rollup/gh-1538
  • f8f2fa7 init for loop scopes correctly
  • 5dec01d Merge pull request #1541 from rollup/gh-1488
  • 0e5f8b6 deshadow indirectly-imported namespaces (#1488)
  • 2e76960 Merge branch 'master' of github.com:rollup/rollup
  • e70dad3 Merge pull request #1540 from rollup/gh-1511
  • a44f442 lint
  • 483dc69 use source-map-support in development
  • cc0e5c7 dont include empty imports for reexported external modules
  • 671757e treat reexports differently from exports
  • 6ba6440 fix external namespace imports in es output (#1511)

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

Version 0.47.3 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.47.2
Type devDependency

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

As rollup 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
  • ❌ bitHound - Code 1 failing file. Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • ❌ coverage/coveralls Coverage pending from Coveralls.io Details

Commits

The new version differs by 7 commits.

  • 6b94155 -> v0.47.3
  • 586e255 Merge pull request #1551 from rollup/gh-1550
  • c364ec4 deshadow aliased imports (#1550)
  • 1b48335 Merge pull request #1549 from alippai/patch-1
  • a1c19b8 Add appveyor NodeJS 8 builds
  • ae996b7 Add travis for NodeJS 8
  • 3353338 check for process.hrtime, closes #1495

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 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

An in-range update of rollup is breaking the build 🚨

Version 0.46.1 of rollup just got published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.46.0
Type devDependency

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

As rollup 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 passed Details
  • βœ… coverage/coveralls First build on greenkeeper/rollup-0.46.1 at 89.362% Details
  • βœ… codecov/patch Coverage not affected when comparing 50f095c...1e772b6 Details
  • βœ… codecov/project 89.36% remains the same compared to 50f095c Details
  • βœ… bitHound - Dependencies No failing dependencies. Details
  • ❌ bitHound - Code 1 failing file. Details

Commits

The new version differs by 19 commits.

  • 8969272 -> v0.46.1
  • 0d5669b Merge pull request #1529 from rollup/gh-1528
  • f9f389c Merge pull request #1531 from rollup/gh-1530
  • 5d651a7 only ship .js files
  • b962cf6 separate node entry from browser entry
  • d8d5eec update config
  • e8da9f5 remove source-map-support
  • aa2b54b Merge pull request #1527 from rollup/tidy-up-tests
  • 0015e05 about to lose my sense of humour
  • 7cd8717 GODDAMMIT
  • 75152bf almost there
  • b38632e AARGGHHHH
  • 2c05caa please let this work
  • b9d0779 losing my goddamn mind over here
  • 6eba4d1 wtf. why are these tests passing locally but not in ci

There are 19 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 rollup is breaking the build 🚨

Version 0.60.6 of rollup was just published.

Branch Build failing 🚨
Dependency rollup
Current Version 0.60.5
Type devDependency

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

rollup 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/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 9 commits.

  • f91e93d 0.60.6
  • ad4d470 Merge branch 'literal-method-return-value-tracking'
  • 58678fd Use EMPTY_PATH in more places
  • a51d48b Resolve #2253
  • b114c9d Remove forEachReturnExpression and someReturnExpression logic!
  • e329e36 Refactor return value handling
  • 9a707a7 Merge branch 'es-module'
  • e3d6bdd readme updates
  • e9feb7c ES6 Module -> ES module

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 🌴

An in-range update of semantic-release is breaking the build 🚨

Version 15.7.0 of semantic-release was just published.

Branch Build failing 🚨
Dependency semantic-release
Current Version 15.6.6
Type devDependency

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

semantic-release 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/travis-ci/push The Travis CI build failed Details

Release Notes v15.7.0

15.7.0 (2018-07-10)

Bug Fixes

  • do not set path to plugin config defined as a Function or an Array (f93eeb7)

Features

  • allow to define multiple generateNotes plugins (5989989)
Commits

The new version differs by 12 commits.

  • 24ce560 refactor: build plugin pipeline parameters at initialization
  • eb26254 refactor: use Object.entries rather than Object.keys
  • 50061bb refactor: remove unnecessary object destructuring
  • 5989989 feat: allow to define multiple generateNotes plugins
  • 576eb60 refactor: simplify plugin validation
  • f7f4aab refactor: use the lastInput arg to compute the prepare pipeline next input
  • 12de628 refactor: fix incorrect comments in lib/plugins/pipeline.js
  • d303286 docs: fix default value for analyzeCommits plugin
  • ed9c456 refactor: always return an Array of results/errors from a plugin pipeline
  • cac4882 docs: clarify verifyRelease plugin description
  • 09348f1 style: disable max-params warning for lib/plugins/normalize.js
  • f93eeb7 fix: do not set path to plugin config defined as a Function or an Array

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 🌴

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 17.0.2 to 17.0.3.

🚨 View failing branch.

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

semantic-release 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/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v17.0.3

17.0.3 (2020-02-13)

Bug Fixes

  • pass a branch name to getGitAuthUrl (e7bede1)
Commits

The new version differs by 6 commits.

  • e7bede1 fix: pass a branch name to getGitAuthUrl
  • 8426b42 chore(package): update tempy to version 0.4.0
  • 804fc2a docs(Troubleshooting): release not found in prereleases branch (e.g. beta) after rebase on master) (#1444)
  • 389e331 chore(package): update got to version 10.5.2
  • a93c96f revert: fix: allow plugins to set environment variables to be used by other plugins
  • 68f7e92 fix: allow plugins to set environment variables to be used by other plugins

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 🌴

An in-range update of semantic-release is breaking the build 🚨

Version 15.9.8 of semantic-release was just published.

Branch Build failing 🚨
Dependency semantic-release
Current Version 15.9.7
Type devDependency

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

semantic-release 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/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes v15.9.8

15.9.8 (2018-08-10)

Bug Fixes

  • package: update get-stream to version 4.0.0 (e882096)
Commits

The new version differs by 1 commits.

  • e882096 fix(package): update get-stream to version 4.0.0

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 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this πŸ’ͺ.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.


Good luck with your project ✨

Your semantic-release bot πŸ“¦πŸš€

An in-range update of semantic-release is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 15.1.6 of semantic-release was just published.

Branch Build failing 🚨
Dependency semantic-release
Current Version 15.1.5
Type devDependency

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

semantic-release 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/travis-ci/push The Travis CI build failed Details

Release Notes v15.1.6

15.1.6 (2018-04-11)

Bug Fixes

  • match tag to tagFormat from the begining of the string (31ad231)
Commits

The new version differs by 2 commits.

  • 31ad231 fix: match tag to tagFormat from the begining of the string
  • a8a07b7 docs: clarify FAQ to publish non-JavaScript packages

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.