Git Product home page Git Product logo

circleci-step-outputter's Introduction

circle-step-outputter

Greenkeeper badge Build Status

Writes CircleCI step output to a file

Install

$ npm install --global circle-step-outputter

Usage

CLI

$ circle-step-outputter --help

  Writes CircleCI build step output to a file

  Usage
    $ circle-step-outputter [options]

  Options
    --baseFileName [Default: "test-output"]
    --repoSlug [Default: $CIRCLE_PROJECT_USERNAME/$CIRCLE_PROJECT_REPONAME]
    --buildNum [Default: $CIRCLE_BUILD_NUM]
    --token [Default: $CIRCLE_API_TOKEN]
    --step [Default: "npm test"] - a build step name substring

  Examples
    $ circle-step-outputter --repoSlug="artemv/circleci-step-outputter" --buildNum=2
  This will write test-output.json, or test-output0.txt, test-output1.txt ... test-output4.txt if there are
  multiple actions in the step (usually parallel actions).

For public/open source projects specifying token is not needed - you only need to do it for private projects. You can generate the token here: api token creation

API

const circleStepOutputter = require('circle-step-outputter');

circleStepOutputter({repoSlug: "artemv/circleci-step-outputter", buildNum: 2});

circleStepOutputter([options])

options

Type: Object

See CLI section for options list.

License

MIT © Artem Vasiliev

circleci-step-outputter's People

Contributors

artemv avatar dependabot[bot] avatar greenkeeper[bot] avatar mernst avatar ro31337 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

circleci-step-outputter's Issues

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

The devDependency ava was updated from 3.0.0 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.

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
  • ci/circleci: test: Your tests passed on CircleCI! (Details).
  • ci/circleci: publish-test: Your tests failed on CircleCI (Details).
  • continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Release Notes for 3.1.0

AVA can now load pre-compiled TypeScript files!

First, install the new @ava/typescript package:

npm install --save-dev @ava/typescript

Now let's assume your TypeScript files are in a src directory, output to a build directory. Configure AVA like so:

ava.config.js file:

export default {
  typescript: {
    rewritePaths: {
      'src/': 'build/'
    }
  }
}

Compile your TypeScript files and run your tests! Or, to run a specific test file, run npx ava src/test.ts.

For more examples see the @ava/typescript package.

As exciting as this is, it's still early days. We need your help improving our TypeScript support. Check out the open issues.

Other changes

Thanks to @jhechtf for fixing our TypeScript recipe after the changes in AVA 3.0 91a0086

See v3.0.0...v3.1.0 for all changes.

Commits

The new version differs by 3 commits.

  • 56338dc 3.1.0
  • e4fef0c Rudimentary support for loading TypeScript test files
  • 91a0086 Remove v2 configuration from TypeScript recipe

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

The devDependency babel-eslint was updated from 10.0.3 to 10.1.0.

🚨 View failing branch.

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

