Giter Site home page Giter Site logo

zotoio / github-task-manager Goto Github PK

View Code? Open in Web Editor NEW
13.0 6.0 4.0 5.08 MB

receive github hook, notify agent, receive task results, notify github

License: MIT License

JavaScript 93.24% CSS 1.95% HTML 4.52% Shell 0.29%
task pull-requests agent github ci cd automation docker k8s lambda gitops

github-task-manager's Introduction

github-task-manager

npm version Build Status Code Climate Test Coverage Greenkeeper badge Commitizen friendly semantic-release Docker Build Status

receive github hook, notify agent, receive task results, notify github (Unofficial)

Aims

Create an asynchronous CI agnostic mechanism for running custom test stage gates for github pull requests.

  • allow team leads to configure task sequences without leaving github
  • allow developers to see output from tasks without leaving github
  • trigger multiple jobs in parallel and indicate pending status on pr checks
  • then add results for each back to pull request check/comments as they complete
  • make extensible for other github event handling
  • stateless and deployable to Kubernetes at scale

Design

  • Deploy two functions to lambda via serverless framework ('gtmGithubHook', 'gtmGithubResults')
  • github PR open hook pointed at 'gtmGithubHook' lambda which adds event to a 'PendingQueue' SQS queue
  • agent(s) watch SQS for new test execution jobs
  • agent notifies 'ResultsQueue' SQS queue that a task has started (lambda updates github PR state)
  • agent triggers CI PR build, deploy and tests (plugin for each CI type)
  • agent formats and adds test results to 'ResultsQueue' SQS queue
  • agent notifies SNS topic which triggers 'gtmGithubResults' lambda
  • 'gtmGithubResults' lambda posts results to github pull request.

flow

Install

