This version is covered by your current version range and after updating it in your project the build failed.
As mocha is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β **bitHound - Code** 2 failing files. [Details](https://www.bithound.io/github/binoculars/aws-cloudformation-cognito-identity-pool/243de4eff0fc3a7cea4246900a80b2fd1e2ce3d3/files#filter-failing-file),- β **bitHound - Dependencies** 1 failing dependency. [Details](https://www.bithound.io/github/binoculars/aws-cloudformation-cognito-identity-pool/243de4eff0fc3a7cea4246900a80b2fd1e2ce3d3/dependencies/npm#filter-failing-dep),- β **ci/circleci** Your tests passed on CircleCI! [Details](https://circleci.com/gh/binoculars/aws-cloudformation-cognito-identity-pool/22?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Release Notescoverave
Thanks to all our contributors, maintainers, sponsors, and users! β€οΈ
As highlights:
We've got coverage now!
Testing is looking less flaky \o/.
No more nitpicking about "mocha.js" build on PRs.
π Enhancements
#2659: Adds support for loading reporter from an absolute or relative path (@sul4bh)
#2769: Support --inspect-brk on command-line (@igwejk)
π Fixes
#2662: Replace unicode chars w/ hex codes in HTML reporter (@rotemdan)
Hi, I'm getting 'Missing region in config' when running gulp. The region is properly configured in my ~/.aws/config file but it seems that is not being picked up.
I had to explicitly set the region before creating any AWS resource to make it work.