babel-eslint 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
  • ci/circleci: test: Your tests failed on CircleCI (Details).
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 2 commits.

  • 4bd049e 10.1.0
  • 2c754a8 Update Babel to ^7.7.0 and enable Flow enums parsing (#812)

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 🌴

circle.yml example

Can you provide a step by step how or where and what to place in the .circleci/config.yml file.

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

The devDependency eslint was updated from 6.0.1 to 6.1.0.

🚨 View failing branch.

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

eslint 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 is in progress (Details).
  • ci/circleci: test: Your tests failed on CircleCI (Details).

Release Notes for v6.1.0
  • 8f86cca Upgrade: eslint-scope@^5.0.0 (#12011) (Kevin Partington)
  • d08683e Fix: glob processing (fixes #11940) (#11986) (Toru Nagashima)
  • bfcf8b2 Fix: dot-location errors with parenthesized objects (fixes #11868) (#11933) (Milos Djermanovic)
  • 79e8d09 Fix: add parens for sequence expr in arrow-body-style (fixes #11917) (#11918) (Pig Fang)
  • 105c098 Docs: update docs for object-curly-spacing (fixes #11634) (#12009) (Chiawen Chen)
  • c90a12c Chore: update release script for new website repo (#12006) (Kai Cataldo)
  • e2c08a9 Sponsors: Sync README with website (ESLint Jenkins)
  • b974fcb Update: Check computed property keys in no-extra-parens (#11952) (Milos Djermanovic)
  • 222d27c Update: Add for-in and for-of checks for props in no-param-reassign (#11941) (Milos Djermanovic)
  • e4c450f Fix: no-extra-parens autofix with in in a for-loop init (fixes #11706) (#11848) (Milos Djermanovic)
  • 2dafe2d Fix: prefer-const produces invalid autofix (fixes #11699) (#11827) (Milos Djermanovic)
  • cb475fd Fix: Cache file error handling on read-only file system. (fixes #11945) (#11946) (Cuki)
  • 89412c3 Docs: Fixed a typo (fixes #11999) (#12000) (Eddie Olson)
  • 6669f78 Fix: --init with Vue.js failed (fixes #11970) (#11985) (Toru Nagashima)
  • 93633c2 Upgrade: Upgrade lodash dependency (fixes #11992) (#11994) (Cyd La Luz)
  • 776dae7 Docs: fix wrong Node.js version in getting started (#11993) (Toru Nagashima)
  • 4448261 Docs: some typos and optimization points (#11960) (Jason Lee)
  • 2a10856 Chore: Add temporary test files to .gitignore (#11978) (Milos Djermanovic)
  • d83b233 Chore: update path for release bundles (#11977) (Kai Cataldo)
  • 1fb3620 Fix: creating of enabledGlobals object without prototype (fixes #11929) (#11935) (finico)
  • c2f2db9 Docs: Replace global true and false with writable and readonly in rules (#11956) (Milos Djermanovic)
  • 19335b8 Fix: actual messageId and expected messageId are switched in rule tester (#11928) (Milos Djermanovic)
  • 8b216e0 Docs: Fix incorrect example comments for unicode-bom rule (fixes #11937) (#11938) (Brandon Yeager)
  • cc3885b Chore: add v8-compile-cache to speed up instantiation time (#11921) (薛定谔的猫)
  • d8f2688 Upgrade: deps (#11904) (薛定谔的猫)
  • e5f1ccc Docs: add 'stricter rule config validating' in migrating docs (#11905) (薛定谔的猫)
Commits

The new version differs by 28 commits.

  • 02d7542 6.1.0
  • 5997f7a Build: changelog update for 6.1.0
  • 8f86cca Upgrade: eslint-scope@^5.0.0 (#12011)
  • d08683e Fix: glob processing (fixes #11940) (#11986)
  • bfcf8b2 Fix: dot-location errors with parenthesized objects (fixes #11868) (#11933)
  • 79e8d09 Fix: add parens for sequence expr in arrow-body-style (fixes #11917) (#11918)
  • 105c098 Docs: update docs for object-curly-spacing (fixes #11634) (#12009)
  • c90a12c Chore: update release script for new website repo (#12006)
  • e2c08a9 Sponsors: Sync README with website
  • b974fcb Update: Check computed property keys in no-extra-parens (#11952)
  • 222d27c Update: Add for-in and for-of checks for props in no-param-reassign (#11941)
  • e4c450f Fix: no-extra-parens autofix with in in a for-loop init (fixes #11706) (#11848)
  • 2dafe2d Fix: prefer-const produces invalid autofix (fixes #11699) (#11827)
  • cb475fd Fix: Cache file error handling on read-only file system. (fixes #11945) (#11946)
  • 89412c3 Docs: Fixed a typo (fixes #11999) (#12000)

There are 28 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/babel is breaking the build 🚨

The devDependency @ava/babel was updated from 1.0.0 to 1.0.1.

🚨 View failing branch.

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

@ava/babel 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 is in progress (Details).
  • ci/circleci: test: Your tests passed on CircleCI! (Details).
  • ci/circleci: publish-test: Your tests failed on CircleCI (Details).

Release Notes for 1.0.1
  • Ensure pre-compiled .cjs files can be loaded, with thanks to @gloryofrobots

v1.0.0...v1.0.1

Commits

The new version differs by 5 commits.

  • a599a28 1.0.1
  • 801c73c XO: Temporarily disable import/order rule
  • 775114b Update require-precompiled
  • 7df10bb Update dependencies
  • b2a3676 Add code of conduct, contributing guide, issue templates

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

The devDependency codecov was updated from 3.6.2 to 3.6.3.

🚨 View failing branch.

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

codecov 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
  • ci/circleci: test: Your tests passed on CircleCI! (Details).
  • continuous-integration/travis-ci/push: The Travis CI build passed (Details).
  • ci/circleci: publish-test: Your tests failed on CircleCI (Details).

Release Notes for v3.6.3

AWS Codebuild fixes + package updates

Commits

The new version differs by 10 commits.

  • 7856231 v3.6.3
  • 96e6d96 Merge pull request #166 from codecov/chore/updates
  • c8ea169 update deps
  • 7c4cdc4 Merge pull request #149 from aiell0/master
  • 62389fa Merge pull request #162 from codecov/dependabot/npm_and_yarn/handlebars-4.5.3
  • 73ae008 Add dependabot config
  • ccf3862 Update README.md
  • 467a495 Bump handlebars from 4.1.2 to 4.5.3
  • 8acbe96 Retest
  • acd92f4 Test when codebuild isn't triggered by webhooks.

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

The devDependency codecov was updated from 3.5.0 to 3.6.0.

🚨 View failing branch.

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

codecov 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 is in progress (Details).
  • ci/circleci: test: Your tests failed on CircleCI (Details).

Commits

The new version differs by 11 commits.

  • 2ed978c v3.6.0
  • 024cced Merge pull request #135 from iansu/codebuild
  • 24a0a76 Merge branch 'master' into codebuild
  • f628c33 Merge pull request #145 from fabiendem/semaphore-compat
  • 0c57093 Rename semaphore v2 clearly in tests
  • 5a5c489 Add retro-compatibility for Semaphore 1.x and maintain support for 2.x
  • a45a9b5 Revert "Updates Semaphore CI Service for 2.0 (#132)"
  • e2f6b81 Test improvements
  • 3faacd4 Add support for AWS CodeBuild
  • 8371836 Create CODE_OF_CONDUCT.md (#133)
  • 6167aa8 Updates Semaphore CI Service for 2.0 (#132)

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 simple-semantic-config is breaking the build 🚨

The devDependency simple-semantic-config was updated from 6.0.14 to 6.0.16.

🚨 View failing branch.

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

simple-semantic-config 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 is in progress (Details).
  • Tidelift: Scanning dependencies (Details).
  • ci/circleci: test: Your tests failed on CircleCI (Details).

Commits

The new version differs by 21 commits.

  • d4d3f34 chore: bump version
  • 21813f7 chore: upgrade deps
  • 23e2eaa Merge pull request #6 from artemv/dependabot/npm_and_yarn/eslint-utils-1.4.2
  • 9fc2778 Merge pull request #7 from artemv/dependabot/npm_and_yarn/mixin-deep-1.3.2
  • 1e52503 Merge pull request #4 from artemv/dependabot/npm_and_yarn/lodash.mergewith-4.6.2
  • a7697ff Merge pull request #5 from artemv/dependabot/npm_and_yarn/lodash-4.17.14
  • 0e41d97 build(deps): bump mixin-deep from 1.3.1 to 1.3.2
  • 7b3413a build(deps): bump eslint-utils from 1.3.1 to 1.4.2
  • fd92766 build(deps): bump lodash from 4.17.11 to 4.17.14
  • f3458c8 build(deps): bump lodash.mergewith from 4.6.1 to 4.6.2
  • 94e2d53 fix(doc): removed unfinished comment
  • 6a57113 Merge pull request #3 from artemv/dependabot/npm_and_yarn/fstream-1.0.12
  • 7ab7f0b Merge pull request #2 from artemv/dependabot/npm_and_yarn/js-yaml-3.13.1
  • fc3b430 Merge pull request #1 from artemv/dependabot/npm_and_yarn/handlebars-4.1.2
  • 34a173f fix(doc): corrected

There are 21 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 simple-semantic-config is breaking the build 🚨

The devDependency simple-semantic-config was updated from 6.0.16 to 6.1.0.

🚨 View failing branch.

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

simple-semantic-config 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
  • ci/circleci: test: Your tests failed on CircleCI (Details).
  • continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).

Commits

The new version differs by 3 commits.

  • c0435bc feat: upgraded semantic-release
  • e7f4f9d Merge pull request #8 from artemv/dependabot/npm_and_yarn/npm-6.13.4
  • 70ea0a8 build(deps): bump npm from 6.11.3 to 6.13.4

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.3.0 to 2.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 is in progress (Details).
  • ci/circleci: test: Your tests failed on CircleCI (Details).

Release Notes for 2.4.0

Experimental t.try() assertions

Thanks to the amazing work and patience of @qlonik we're shipping a new assertion! t.try() lets you perform assertions and decide whether to commit or discard their outcome. All kinds of interesting things can be built on top of this, from fuzzy testers to new test interfaces and more.

We're excited to get this out there, but it's not quite done yet. For now you have to opt in to this new feature. Being opt-in, we may make changes (breaking ones even!) until we feel this is stable.

To opt in, configure AVA with the following:

package.json:

{
  "ava": {
    "nonSemVerExperiments": {
      "tryAssertion": true
    }
  }
}

ava.config.js:

export default {
	nonSemVerExperiments: {
		tryAssertion: true
	}
};

We'd love to hear your feedback. Please join us in this issue: #2250

Also, if you're looking to help out with the remaining issues so that we can ship this without the opt-in, have a look at this project: https://github.com/orgs/avajs/projects/1

Thanks again @qlonik!

Other changes

All changes

v2.3.0...v2.4.0

Thanks

Thank you @jeremenichelli, @jamesgeorge007, @dongjae93, @qlonik and @tryzniak. 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 14 commits.

  • 05f077e 2.4.0
  • ca4eff7 Bump dependencies
  • 67e4dea Update endpoint testing recipe to focus on the concept, not libraries
  • 4fdb02d Implement experimental t.try() assertion
  • 782c2d8 Run some tests on Travis still
  • 4c890d9 Add OpenCollective link to README
  • 03c1509 Groundwork to support experimental features
  • 0a5c933 Remove unnecessary flag from tap invocation
  • e598c30 Detect whether error source is on a different drive (on Windows)
  • fb0c536 Fix serialize-error tests on Windows with GitHub Actions
  • 53d7fe1 Allow some fixtures to pass linting when XO is installed without lockfile
  • 11771ba Run CI using GitHub Actions
  • 5538bdc Replace an indexOf() by includes()
  • 49b202f Add shared variables & asynchronous tests to common pitfalls

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 🌴

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


☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io


The devDependency nyc was updated from 15.0.0 to 15.0.1.

🚨 View failing branch.

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

nyc 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
  • ci/circleci: test: Your tests failed on CircleCI (Details).

Commits

The new version differs by 12 commits.

  • d9a76d5 chore(release): 15.0.1
  • 3a577f0 fix: Ignore insignificant lines when coalesce text report (#1300)
  • df34c1c fix: Data merge concurrency limit to prevent OOM (#1293)
  • befbf08 chore: A test where nyc output help text to stderr was flaky (#1269)
  • 9260a70 docs: Remove nyc containing object in json config examples (#1276)
  • bed4729 chore: Minor Markdown tweaks (#1256)
  • fcacc46 chore: Update node-preload to v0.2.1 (#1257)
  • 8b4a148 chore: Update standard to v14.3.1 (#1250)
  • 676ca86 chore: Switch to AppVeyor for Windows testing (#1255)
  • fcd2115 chore: Conditionally set envPath.APPDATA for tests (#1254)
  • 3445b19 chore: Remove the unused uuid dependency (#1252)
  • 559ada2 chore: Remove the unused js-yaml dependency. (#1247)

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 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml
  • The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


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

The dependency meow 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.

meow is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ci/circleci: test: Your tests passed on CircleCI! (Details).
  • continuous-integration/travis-ci/push: The Travis CI build passed (Details).
  • ci/circleci: publish-test: Your tests failed on CircleCI (Details).

Release Notes for v6.0.1

v6.0.0...v6.0.1

Commits

The new version differs by 2 commits.

  • f17525e 6.0.1
  • 16640f1 Replace minimist-options types with own ones (#135)

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 🌴

Specifying step

I noticed it is sufficient to specify the prefix of a step to get its output. So, for a longwinded step such as set -x\nsource aliases.sh\necho foo, I merely needed to say --step set. Is this intentional and can it be documented?

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

Version 15.6.0 of semantic-release was just published.

Branch Build failing 🚨
Dependency [semantic-release](https://github.com/semantic-release/semantic-release)
Current Version 15.5.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
  • ci/circleci: test Your tests failed on CircleCI Details

Release Notes v15.6.0

15.6.0 (2018-06-19)

Features

  • allow to disable the publish plugin hook (4454d57)
Commits

The new version differs by 1 commits.

  • 4454d57 feat: allow to disable the publish plugin hook

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 🌴

Command line options aren't recognised

Running this line:

circle-step-outputter --repoSlug="parse-community/Parse-SDK-iOS-OSX" --buildnum=2952

Results in the --help output. I've tried setting the appropriate environment vars for the user and repo instead of using command line options, and get a little further, but since I can't specify 'step' in this way, still no result :(

Darrens-MacBook-Pro:~ drdaz$ CIRCLE_BUILD_NUM=2952 CIRCLE_PROJECT_USERNAME="parse-community" CIRCLE_PROJECT_REPONAME="Parse-SDK-iOS-OSX" circle-step-outputter --stepName="bundle exec rake test:macos"
querying "https://circleci.com/api/v1.1/project/github/parse-community/Parse-SDK-iOS-OSX/2952" for meta
You specified invalid step identifier, "npm test". Steps available in build: ["Spin up Environment","Checkout code","git submodule update --init --recursive\ngem install bundler\nbundle install\n","bundle exec rake test:macos","Uploading test results"]

macOS 10.14.5, node 12.4.0, npm 6.10.0.

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

The devDependency eslint was updated from 5.15.3 to 5.16.0.

🚨 View failing branch.

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

eslint 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
  • ci/circleci: test: Your tests failed on CircleCI (Details).
  • continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Release Notes for v5.16.0
  • dfef227 Build: gensite passes rulesMeta to formatter rendering (#11567) (Kevin Partington)
  • c06d38c Fix: Allow HTML formatter to handle no meta data (#11566) (Ilya Volodin)
  • 87a5c03 Docs: func-style: clarify when allowArrowFunctions is used (#11548) (Oliver Joseph Ash)
  • bc3e427 Update: pass rule meta to formatters RFC 10 (#11551) (Chris Meyer)
  • b452f27 Chore: Update README to pull in reviewer data (#11506) (Nicholas C. Zakas)
  • afe3d25 Upgrade: Bump js-yaml dependency to fix Denial of Service vulnerability (#11550) (Vernon de Goede)
  • 4fe7eb7 Chore: use nyc instead of istanbul (#11532) (Toru Nagashima)
  • f16af43 Chore: fix formatters/table test (#11534) (Toru Nagashima)
  • 78358a8 Docs: fix duplicate punctuation in CLI docs (#11528) (Teddy Katz)
Commits

The new version differs by 11 commits.

  • ded2f94 5.16.0
  • ea36e13 Build: changelog update for 5.16.0
  • dfef227 Build: gensite passes rulesMeta to formatter rendering (#11567)
  • c06d38c Fix: Allow HTML formatter to handle no meta data (#11566)
  • 87a5c03 Docs: func-style: clarify when allowArrowFunctions is used (#11548)
  • bc3e427 Update: pass rule meta to formatters RFC 10 (#11551)
  • b452f27 Chore: Update README to pull in reviewer data (#11506)
  • afe3d25 Upgrade: Bump js-yaml dependency to fix Denial of Service vulnerability (#11550)
  • 4fe7eb7 Chore: use nyc instead of istanbul (#11532)
  • f16af43 Chore: fix formatters/table test (#11534)
  • 78358a8 Docs: fix duplicate punctuation in CLI docs (#11528)

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.