Environment variable description
GTM_AWS_KMS_KEY_ID aws kms key id
GTM_CRYPT_GITHUB_TOKEN encrypted access token for accessing github
GTM_CRYPT_GITHUB_WEBHOOK_SECRET encrypted shared secret from github webook config
GTM_CRYPT_AWS_ACCESS_KEY_ID encrypted aws key id - for agent only
GTM_CRYPT_AWS_SECRET_ACCESS_KEY encrypted aws secret - for agent only
GTM_CRYPT_AGENT_AWS_SECRET_ACCESS_KEY secret key for agent
GTM_CRYPT_AGENT_AWS_ACCESS_KEY_ID access key for agent
GTM_CRYPT_JENKINS_TOKEN encrypted token
GTM_CRYPT_TEAMCITY_PASSCODE encrypted teamcity executor passcode
GTM_CRYPT_SONAR_LOGIN encrypted sonar access token
GTM_CRYPT_SONAR_GITHUB_OAUTH encrypted github token for sonar to post comments and status
GTM_CRYPT_DOCKER_REG_PASSWORD encrypted docker private registry password
GTM_AWS_REGION awsregion to create resources in
GTM_SQS_PENDING_QUEUE name of SQS queue for new event
GTM_SQS_RESULTS_QUEUE name of SQS queue for results
GTM_SNS_RESULTS_TOPIC name of SNS topic for result ping
GTM_GITHUB_HOST api hostname can be updated for github enterprise
GTM_GITHUB_DEBUG debug mode for api calls
GTM_GITHUB_TIMEOUT github api timeout
GTM_GITHUB_PATH_PREFIX path prefix for github enterprise
GTM_GITHUB_PROXY github api client proxy
GTM_TASK_CONFIG_FILENAME filename in repo to look for for task config - default is .githubTaskManager
AWS_PROXY URL of proxy to use for network requests. Optional
GTM_AGENT_PORT defaults to 9091
GTM_JENKINS_USER login for jenkins executor
GTM_JENKINS_URL url executor uses to talk to jenkins
GTM_JENKINS_CSRF is csrf enabled? true or false
GTM_TEAMCITY_USER teamcity executor user
GTM_TEAMCITY_URL teamcity api url
GTM_DOCKER_IMAGE_WHITELIST comma separated list of regex of allows docker images eg. alpine:*,bash:latest
GTM_DOCKER_IMAGE_WHITELIST_FILE use an optional docker whitelist file .dockerImageWhitelistExample
GTM_DOCKER_COMMANDS_ALLOWED default is false, set to true to enable docker executor
GTM_DOCKER_ALLOW_PULL allow agent to pull from registry
GTM_DOCKER_DEFAULT_WORKER_IMAGE for running ci tasks, default is zotoio/gtm-worker:latest
GTM_DOCKER_REG_USERNAME username for docker private registry
GTM_DOCKER_REG_SERVER hostname for docker private registry
IAM_ENABLED agent host uses IAM ?
LAUNCHDARKLY_API_TOKEN token for launchdarkly sass executor
GTM_LOGSTASH_HOST optional logstash host for elasticsearch analysis
GTM_LOGSTASH_PORT optional logstash port
GTM_SONAR_HOST_URL sonar host url to connect to
GTM_SONAR_PROJECTNAME_PREFIX prefix if reporting to sonarqube
GTM_SONAR_ANALYSIS_MODE mode for sonar runner, default preview for PRs
GTM_SONAR_SOURCES default source dir is src
GTM_SONAR_JAVA_BINARIES default is target
GTM_SONAR_MODULES comma separated modules
GTM_SONAR_GITHUB_ENDPOINT optional enterprise github api url
GTM_TASK_CONFIG_DEFAULT_URL url to default sample config used when repo is missing .githubTaskManager.json
GTM_TASK_CONFIG_DEFAULT_MESSAGE_PATH path to markdown comment file added to PRs when repo is missing .githubTaskManager.json
GTM_DYNAMO_TABLE_EVENTS DynamoDB table to store event summaries
GTM_DYNAMO_TABLE_AGENTS DynamoDB table to store agent summaries
GTM_AWS_VPC_ID vpc id - only required for ddb endpoints
GTM_BASE_URL Base url used to render links to agent ui - eg elb cname
GTM_WELCOME_MESSAGE_ENABLED If not 'false', send a warning message on unconfigured repository pull requests
GTM_S3_DEPENDENCY_BUCKET aws s3 storage of build dependencies
GTM_AWS_S3_PROXY https_proxy for aws s3
GTM_REPO_BLACKLIST comma separated list of regex to blackist repo names from triggering events
GTM_SLS_EXECUTOR_AWS_STAGE stage override from default calculation of dev/test
GTM_SLS_EXECUTOR_AWS_REGION aws region for lambdas default ap-southeast-2
GTM_SLS_EXECUTOR_AWS_EXECUTION_ROLE docker serverless lambda execution role
GTM_SLS_EXECUTOR_DEPLOY_MODE deploy multiple lambdas 'parallel' (default) or 'sequential'
GTM_SLS_EXECUTOR_SNS_ERROR_TOPIC_ARN sns topic to notify on serverless error
GTM_SLS_EXECUTOR_APIGW_ENDPOINT_TYPE EDGE or REGIONAL or PRIVATE
GTM_SLS_EXECUTOR_APIGW_DOMAIN_SUFFIX reverse proxy domain name that will have apiId added as subdomain. eg. lambda.mysuffix.com will result in [apiId].lambda.mysuffix.com
GTM_SLS_EXECUTOR_HTTP_PROXY proxy passed to serverless executor
GTM_SLS_EXECUTOR_NO_PROXY no_proxy passed to serverless executor
GTM_SLS_EXECUTOR_VPC_ID vpc id for private apigw endpoints
GTM_SLS_EXECUTOR_VPC_SECURITY_GROUP_ID vpc security group id
GTM_SLS_EXECUTOR_VPC_SUBNET_A vpc az subnet
GTM_SLS_EXECUTOR_VPC_SUBNET_B vpc az subnet
GTM_SLS_EXECUTOR_VPC_SUBNET_C vpc az subnet
GTM_SLS_EXECUTOR_AWS_KMS_KEY_ID kms key id for sls env var encryption
GTM_SLS_EXECUTOR_CONFIG_TYPE 'ssm' (aws parameter store) or 'spring' or 'dotenv'
GTM_SLS_EXECUTOR_SPRING_CONFIG_ENDPOINT endpoint url of spring config server eg. http://spring:8888 if GTM_SLS_EXECUTOR_CONFIG_TYPE is 'spring'
GTM_WORKER_SCRIPTS_CLONE for docker executors using https://github.com/zotoio/gtm-worker based image - url of git repo to overlay on workspace eg. https://github.com/zotoio/gtm-worker-scripts.git
GTM_WORKER_SCRIPTS_PATH directory within scripts clone repo to overlay

