agrid's People
agrid's Issues
An in-range update of @angular/core is breaking the build 🚨
Version 4.2.4 of @angular/core just got published.
Branch | Build failing 🚨 |
---|---|
Dependency | @angular/core |
Current Version | 4.2.3 |
Type | peerDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @angular/core is “only” a peerDependency 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 ghooks is breaking the build 🚨
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 2.0.3 of ghooks was just published.
Branch | Build failing 🚨 |
---|---|
Dependency | ghooks |
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.
ghooks 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.
6128d0b
fix: lookup node_modules using relative path
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 🌴
Is there a demo of the awesome grid control?
Is there a demo of the awesome grid control?
Dose the grid have frozen column?
How to make the grid show horizontal scrollbar?
How to make the grid show horizontal scrollbar when content width is large?
An in-range update of @angular/compiler is breaking the build 🚨
Version 4.1.2 of @angular/compiler just got published.
Branch | Build failing 🚨 |
---|---|
Dependency | @angular/compiler |
Current Version | 4.1.1 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
@angular/compiler 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 gulp-tslint is breaking the build 🚨
Version 8.1.3 of gulp-tslint was just published.
Branch | Build failing 🚨 |
---|---|
Dependency | gulp-tslint |
Current Version | 8.1.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
gulp-tslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 4 commits.
c86c5ad
Release 8.1.3
e8c153d
Update dependencies.
5d72ae5
Merge pull request #143 from demurgos/issue-140
63be315
Drop dependency on deprecated gulp-util
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 🚨
Version 4.17.5 of lodash was just published.
Branch | Build failing 🚨 |
---|---|
Dependency | lodash |
Current Version | 4.17.4 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
lodash 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
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 @angular/platform-browser is breaking the build 🚨
Version 4.2.6 of @angular/platform-browser just got published.
Branch | Build failing 🚨 |
---|---|
Dependency | @angular/platform-browser |
Current Version | 4.2.5 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @angular/platform-browser 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 @types/hammerjs is breaking the build 🚨
Version 2.0.36 of @types/hammerjs was just published.
Branch | Build failing 🚨 |
---|---|
Dependency | @types/hammerjs |
Current Version | 2.0.35 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
@types/hammerjs 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).
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 @types/uglify-js is breaking the build 🚨
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 2.6.31 of @types/uglify-js was just published.
Branch | Build failing 🚨 |
---|---|
Dependency | @types/uglify-js |
Current Version | 2.6.30 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
@types/uglify-js 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
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 @types/webpack is breaking the build 🚨
Version 3.8.4 of @types/webpack was just published.
Branch | Build failing 🚨 |
---|---|
Dependency | @types/webpack |
Current Version | 3.8.3 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
@types/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 failed 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 🌴
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
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 nyc is breaking the build 🚨
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 11.6.0 of nyc was just published.
Branch | Build failing 🚨 |
---|---|
Dependency | nyc |
Current Version | 11.5.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
nyc is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details
Commits
The new version differs by 4 commits.
dd372f5
chore(release): 11.6.0
c6b30ba
feat: allow usage of ignoreClassMethods from istanbul (#785)
2d51562
fix: update to yargs version that allows extending configs with no extension (#790)
b4032ce
fix: removes unused split-lines dependency. (#787)
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 @angular/core is breaking the build 🚨
Version 4.0.1 of @angular/core just got published.
Branch | Build failing 🚨 |
---|---|
Dependency | @angular/core |
Current Version | 4.0.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @angular/core 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 @types/jasmine is breaking the build 🚨
Version 2.8.5 of @types/jasmine was just published.
Branch | Build failing 🚨 |
---|---|
Dependency | @types/jasmine |
Current Version | 2.8.4 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
@types/jasmine 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
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 @angular/compiler is breaking the build 🚨
Version 4.2.5 of @angular/compiler just got published.
Branch | Build failing 🚨 |
---|---|
Dependency | @angular/compiler |
Current Version | 4.2.4 |
Type | peerDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @angular/compiler is “only” a peerDependency 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 commitizen is breaking the build 🚨
Version 2.10.0 of commitizen was just published.
Branch | Build failing 🚨 |
---|---|
Dependency |
commitizen
|
Current Version | 2.9.6 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
commitizen 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
v2.10.0<a name"2.10.0">
2.10.0 (2018-05-24)
Bug Fixes
- lodash Node Security warning (#482) (0023958e)
- adapter: Don't print git root to stdout (#428) (d5e24245)
- cli: Don't print error stack trace if git-cz failed (#436) (#437) (53719a42)
Features
Commits
The new version differs by 15 commits.
89300f5
Configure Renovate (#464)
0023958
fix: lodash Node Security warning (#482)
40d8dab
Activating Open Collective (#468)
495437c
feat(strategies): respect the
--allow-emtpy
flag (#477)07b92bc
docs: Fix Angular commit conventions link (#458)
53853fe
chore(Update cz-conventional-changelog to 2.0.0): (#439)
d74b920
chore: add a project .editorconfig (#456)
f359d65
docs(readme): change deprecated adapter (#457)
4b32235
docs(contributing): Indentation usage and link to angular convention (#455)
de2459f
Grammar and layout tweaks (#447)
f2f0453
docs($README): add related projects (#444)
53719a4
fix(cli): Don't print error stack trace if git-cz failed (#436) (#437)
2e283a3
docs($readme): add note about avoiding double calls to
precommit
(#433)d5e2424
fix(adapter): Don't print git root to stdout (#428)
bc39af3
docs(readme): Fix incorrect spelling of "changelog" (#427)
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 tslint-loader is breaking the build 🚨
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 3.6.0 of tslint-loader was just published.
Branch | Build failing 🚨 |
---|---|
Dependency | tslint-loader |
Current Version | 3.5.3 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
tslint-loader 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
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 @angular/core is breaking the build 🚨
Version 4.1.2 of @angular/core just got published.
Branch | Build failing 🚨 |
---|---|
Dependency | @angular/core |
Current Version | 4.1.1 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
@angular/core 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 🌴
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.