express-skeleton's People
express-skeleton's Issues
An in-range update of grunt is breaking the build π¨
The devDependency grunt 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.
grunt is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Commits
The new version differs by 5 commits.
8fcbed1
v1.0.4 (#1668)
0b13970
Update js-yaml to address https://npmjs.com/advisories/788 (#1667)
7db6cf7
Use SOURCE_DATE_EPOCH to render dates in template. (#1596)
a2d6d80
Revert "Indicate in package.json that Node.js 4 or newer is required (#1643)" (#1644)
773b7e7
Indicate in package.json that Node.js 4 or newer is required (#1643)
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 chromedriver is breaking the build π¨
Version 2.25.3 of chromedriver just got published.
Branch | Build failing π¨ |
---|---|
Dependency | chromedriver |
Current Version | 2.25.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As chromedriver is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of node-cache is breaking the build π¨
Version 4.1.1 of node-cache just got published.
Branch | Build failing π¨ |
---|---|
Dependency | node-cache |
Current Version | 4.1.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As node-cache is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
fix internal check interval- fix internal check interval for node < 0.10.25, thats the default node for ubuntu 14.04.
Thanks to Jimmy Hwang for for the pull #78; - added more docker tests
Commits
The new version differs by 10 commits .
37ac785
bump version
f3fe4fa
optimized docker tests and added different environments
0b4d426
fixed #78
fec7842
removed issue #78 test and added a test to the general tests
4b4f227
added docker test for issue #78
5db7271
fixed gitter chat link
412cc28
fix tests in appveyor, fix tests only executing a single test suite
d664938
update clone note in description, add clone tests for a function and a regex
d525ae9
add code coverage via coveralls.io
bb397e0
upgrade clone to v2.x, update tests for clones
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of browser-sync is breaking the build π¨
The devDependency browser-sync was updated from 2.26.3
to 2.26.4
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
browser-sync is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Commits
The new version differs by 6 commits.
47a4d1b
v2.26.4
05a58db
deps: fixes #1677 #1671 #1659 #1648
35035df
deps: removed nodemon since it includes flat-stream (security)
1b2eab5
Merge pull request #1634 from mxschmitt/patch-1
e35e5dc
fix(ui): updated dead links and moved to https
85c4ba7
examples: server + proxy
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 pm2 is breaking the build π¨
Version 2.2.1 of pm2 just got published.
Branch | Build failing π¨ |
---|---|
Dependency | pm2 |
Current Version | 2.2.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As pm2 is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 2 commits .
55f1e74
[email protected] [startup refactor]
d9f70fe
[email protected] [startup refactor]
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of grunt-webdriver is breaking the build π¨
Version 2.0.3 of grunt-webdriver just got published.
Branch | Build failing π¨ |
---|---|
Dependency | grunt-webdriver |
Current Version | 2.0.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As grunt-webdriver is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 5 commits .
7c452ff
v2.0.3
d000150
Update contributors
41b3823
updated changelog
211a394
Merge pull request #84 from alippai/patch-1
0fd923a
Update grunt peerDependency
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of express-session is breaking the build π¨
Version 1.14.2 of express-session just got published.
Branch | Build failing π¨ |
---|---|
Dependency | express-session |
Current Version | 1.14.1 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As express-session is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
1.14.2- deps: [email protected]
- Fix deprecation warning in Node.js 7.x
- deps: uid-safe@~2.1.3
- deps: [email protected]
Commits
The new version differs by 17 commits .
-
1a61416
1.14.2
-
087a0a4
build: support Node.js 7.x
-
dcc6241
deps: uid-safe@~2.1.3
-
69f07ec
deps: [email protected]
-
1c6ea44
build: [email protected]
-
2667028
docs: add callback to method signatures that take one
-
b7c6974
docs: flatten cookie options into option header level
-
ddffd58
docs: add connect-ml to the list of session stores
-
30a4d88
docs: add connect-datacache to the list of session stores
-
fba7be4
docs: add express-etcd to the list of session stores
-
12b0502
docs: add express-sessions to list of session stores
-
7ede224
build: [email protected]
-
708a70b
build: [email protected]
-
8e57b21
docs: add hazelcast-store to list of session stores
-
81e6d09
docs: add documentdb-session to list of session stores
There are 17 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of express is breaking the build π¨
Version 4.14.1 of express just got published.
Branch | Build failing π¨ |
---|---|
Dependency | express |
Current Version | 4.14.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As express is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
4.14.1- deps: [email protected]
- deps: [email protected]
- Fix exception when
err.headers
is not an object - deps: statuses@~1.3.1
- perf: hoist regular expressions
- perf: remove duplicate validation path
- Fix exception when
- deps: proxy-addr@~1.1.3
- deps: [email protected]
- deps: [email protected]
- deps: http-errors@~1.5.1
- deps: [email protected]
- deps: statuses@~1.3.1
- deps: serve-static@~1.11.2
- deps: [email protected]
- deps: type-is@~1.6.14
- deps: mime-types@~2.1.13
Commits
The new version differs by 24 commits .
0437c51
4.14.1
1f70b76
build: [email protected]
0b39fa2
build: [email protected]
0d6c64f
deps: type-is@~1.6.14
c238aca
examples: remove big-view example
6b506d8
examples: fix mvc example to ignore files in controllers dir
dc48f27
deps: update example dependencies
8e14e06
deps: serve-static@~1.11.2
572657e
deps: [email protected]
cfae537
deps: [email protected]
a3d6353
deps: proxy-addr@~1.1.3
a2e323a
build: [email protected]
e73913b
build: [email protected]
ddc93aa
deps: [email protected]
6723b44
tests: add test for res.sendFile "cacheContol" option
There are 24 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of session-file-store is breaking the build π¨
The dependency session-file-store was updated from 1.2.0
to 1.3.0
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
session-file-store 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 failed (Details).
Commits
The new version differs by 7 commits.
c57ec71
increase minimum supported node version.
f08bd65
revert write-file-atomic version.
478b2b3
fixes security vulnerabilities in dependencies.
8aeafd1
Merge pull request #71 from mojoblanco/patch-1
a74c8e4
Fix typo in Readme file
b2f37a8
Merge pull request #68 from ericandrewlewis/patch-1
e81c93f
Add fileStoreOptions to usage example
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 browser-sync is breaking the build π¨
Version 2.18.0 of browser-sync just got published.
Branch | Build failing π¨ |
---|---|
Dependency | browser-sync |
Current Version | 2.17.6 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As browser-sync is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 7 commits .
-
81c3f74
2.18.0
-
09c938b
docs: Since param on httpModule option
-
67d58ef
Merge pull request #1250 from BrowserSync/AddSupportForOverridingHttpModule
-
8ba178e
feat(httpModule): Allow custom HTTP module to be given in options
-
5136fd5
Merge branch 'AddSupportForOverridingHttpModule' of github.com:itslenny/browser-sync into AddSupportForOverridingHttpModule
-
4af1a4d
test: skip tunnel e2e (flaky ci) & use url directly in supertest requests to SSL endpoints
-
558c6da
Allow users to override default httpModule
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of session-file-store is breaking the build π¨
The dependency session-file-store was updated from 1.3.1
to 1.4.0
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
session-file-store 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 failed (Details).
Commits
The new version differs by 7 commits.
6b3fd88
Upgraded to 1.4.0 version.
f35dd91
Merge pull request #84 from runeh/patch-1
d4b183b
Avoid setInterval keeping node process alive
a53f150
Merge pull request #83 from jas-/docs
e7cdc41
docs: Updated readme to reflect changes in crypto functionality
0c42c6c
Merge pull request #81 from jas-/crypto
1d1dc0b
crypto: Replaced all crypto API calls to use kruptein module
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
An in-range update of express-session is breaking the build π¨
The dependency express-session was updated from 1.15.6
to 1.16.0
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
express-session 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 failed (Details).
Release Notes for v1.16.0
- Catch invalid
cookie.maxAge
value earlier - Deprecate setting
cookie.maxAge
to aDate
object - Fix issue where
resave: false
may not save altered sessions - Remove
utils-merge
dependency - Use
safe-buffer
for improved Buffer API - Use
Set-Cookie
as cookie header name for compatibility - deps: depd@~2.0.0
- Replace internal
eval
usage withFunction
constructor - Use instance methods on
process
to check for listeners - perf: remove argument reassignment
- Replace internal
- deps: on-headers@~1.0.2
- Fix
res.writeHead
patch missing return value
- Fix
Commits
The new version differs by 86 commits.
b1f0984
1.16.0
e77cbfa
build: add version script for npm version releases
9495367
docs: update badge for level-session-store store
6e514a4
build: [email protected]
dc5262a
docs: add connect-arango to the list of session stores
e926b88
build: [email protected]
a7cf57f
build: [email protected]
03aa560
build: [email protected]
cc5c83a
lint: ensure strict equality checks
ed8a50f
build: [email protected]
3e0d548
tests: move some code into support/
2f0759c
build: [email protected]
4cbb93f
build: simplify & speed up logic in Travis CI build steps
eda02b2
deps: on-headers@~1.0.2
3602d29
build: [email protected]
There are 86 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 grunt-contrib-watch is breaking the build π¨
Version 1.0.1 of grunt-contrib-watch was just published.
Branch | Build failing π¨ |
---|---|
Dependency | grunt-contrib-watch |
Current Version | 1.0.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
grunt-contrib-watch is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 16 commits.
6ec71e9
v1.0.1
7d20933
Update copyright year
e3d19df
Update ci configs
d117574
Updating ci configs
99410a7
README.md: Fixed typos (#536)
7f8cf80
Add local grunt-cli
ab6771e
Drop back to [email protected] until the bad test helper can be sorted
2e2daa5
Update to [email protected]
3d7fa3a
Avoid timing issue in tests because of the bad test helper
0130a16
Merge pull request #500 from gruntjs/deps
5289845
Update devDependencies.
fd3ed7a
Lint tweaks.
e42386a
Merge pull request #501 from cepko33/master
8c93077
Updated lodash and changed outdated 'contains' to 'includes'
986b8a9
Update CHANGELOG.
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 debug is breaking the build π¨
Version 2.3.0 of debug just got published.
Branch | Build failing π¨ |
---|---|
Dependency | debug |
Current Version | 2.2.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As debug is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 37 commits .
-
8e5a6b3
2.3.0
-
d887d93
updated contributors
-
820f351
Merge pull request #215 from gorangajic/add-ms-as-last-param
-
d188464
Merge pull request #317 from visionmedia/feature/yarnIntegration
-
341e584
added Yarn integration to Makefile
-
b39265f
renamed History.md to CHANGELOG.md
-
5b1e1da
added yarn lockfile for yarn support
-
061b4a5
Merge pull request #274 from sdaitzman/patch-1
-
2b78d42
hyphenates license years
-
dafc16e
move ms to the last place
-
b02b753
Merge pull request #315 from DevSide/patch-3
-
e8fe71b
Bump ms 0.7.2
-
0682a14
Merge pull request #250 from zacronos/master
-
a4e36a8
Readme: fix USE_COLORS to DEBUG_COLORS
-
4e61d2a
Merge pull request #269 from mlucool/patch-1
There are 37 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of nodemon is breaking the build π¨
The devDependency nodemon was updated from 1.18.10
to 1.18.11
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
nodemon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Commits
The new version differs by 1 commits.
aa41ab2
fix: hard bump of [email protected]
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 π¨
Version 1.16.0 of body-parser just got published.
Branch | Build failing π¨ |
---|---|
Dependency | body-parser |
Current Version | 1.15.2 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As body-parser is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
1.16.0- deps: [email protected]
- Allow colors in workers
- Deprecated
DEBUG_FD
environment variable - Fix error when running under React Native
- Use same color for same namespace
- deps: [email protected]
- deps: http-errors@~1.5.1
- deps: [email protected]
- deps: [email protected]
- deps: statuses@'>= 1.3.1 < 2'
- deps: [email protected]
- Added encoding MS-31J
- Added encoding MS-932
- Added encoding MS-936
- Added encoding MS-949
- Added encoding MS-950
- Fix GBK/GB18030 handling of Euro character
- deps: [email protected]
- Fix array parsing from skipping empty values
- Fix compacting nested arrays
- deps: raw-body@~2.2.0
- deps: [email protected]
- deps: type-is@~1.6.14
- deps: mime-types@~2.1.13
Commits
The new version differs by 20 commits .
c5a73d5
1.16.0
9744dda
deps: [email protected]
7807757
deps: [email protected]
0e44768
lint: use standard style in the README
14952be
build: [email protected]
502c940
build: support Node.js 7.x
00bb95c
build: [email protected]
4201584
deps: [email protected]
8946435
deps: raw-body@~2.2.0
2c5d9db
deps: [email protected]
eaf2e80
deps: type-is@~1.6.14
5e51cce
deps: http-errors@~1.5.1
c064ac1
build: [email protected]
d0cf951
build: [email protected]
851f6a6
build: [email protected]
There are 20 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of tenon-node is breaking the build π¨
Version 0.4.1 of tenon-node was just published.
Branch | Build failing π¨ |
---|---|
Dependency | tenon-node |
Current Version | 0.4.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
tenon-node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 15 commits.
a66db04
update travis config to fix auto-deployments to npm
a46a032
Rebuild package-lock.json
8cc8649
Fix link to Tenon's docs.
129ab84
Update devDependencies badge
07ef1b0
Fix eslint issues
7db6103
Update supported node and npm versions
19bfac9
Update devDependencies
7161032
Merge pull request #9 from naterkane/readme-typo
185bc63
0.4.1
468d729
fix typo in example in readme
d180e91
Merge pull request #2 from poorgeek/master
e274887
Configure travis to release to npm when tagged
ffd9d05
Merge pull request #8 from NickHeiner/patch-1
a5ed65f
install npmv3 on travis so that some dependencies will work
b5ff4c4
Small grammar fixes.
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 browser-sync is breaking the build π¨
Version 2.18.3 of browser-sync just got published.
Branch | Build failing π¨ |
---|---|
Dependency | browser-sync |
Current Version | 2.18.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As browser-sync is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 8 commits .
ed71efc
2.18.3
069927a
fix(ui): bump ui to remove cache headers to fix #1152
8515664
deps: bump yargs ua-parser-js localtunnel http-proxy fs-extra chokidar
75ad9b7
Merge pull request #1252 from BrowserSync/http2-opts
0c555bd
fix(https): pass ALL https options given by the user to .createServer() - fixes #956
f2f9722
deps: bump socket.io = 1.6.0
78c519e
Support pfx passphrase
fbd85de
Support pfx passphrase
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of pm2 is breaking the build π¨
Version 2.1.4 of pm2 just got published.
Branch | Build failing π¨ |
---|---|
Dependency | pm2 |
Current Version | 2.1.3 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As pm2 is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 9 commits .
-
24168c9
(minor) upgrade some deps + PM2_CONCUTTENT_ACTIONS to default for test
-
91a5eae
#2486 add --web option to pm2-docker to expose web process api
-
1579079
[email protected]
-
51edbc5
(CHANGELOG)
-
433f213
(test) extra test for wait-ready
-
f6be6f3
#2492 drop legacy if statement in worker
-
8e6cde6
#2488 CLI description
-
672268c
#2485 try/catch process.kill
-
382f5ce
dont use signal to verify daemon has been killed under windows (#2484)
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of 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 failed (Details).
Release Notes for 4.17.0
- Add
express.raw
to parse bodies intoBuffer
- Add
express.text
to parse bodies into string - Improve error message for non-strings to
res.sendFile
- Improve error message for
null
/undefined
tores.status
- Support multiple hosts in
X-Forwarded-Host
- deps: accepts@~1.3.7
- deps: [email protected]
- Add encoding MIK
- Add petabyte (
pb
) support - Fix parsing array brackets after index
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- deps: type-is@~1.6.17
- deps: [email protected]
- deps: [email protected]
- Add
SameSite=None
support
- Add
- deps: finalhandler@~1.1.2
- Set stricter
Content-Security-Policy
header - deps: parseurl@~1.3.3
- deps: statuses@~1.5.0
- Set stricter
- deps: parseurl@~1.3.3
- deps: proxy-addr@~2.0.5
- deps: [email protected]
- deps: [email protected]
- Fix parsing array brackets after index
- deps: range-parser@~1.2.1
- deps: [email protected]
- Set stricter CSP header in redirect & error responses
- deps: http-errors@~1.7.2
- deps: [email protected]
- deps: [email protected]
- deps: range-parser@~1.2.1
- deps: statuses@~1.5.0
- perf: remove redundant
path.normalize
call
- deps: [email protected]
- Set stricter CSP header in redirect response
- deps: parseurl@~1.3.3
- deps: [email protected]
- deps: [email protected]
- deps: statuses@~1.5.0
- Add
103 Early Hints
- Add
- deps: type-is@~1.6.18
- deps: mime-types@~2.1.24
- perf: prevent internal
throw
on invalid type
Commits
The new version differs by 53 commits.
10c7756
4.17.0
9dadca2
docs: remove Gratipay links
b8e5056
tests: ignore unreachable line
94e48a1
build: update example dependencies
efcb17d
deps: [email protected]
b9ecb9a
build: support Node.js 12.x
5266f3a
build: test against Node.js 13.x nightly
e502dde
build: [email protected]
da6f701
deps: range-parser@~1.2.1
88f9733
deps: [email protected]
8267c4b
deps: [email protected]
bc07a41
deps: finalhandler@~1.1.2
c754c8a
build: support Node.js 11.x
e917028
build: [email protected]
7b076bd
build: [email protected]
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 π΄
An in-range update of express-handlebars is breaking the build π¨
The dependency express-handlebars was updated from 3.0.0
to 3.0.1
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
express-handlebars 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 failed (Details).
Commits
The new version differs by 22 commits.
5d27bb5
Update package.json
6c2d279
Merge pull request #243 from asos-albinotonnina/patch-1
2968603
π¨π¨ Security Update: Handlebars dependency
ba0f0d7
Merge pull request #191 from JosephUz/master
a78b2f0
Merge pull request #192 from GeekG1rl/patch-1
c8a1071
Merge pull request #234 from knoxcard/patch-1
6f97997
Merge pull request #237 from feygon/patch-1
32f6b04
Merge pull request #241 from erikeckhardt/erikeckhardt-patch-1
73eed8e
Fix typo
f755e50
fixed a typo
d71cd4f
bump glob, handlebars, object.assign and promise
516fb37
Update README.md
d00d3fe
solves #160
a66aad4
Merge pull request #148 from camabeh/master
077a667
Merge pull request #180 from kevmo/patch-1
There are 22 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 helmet is breaking the build π¨
Version 3.2.0 of helmet just got published.
Branch | Build failing π¨ |
---|---|
Dependency | helmet |
Current Version | 3.1.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As helmet is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of chromedriver is breaking the build π¨
Version 2.25.2 of chromedriver just got published.
Branch | Build failing π¨ |
---|---|
Dependency | chromedriver |
Current Version | 2.25.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As chromedriver is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of webdriverio is breaking the build π¨
Version 4.5.0 of webdriverio just got published.
Branch | Build failing π¨ |
---|---|
Dependency | webdriverio |
Current Version | 4.4.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As webdriverio is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 72 commits .
cdb36ab
v4.5.0
c1c9aa6
Update contributors
55e3a67
update changelog
2377aea
fix multiremote issue
9fcb5db
bump wdio-mocha-framework
3ab3212
add uses property to touchAction command docs [ci skip]
68974ac
propagate protocol to runner instances - refs #1683
9b879fb
remove protocol as default option
0ba7948
add docs for repl usage
e2dd3a0
display error if repl session can't be started
b02b22a
add saucelabs-sample-test-frameworks/JS-Mocha-WebdriverIO-Selenium boilerplate reference project
950a373
Merge pull request #1759 from wvankuipers/add-uid-to-runner
dbcfadc
Added uid to testdetails payload (when available)
05797db
finised cli repl command
89c584a
support standalone repl
There are 72 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of grunt 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 grunt was updated from 1.0.4
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.
grunt is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Release Notes for v1.1.0
- Update to mkdirp ~1.0.3
- Only support versions of Node >= 8
Commits
The new version differs by 8 commits.
d5cdac0
Merge pull request #1706 from gruntjs/tag-neew
4674c59
v1.1.0
6124409
Merge pull request #1705 from gruntjs/mkdirp-update
0a66968
Fix up Buffer usage
4bfa98e
Support versions of node >= 8
f1898eb
Update to mkdirp ~1.0.3
75da17b
HTTPS link to gruntjs.com (#1683)
6795d31
Update js-yaml dependecy to ~3.13.1 (#1680)
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-uuid is breaking the build π¨
Version 1.4.8 of node-uuid just got published.
Branch | Build failing π¨ |
---|---|
Dependency | node-uuid |
Current Version | 1.4.7 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As node-uuid is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 1 commits .
6f0f31b
Deprecation notice in README
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of bunyan is breaking the build π¨
Version 1.8.6 of bunyan just got published.
Branch | Build failing π¨ |
---|---|
Dependency | bunyan |
Current Version | 1.8.5 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As bunyan is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 2 commits .
4b9df66
authors update
550ea90
Bunyan's
safeCycles
is too slow when logging large objects. Fixes #474
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of handlebars-helpers is breaking the build π¨
Version 0.7.6 of handlebars-helpers just got published.
Branch | Build failing π¨ |
---|---|
Dependency | handlebars-helpers |
Current Version | 0.7.5 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As handlebars-helpers is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 11 commits .
7ef7fa1
generate docs
1d9852b
update deps
afadfd5
add comments
892b6d5
run update
c82d86a
Merge pull request #226 from alisd23/master
ae4b6ec
Merge pull request #239 from nathanjessen/master
573cad9
Add quotations to the id of the gist helper
d9697cf
Merge pull request #232 from Swapnull/master
2509bdc
Fixed the documentation of toPrecision so the 'precision' paramater is also declared
d7602f4
Fix markdown by making properties enumerable
8aa4382
0.7.5
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of grunt is breaking the build π¨
Version 1.0.2 of grunt was just published.
Branch | Build failing π¨ |
---|---|
Dependency | grunt |
Current Version | 1.0.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
grunt is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 27 commits.
ccc3163
v1.0.2
e7795dc
Remove iojs from test matrix (#1622)
a6a133b
Remove deprecation warning for coffeescript (#1621) r=@vladikoff
06b377e
https links to webchat.freenode.net and gruntjs.com (#1610)
7c5242f
Use node executable for local grunt bin for Windows support
f6cbb63
Oh right, Windows isnt bash
a9a20da
Try and debug why appveyor is failing on npm
48bba6c
Move to the test script to avoid npm was unexpected at this time.
6b97ac0
Try to fix appveyor script
19003ba
For appveyor, check node version to decide whether to install npm@3
3fcf921
Install npm@3 if npm version is npm 1 or 2
77fc157
Use the local version of grunt to run tests
400601a
Updating devDependencies
6592ad1
Update travis/appveyor to node versions we support
b63aeec
Dont manually install npm, use the version each node version corresponds with
There are 27 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 serve-favicon is breaking the build π¨
Version 2.4.0 of serve-favicon just got published.
Branch | Build failing π¨ |
---|---|
Dependency | serve-favicon |
Current Version | 2.3.2 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As serve-favicon is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
2.4.0- deps: etag@~1.8.0
- Use SHA1 instead of MD5 for ETag hashing
- Works with FIPS 140-2 OpenSSL configuration
- deps: [email protected]
- Fix false detection of
no-cache
request directive - perf: enable strict mode
- perf: hoist regular expressions
- perf: remove duplicate conditional
- perf: remove unnecessary boolean coercions
- Fix false detection of
- perf: simplify initial argument checking
Commits
The new version differs by 11 commits .
b2073b1
2.4.0
4d7024d
lint: use standard style in readme
92e0a99
lint: use standard style
0f44452
deps: etag@~1.8.0
f91ae78
deps: [email protected]
2301e1f
build: [email protected]
42f6966
tests: make the buffer tests more self-contained
92d222c
build: support Node.js 7.x
242c838
perf: simplify initial argument checking
a8bd991
tests: replace proxyquire with writing temp files
c54b3ee
build: [email protected]
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of debug is breaking the build π¨
Version 2.4.0 of debug just got published.
Branch | Build failing π¨ |
---|---|
Dependency | debug |
Current Version | 2.3.3 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As debug is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 7 commits .
b82d4e6
release 2.4.0
41002f1
Update bower.json (#342)
e58d54b
Node: configurable
util.inspect()
options (#327)00f3046
Node:
%O
(big O) pretty-prints the object (#322)bd9faa1
allow colours in workers (#335)
501521f
Use same color for same namespace. (#338)
e2a1955
Revert "handle regex special characters"
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
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-levelnode_js
that didnβt already include Node.js 10, such asnode
orlts/*
. 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 grunt-contrib-jshint is breaking the build π¨
Version 1.1.0 of grunt-contrib-jshint just got published.
Branch | Build failing π¨ |
---|---|
Dependency | grunt-contrib-jshint |
Current Version | 1.0.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As grunt-contrib-jshint is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 10 commits .
-
8d38fc2
v1.1.0
-
6401cee
Merge pull request #266 from paladox/patch-15
-
b0aaf69
Update jshint to 2.9.4
-
bab102d
Merge pull request #257 from paychex/bugfix/reporter-output-path-256
-
8605e12
bugfix: 256 all paths are relative. Need to check if path is null as that's the default value per documentation.
-
4c6d853
Update CI configs from the latest grunt-contrib-internal.
-
3cc9836
Update grunt-contrib-internal
-
b10e7b6
Update grunt to 1.0.0
-
91a2db0
Update CHANGELOG.
-
638daca
Update CI configs.
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of nodemon is breaking the build π¨
Version 1.11.1 of nodemon just got published.
Branch | Build failing π¨ |
---|---|
Dependency | nodemon |
Current Version | 1.11.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As nodemon is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 8 commits.
8ef739a
docs: typo (#1059)
3426224
fix: update readme
7b39b45
docs: vertical rhythm (#1055)
f9fc962
Delete CNAME
0b367d5
Create CNAME
5c71aae
docs: move to github pages hosting
7352a4c
docs: add design principle
8c1fd44
chore: update site to https
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of webdriverio is breaking the build π¨
Version 4.3.0 of webdriverio just got published.
Branch | Build failing π¨ |
---|---|
Dependency | webdriverio |
Current Version | 4.2.16 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As webdriverio is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 93 commits .
-
57d68f5
v4.3.0
-
81dda1c
Update contributors
-
9317643
updated changelog
-
4004c62
polished up guide section
-
9c2059c
bumped wdio-mocha-framework [ci skip]
-
94a902a
minor [ci skip]
-
e7bb04f
don't build the project twice
-
e72015e
more build fixes
-
f6f300e
fix some build issues
-
b7c0754
remove grunt-cordova-cli as well
-
2c317ba
remove cordova dev dependency as it installs vulnarable deps
-
e4b5640
add native test for touchActions
-
5471794
eslint fixes
-
7091be6
no need for phantomjs prebuild as it is already available on travis
-
a44eae6
don't propagate selector if x and y is given
There are 93 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of helmet is breaking the build π¨
Version 3.1.0 of helmet just got published.
Branch | Build failing π¨ |
---|---|
Dependency | helmet |
Current Version | 3.0.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As helmet is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of 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 failed (Details).
Commits
The new version differs by 44 commits.
998b265
1.19.0
40a0e81
deps: type-is@~1.6.17
eda21da
build: support Node.js 12.x
dc7fea4
build: [email protected]
926f8f1
build: [email protected]
cc0cbac
deps: [email protected]
b69292b
build: [email protected]
1c9ed74
build: [email protected]
737cb13
build: [email protected]
93ba395
build: [email protected]
3eb8d29
build: [email protected]
d198d87
deps: [email protected]
91d0232
deps: [email protected]
c9718ce
build: [email protected]
a5701e3
build: [email protected]
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 wdio-mocha-framework is breaking the build π¨
Version 0.5.5 of wdio-mocha-framework just got published.
Branch | Build failing π¨ |
---|---|
Dependency | wdio-mocha-framework |
Current Version | 0.5.4 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As wdio-mocha-framework is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 14 commits .
0f0d5a3
v0.5.5
b788261
Update contributors
a143fea
bumped wdio-sync
e4000cf
improve waitUntilSettled logic
4b0a806
Merge pull request #27 from wvankuipers/wdio-spec-reporter_issues_11
2b65e4d
Refactored the generateUID method to return a UID and parentUID instead of altering the message directly
fc6fe2e
Fixed tests
f5ba730
Refactored the getUID method when starting a suite/hook or test, also added mising vars for messageCounter and messageUIDs
bb53b57
Changed UID generation to make sure it generates a unique variant for each suite, hook and test
e1be450
Corrected location of UID definition
0187975
Added check for uid to the test scenarioβs
d33dd40
Implemented UID with the value of the title of the test
141c8e2
only mark message as sent when process.send returns true
865480b
wait until all events has been sent to the main process - refs webdriverio/webdriverio#1713
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of grunt-contrib-clean is breaking the build π¨
Version 1.1.0 of grunt-contrib-clean just got published.
Branch | Build failing π¨ |
---|---|
Dependency | grunt-contrib-clean |
Current Version | 1.0.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As grunt-contrib-clean is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 7 commits .
d1cd6ca
v1.1.0
985cc7f
Updating internal
147f51b
Update grunt to 1.0.0
d1533d4
Update docs.
431cc70
Update CHANGELOG.
47d7f31
update readme
2f5499c
Remove node_modules from appveyor cache
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of helmet is breaking the build π¨
The dependency helmet was updated from 3.15.1
to 3.16.0
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
helmet 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 failed (Details).
Commits
The new version differs by 18 commits.
123e93c
3.16.0
e9c6eab
Update changelog for 3.16.0 release
1cff218
Update ienoopen to v1.1.0
c8578fe
Minor: use xssFilter instead of noCache in readme example
09c90d2
Update changelog with a few more changes
94e92d0
Minor: reference the "drop support for Node <4" commit in the changelog
1dab41f
Fix link to CHANGELOG.md from HISTORY.md
a49cec3
Drop support for Node <4
9f13f08
Add email to
bugs
field in package.jsonce70edc
Minor: add more specificity to
.npmignore
3a37f1f
Update Adam Baldwin's contact information
1be1cbc
Update hsts to 2.2.0
354e80e
Update devDependencies to latest versions
b7f7359
Note that the changelog is now in Keep A Changelog format
b381760
Update changelog to match https://keepachangelog.com/ standard
There are 18 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 session-file-store is breaking the build π¨
Version 1.1.0 of session-file-store just got published.
Branch | Build failing π¨ |
---|---|
Dependency | session-file-store |
Current Version | 1.0.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
session-file-store is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 12 commits.
0aa2350
upgraded to 1.1.0 version.
fd6c5ca
updates dev dependencies version and travis config
3523df1
Merge pull request #57 from takkaria/master
ed5889e
Merge branch 'master' into master
37ad381
updates dependencies version
b5bdd0a
cleanup readme file
7cb9328
Merge pull request #55 from ma-zal/fix-touch
dadf6ff
Allow falsy values in user options to override defaults
979260d
Improved
touch
method for session data rewrite prevention.caad95e
update description style
e142425
update key function description
6ab3d30
fix key function description
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of node-cache is breaking the build π¨
The dependency node-cache was updated from 4.2.0
to 4.2.1
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
node-cache 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 failed (Details).
Commits
The new version differs by 15 commits.
f0c55ff
updated lodash to latest 4.17.15
f0a9e97
bump version 4.2.1
13f1b0c
update readme for v4.2.1
0aae371
fix some typos - thx @daluf
b3fd6c4
fix tests with new mocha + coffee script dependencies
c72383d
Merge pull request #128 from AndrewLane/patch-1
3a19704
Typo fix
8399b71
clean up dockertests, update package.json, update copyright
ff189d4
Merge branch 'update-dependencies'
09682f1
warn about upcoming major release
b208726
update dependencies so npm audit will shut up; update nvmrc to 10.16
ca51a2e
Merge branch 'master' of github.com:mpneuried/nodecache
5edeb0d
add .nvmrc
f30c814
Merge pull request #120 from IsuruNana/patch-1
c9c3f97
Fix typo (exmaple to example) in 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 helmet is breaking the build π¨
The dependency helmet was updated from 3.21.2
to 3.21.3
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
helmet 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 failed (Details).
Commits
The new version differs by 6 commits.
903c88e
3.21.3
9c359ba
Update changelog for 3.21.3 release
a857597
Update helmet-csp to v2.9.5
d911036
Stop testing on Node 6, start testing on Node 12
a7b5b0e
Update Sinon to 9.0.0
ebf480e
Update Mocha to 7.0.1
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-session is breaking the build π¨
Version 1.15.1 of express-session just got published.
Branch | Build failing π¨ |
---|---|
Dependency | express-session |
Current Version | 1.15.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As express-session is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you itβs very likely also breaking them.
I recommend you give this issue a very high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/travis-ci/push The Travis CI build failed Details
Release Notes
1.15.1- deps: [email protected]
- Fix deprecation messages in WebStorm and other editors
- Undeprecate
DEBUG_FD
set to1
or2
Commits
The new version differs by 3 commits .
8e56128
1.15.1
f855053
build: [email protected]
eba2521
deps: [email protected]
See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
An in-range update of express-handlebars is breaking the build π¨
The dependency express-handlebars was updated from 3.0.2
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.
express-handlebars 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 failed (Details).
Commits
The new version differs by 10 commits.
5729018
v3.1.0
588646f
bump handlebars to 4.1.2 to fix vulnerability issue
eac8710
Merge pull request #249 from jfbrennan/master
87f7c11
Update README.md
e7e1194
Update README.md
3334f4f
Update README.md
ebbb003
Update server.js
cf09e20
Update server.js
489e8d8
Update express-handlebars.js
d489794
Update express-handlebars.js
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
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.