important: values of env vars prefixed with GTM_CRYPT_* must be created via npm run sls-encrypt [name] [value]

Configure and deploy

  • run: npm run sls-deploy - note that this will create aws re$ources..
  • capture the hook url output in console and add to github repo pull request conf
  • run: npm run sls-logs-hook or npm run sls-logs-results to tail the logs
  • create a .githubTaskManager.json in your repo per https://github.com/zotoio/github-task-manager/wiki/Creating-a-Task-Configuration
  • start an agent locally using npm run build && npm start agent (or use docker/k8s)
  • create a pull request and confirm the hook is being hit and agent processes event

Docker and Kubernetes agents

You can run the latest image from docker hub: https://hub.docker.com/r/zotoio/github-task-manager

npm run docker-hub-run

..or run using the local checkout and tail logs:

npm run docker-local-bounce

..or if you have a k8s cluster and kubectl configured:

npm run k8s-apply
npm run k8s-delete

note that these k8s npm script inject vars from .env into the manifest

k8s

a starting point k8s manifest is in ./k8s/k8s-gtm-agent.yml

Agent Configuration

Running the Agent

The agent uses environment variables to configure itself as well as any executors running within it. The below environment variables are required for basic operation of the GTM Agent.

TODO: Provide Variables

Agent Homepage

The GTM Agent provides an information page summarising the ongoing operation of the agent. The page is available on port 9091 by default.

Plugins

Task executors for Jenkins, Teamcity, Travis, Http, Docker are in progress. Custom task executors can be added by adding this project as a dependency, and registering new Executors and EventHandlers. Please see https://github.com/zotoio/gtm-agent for an example that you can fork and modify as required while still using this project as the core.

  • Executors contain the logic to run tasks against a given system type, and format the results.
  • EventHandlers are used to map Github events to specific functionality such as pull requests.

Contributing

Fork this repository and work on your enhancements, then send a pull request. If you build custom plugins that may be useful to others in your forked gtm-agent, please let us know and may be able to assist wwith backporting to this project.

Use commitizen for conventional commit messages via git cz instead of git commit.
To setup if not already installed:

npm install -g commitizen
npm install -g cz-conventional-changelog
echo '{ "path": "cz-conventional-changelog" }' > ~/.czrc

...or you can just use npm run commit which will use local commitizen install.

github-task-manager's People

Contributors

david-jonathan avatar greenkeeper[bot] avatar greenkeeperio-bot avatar neko-design avatar wyvern8 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

github-task-manager's Issues

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


The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment.


Good luck with your project ✨

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

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

Version 1.31.0 of serverless was just published.

Branch Build failing 🚨
Dependency serverless
Current Version 1.30.3
Type devDependency

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

serverless 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 1.31.0 (11.09.2018)
Commits

The new version differs by 42 commits.

  • 47901ae Merge pull request #5287 from serverless/release-v-1-31-0
  • a0ba3df Releasing v1.31.0
  • f53f047 Merge pull request #5258 from pinkerton/master
  • 7616fb2 Fix serverless-cloudflare-workers version
  • e2050f9 Fix serverless-cloudflare-workers version in enterprise
  • 8c5511c Update PoP number
  • 1e37c2c Add docs link to menu
  • 4bbdacd Change path from cloudflare-workers to cloudflare
  • 30db8e9 Add to providers page
  • 0abdf19 Add image headers to docs
  • c94db19 Add links to Workers page
  • 0ec216a Add note about updated route handling
  • c4f358c Update version in docs
  • 9f1c334 Merge pull request #5276 from andriyor/master
  • 87a09d3 Update instructions a bit

There are 42 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 rimraf is breaking the build 🚨

The devDependency rimraf was updated from 2.6.2 to 2.6.3.

🚨 View failing branch.

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

rimraf 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 6 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 https-proxy-agent is breaking the build 🚨

The dependency https-proxy-agent was updated from 2.2.1 to 2.2.2.

🚨 View failing branch.

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

https-proxy-agent 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
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for 2.2.2

Patches

  • Remove package-lock.json: c881009
  • Ignore test directory, History.md and .travis.yml when creating npm package. Fixes #42: #45
  • Update agent-base to v4.2: #50
  • Add TypeScript type definitions: #66
  • Feat(typescript): Allow input to be options or string: #68
  • Update agent-base to v4.3: #69

Credits

Huge thanks to @marco-c, @tareqhs, @ianhowe76, and @BYK for helping!

Commits

The new version differs by 7 commits.

  • e145714 2.2.2
  • 4a7ea92 Update agent-base to v4.3 (#69)
  • 13917f6 feat(typescript): Allow input to be options or string (#68)
  • c5c4ffc Add TypeScript type definitions (#66)
  • 11bc347 Update agent-base to v4.2 (#50)
  • 056c843 Ignore test directory, History.md and .travis.yml when creating npm package. Fixes #42 (#45)
  • c881009 Remove package-lock.json

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.15 of semantic-release was just published.

Branch Build failing 🚨
Dependency semantic-release
Current Version 15.9.14
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.15

15.9.15 (2018-09-11)

Bug Fixes

  • package: update debug to version 4.0.0 (7b8cd99)
Commits

The new version differs by 1 commits.

  • 7b8cd99 fix(package): update debug 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 🌴

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

The devDependency supertest 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.

supertest 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 for v3.4.0
  • PR-532 - Packages updated, pipeline more explicit, documentation updated (thanks @rimiti)
  • PR-517 - Documentation updated (thanks @oprogramador)
  • PR-513 - Use more robust Array instance check (thanks @rubendg)
Commits

The new version differs by 14 commits.

  • 5640ac9 3.4.0
  • 60f8a9e Merge pull request #532 from visionmedia/v3.4.0
  • 43bfae1 doc(History.md) changelog updated
  • fc1568d doc(README.md) cookie example added
  • 3192d96 chore(package-lock.json) file updated
  • b3d271f chore(package.json) blocks reorganized, nock removed
  • aeae0f3 chore(.travis.yml) pipeline more explicit
  • 53feddc chore(test/supertest.js) obscure test removed
  • 50c59d6 Merge pull request #519 from oprogramador/patch-3
  • 6ca3897 Merge pull request #517 from oprogramador/patch-2
  • 0146d81 auth info in README
  • d853b37 fix typo in README
  • 8158979 Merge pull request #513 from rubendg/use-isarray
  • 550613b Use more robust Array instance check

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

The devDependency node-sass was updated from 4.9.3 to 4.9.4.

🚨 View failing branch.

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

node-sass 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 for v4.9.4

Dependencies

Supported Environments

OS Architecture Node
Windows x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
OSX x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
Linux* x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^
Alpine Linux x64 4, 6, 7, 8, 9, 10
FreeBSD 10+ amd64 4, 6, 8, 9, 10
FreeBSD 10+ i386 4, 6, 8, 9, 10

*Linux support refers to Ubuntu, Debian, and CentOS 5+
** Node 8 and 9 are not supported on CentOS 5
^ Only available on x64

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 🌴

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


The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment.


Good luck with your project ✨

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

An in-range update of serverless-offline is breaking the build 🚨

The devDependency serverless-offline was updated from 3.25.11 to 3.25.12.

🚨 View failing branch.

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

serverless-offline 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 15 commits.

  • ace47fe v3.25.12
  • 3f59c9b fix #479
  • 719ddde Merge branch 'Enase-master'
  • 590484a master origin merge + package lock updated
  • dcdd827 Merge remote-tracking branch 'source/master'
  • 99ff5ff package lock updated
  • 8a215a5 package lock updated
  • ec94136 Merge remote-tracking branch 'source/master'
  • 14f7f40 Merge remote-tracking branch 'source/master'
  • 694575b package lock updated
  • c68053a Merge remote-tracking branch 'source/master'
  • 642862e Merge remote-tracking branch 'source/master'
  • b42c579 Merge remote-tracking branch 'source/master'
  • 33fc0d5 Merge remote-tracking branch 'source/master'
  • 84fadf0 babel ver 7 support added

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 🌴

Add 'Merge' executor

Allow a chain of tasks to trigger a github merge to a given branch on successful execution.

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


The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment.


Good luck with your project ✨

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

An in-range update of source-map-support is breaking the build 🚨

The dependency source-map-support was updated from 0.5.11 to 0.5.12.

🚨 View failing branch.

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

source-map-support 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
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 5 commits.

  • 208d1df 0.5.12
  • 2afd513 Update built files
  • f2a0fbf Merge pull request #237 from legraphista/fix/195
  • 2515a8f Add: test for console.trace
  • 4da4100 Fix: formatting in prepareStackTrace when error isn't of instance Error

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

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

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

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

The dependency ldclient-node was updated from 5.4.2 to 5.5.0.

🚨 View failing branch.

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

ldclient-node 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
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for 5.5.0

[5.5.0] - 2018-10-08

Added:

  • The allFlagsState method now accepts a new option, detailsOnlyForTrackedFlags, which reduces the size of the JSON representation of the flag state by omitting some metadata. Specifically, it omits any data that is normally used for generating detailed evaluation events if a flag does not have event tracking or debugging turned on.

Fixed:

  • Fixed an error that would occur in two cases where the client should return a default value: evaluating a flag when the client and the feature store are not yet initialized, and evaluating with no flag key. (Thanks, SharkofMirkwood!)
  • JSON data from allFlagsState is now slightly smaller even if you do not use the new option described above, because it completely omits the flag property for event tracking unless that property is true.
Commits

The new version differs by 3 commits.

  • 6a47a4a Update Changelog for release of version 5.5.0
  • d273e60 prepare 5.5.0 release (#124)
  • a4dc34f Fix uncaught 'variationErr is not defined' exception (#123)

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

The dependency webpack was updated from 4.18.0 to 4.18.1.

🚨 View failing branch.

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

webpack 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
  • ❌ 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.

  • c51a1ba 4.18.1
  • c79c1de Merge pull request #8018 from webpack/ci/azure-windows
  • 37046a7 Add windows to azure
  • 814b85b Merge pull request #8012 from webpack/ci/azure
  • 474a9ac Add simple azure pipeline
  • 7b3a297 Merge pull request #8015 from webpack/deps/upgrade-tapable
  • 35015dd Upgrade tapable version

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

The dependency systemjs was updated from 0.21.4 to 0.21.5.

🚨 View failing branch.

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

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

Release Notes for SystemJS 0.21.5
  • Fixes an IE11 compatibility bug (#1845)
Commits

The new version differs by 4 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 serverless-kms-secrets is breaking the build 🚨

The dependency serverless-kms-secrets was updated from 1.0.3 to 1.0.4.

🚨 View failing branch.

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

serverless-kms-secrets 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
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

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

The dependency launchdarkly-nodeutils was updated from 3.5.6 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.

launchdarkly-nodeutils 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
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v3.6.0

3.6.0 (2018-10-19)

Features

  • members: Invite User Functionality (35e7da0)
Commits

The new version differs by 2 commits.

  • 35e7da0 feat(members): Invite User Functionality
  • e2ada34 Update README.md

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

The dependency lodash was updated from 4.17.10 to 4.17.11.

🚨 View failing branch.

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

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

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 🌴

Standardize proxy usage

Currently there are proxy settings coming from env vars:

  • AWS_PROXY
  • HTTP_PROXY
  • https_proxy
  • GTM_GITHUB_PROXY

In addition there is a combination of at least three proxy agent modules in use:

  • https
  • proxy-agent
  • https-proxy-agent

..and the logic to drive usage proxy varies between checking:

  • IAM_ENABLED env var
  • GTM_DYNAMO_VPCE env var
  • relevant proxy env var existence.

This should be updated so that:

  • GTM_AWS_PROXY is used for aws sdk calls if it is set
  • GTM_GITHUB_PROXY is used for octokit if it is set
  • A single proxy agent module is selected and used.
  • proxy usage is driven by relevant env var existence

Ideally, all AWS api calls should be moved into util classes to centralize, and as an aside, it looks like this env var is not in use. GTM_AWS_VPC_ID

thoughts @Neko-Design ?

An in-range update of serverless-dotenv-plugin is breaking the build 🚨

The devDependency serverless-dotenv-plugin was updated from 1.2.0 to 1.2.1.

🚨 View failing branch.

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

serverless-dotenv-plugin 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 2 commits.

  • 887a8e3 Path cannot be set from stage vars
  • af056fe Added example app

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

The dependency elasticsearch was updated from 15.1.1 to 15.2.0.

🚨 View failing branch.

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

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

Commits

The new version differs by 9 commits.

  • 29c3381 version 15.2.0
  • 11b0d89 [apis] regenerate
  • 2ee5166 add 6.4 and 6.5 branch support, 6.4 is the new default
  • 2b82644 [apis] regenerate
  • 0454df9 remove dead percolator link (#716)
  • 559ed04 Fix typo: "Integrer -> Integer" (#715)
  • 84bbdb1 [apis] regenerate
  • bc422cc [package] remove accidental duplicate branch name
  • c01f57d [lodash] fix missed _.flattenDeep() upgrade

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

The dependency body-parser was updated from 1.18.3 to 1.19.0.

🚨 View failing branch.

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

body-parser 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
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 44 commits.

There are 44 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 express-sse is breaking the build 🚨

The dependency express-sse was updated from 0.5.0 to 0.5.1.

🚨 View failing branch.

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

express-sse 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
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 4 commits.

  • 04e0114 Bring back v4 and v5 testing
  • ef6a936 Older node support fix
  • 9c8741b Security fix + HTTP/2, version bump
  • 2783175 Test coverage moved to codecov

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

The dependency dockerode was updated from 2.5.6 to 2.5.7.

🚨 View failing branch.

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

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

Commits

The new version differs by 6 commits.

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

The dependency require-dir was updated from 1.0.0 to 1.1.0.

🚨 View failing branch.

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

require-dir 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
  • ❌ 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.

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 app-root-path is breaking the build 🚨

The dependency app-root-path was updated from 2.1.0 to 2.2.0.

🚨 View failing branch.

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

app-root-path 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
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for 2.2.0
  • Added support for Yarn Plug'n'Play
  • Adjusted browser-shim to address webpack warnings
  • Bumped minimum Node version to 6
Commits

The new version differs by 7 commits.

  • 59352ec docs: Documented 2.2.0 release
  • ce58fd1 feat: Hopefully resolve dynamic webpack warnings in browser
  • 6bcd128 chore: Bumped version in package.json
  • 84eb218 chore: Dropped Node 12
  • d88aca1 chore: Adjusted supported Node versions
  • 8ccfb54 docs: 2.1.0
  • b20b622 feat: Yarn Plug'n'Play support

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

The dependency proxy-agent was updated from 3.0.3 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.

proxy-agent 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
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for 3.1.0

Minor Changes

  • Add TypeScript types: #34

Patches

  • Remove package-lock.json file: 063ad8f

Credits

Huge thanks to @jbarrus for helping!

Commits

The new version differs by 3 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 express is breaking the build 🚨

The dependency express was updated from 4.16.4 to 4.17.0.

🚨 View failing branch.

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

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

Release Notes for 4.17.0
Commits

The new version differs by 53 commits.

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

Update Jenkins and Teamcity executor option structure.

@David-Jonathan @Neko-Design
Let's make the Jenkins and TeamCity executors take 'jobName' and 'parameters' to be more generic as discussed - eg:

{
    "executor": "Jenkins",
    "context": "run e2e tests",
    "options": {
        "jobName": "EXECUTE_AUTOMATED_TESTS",
        "parameters": {
            "TAGS": "['@project-tag', '@##GHREPONAME']",
            "ENVIRONMENT": "test1"
        }
    }
}

..and update the wiki page with token info.
https://github.com/wyvern8/github-task-manager/wiki/Structure-of-.githubTaskManager.json

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

The devDependency dotenv was updated from 6.0.0 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.

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

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

The dependency xml2js was updated from 0.4.19 to 0.4.20.

🚨 View failing branch.

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

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

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-plugin-source-map-support is breaking the build 🚨

The dependency babel-plugin-source-map-support was updated from 2.0.1 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.

babel-plugin-source-map-support 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
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 16 commits.

  • 851ae06 v2.1.0
  • e664c34 update dependencies (closes #7, closes #13, closes #14)
  • 0b33430 Bump eslint from 5.5.0 to 5.12.0
  • 6935c47 Bump @babel/preset-env from 7.0.0 to 7.2.3
  • 32042f1 Bump eslint-plugin-promise from 4.0.0 to 4.0.1
  • 40a1b6a Bump lodash from 4.17.10 to 4.17.11
  • 4237f86 update babel: 7.0.0-beta.40 -> 7.0.0
  • 35a8acb try to route around a downstream issue which breaks upgrades on Node v10
  • 6e52bff stop AVA searching other directories for tests (!)
  • 2a6bcd5 changelog: snip superfluous timestamps
  • b77b9c6 add Node v10 to the Travis tests
  • c57bb7c rm license badge
  • dbff972 remove unsupported Node versions from the Travis matrix
  • 6d9c9f6 tweak license blurb
  • 7a8a512 include license

There are 16 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 uuid is breaking the build 🚨

The dependency uuid was updated from 3.3.2 to 3.3.3.

🚨 View failing branch.

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

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

Commits

The new version differs by 3 commits.

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

The dependency nunjucks was updated from 3.1.3 to 3.1.4.

🚨 View failing branch.

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

nunjucks 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
  • ❌ 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.

  • 11262e5 Release v3.1.4
  • bcd45fc Merge pull request #1165 from stigkj/master
  • 40480f0 Fix engine version for Node v11.1.0
  • 3512ca6 Merge pull request #1161 from jonathanchu/master
  • 9dc07dc Fix dependency version for node v11.0.0
  • 39bb716 Merge pull request #1126 from TheDancingCode/issue-126
  • 4d4dc40 Escape unicode newlines when compiling

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

The dependency node-static was updated from 0.7.10 to 0.7.11.

🚨 View failing branch.

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

node-static 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
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 3 commits.

  • e59fe21 Bump version to 0.7.11
  • e994d29 Merge pull request #191 from jshthornton/master
  • 8a5294a The index file should be served up with 200

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


The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment.


Good luck with your project ✨

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

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

The dependency highlight.js was updated from 9.14.2 to 9.15.1.

🚨 View failing branch.

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

highlight.js 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
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

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 request-promise-native is breaking the build 🚨

The dependency request-promise-native was updated from 1.0.5 to 1.0.6.

🚨 View failing branch.

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

request-promise-native 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
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 10 commits.

  • 7ad655a Version 1.0.6 (now really)
  • 1240b80 fix: updated indirect lodash dependency to fix security vulnerability
  • 80947a1 Version 1.0.6
  • ad529a3 chore: fix ci build for node v8+
  • c2c54c4 Merge pull request #33 from jasonmit/u/jasonmit/fix-node-6
  • 67f7ed2 Merge branch 'master' into u/jasonmit/fix-node-6
  • 4633d4c fix: breaking change in tough-cookie v3
  • 14aa6ee chore: added node 8 and 10 to ci build
  • 9cfcaaa Update package.json
  • 049152b fix: target tough-cookie 2.x to preserve node 6 support

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


The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment.


Good luck with your project ✨

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

An in-range update of cross-env is breaking the build 🚨

The devDependency cross-env was updated from 5.2.0 to 5.2.1.

🚨 View failing branch.

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

cross-env 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 for v5.2.1

5.2.1 (2019-08-31)

Bug Fixes

Commits

The new version differs by 6 commits.

  • a75fd0e fix: remove is-windows dependency (#207)
  • 4889923 docs: add note for windows issues
  • 2b36bb3 docs: add Jason-Cooke as a contributor (#201)
  • 41ab3b0 docs: Fix typo (#200)
  • 553705c docs(README): list @naholyr/cross-env in Other Solutions section (#189)
  • 5d0f19f docs: remove codesponsor (#186)

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

The devDependency serverless-webpack was updated from 5.2.0 to 5.3.0.

🚨 View failing branch.

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

serverless-webpack 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 for 5.3.0

Release Notes

  • Restore compatibility with TypeScript #449 #465
  • Allow glob for excludeFiles #471
  • Support Webpack 5 #472
  • Use colored output depending on tty #480
  • Allow to keep webpack folder #453 #467
  • Add ability to exclude files from handler lookup #433
  • Documentation fixes #429

Special thanks to @hassankhan and @designfrontier for the help to get this release out πŸ₯‡

Commits

The new version differs by 43 commits.

  • 4ea395b Added missed release notes
  • 58a2d0f Merge pull request #493 from serverless-heaven/release-5.3.0
  • 2a5b05f Prepared release of 5.3.0
  • 9550751 Merge pull request #472 from neilime/patch-2
  • a6d536c Improve code of getExternalModules function
  • 29f4fc4 Improve code coverage
  • 1bb32c7 Add new tests
  • 8e738b7 Add ne tests
  • d3221ad Merge branch 'master' into patch-2
  • 7983e44 Fix lint issues
  • 961ad25 Merge pull request #471 from designfrontier/remove-warning
  • cb3c562 Merge branch 'master' into remove-warning
  • d3fb131 Merge branch 'master' into patch-2
  • 3240cce Merge pull request #429 from grgur/patch-1
  • cd4bcdb Merge pull request #489 from Zn4rK/fix-no-stopping-the-watcher

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

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.