greenkeeperio / badges Goto Github PK

View Code? Open in Web Editor NEW

10.0 10.0 13.0 141 KB

:sparkles: shiny README badges

Home Page: https://greenkeeper.io/

License: Apache License 2.0

JavaScript 93.54% Shell 5.45% Dockerfile 1.01%

badges's People

Contributors

Stargazers

Watchers

Forkers

pridiltal m1ck2 uniibu pradeep0601 bovas85 trustyboard stonebuzz js2me baby636

badges's Issues

Styles not working

For example, for greenkeeperio/greenkeeper:

flat (default):
flat-square:
plastic:

All styles work seem to work locally, it’s only badges.greenkeeper.io which always serves the same style. This might have something to do with caching since all three badges return the same ETag (ef8933a07de557ea2af70751db30ba052ef8d6c17d58568e43724d0797e936dc-gzip).

An in-range update of pouchdb-mapreduce is breaking the build 🚨

Version 6.3.0 of pouchdb-mapreduce just got published.

Branch	Build failing 🚨
Dependency	pouchdb-mapreduce
Current Version	6.2.0
Type	dependency

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

pouchdb-mapreduce 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 🌴

Badge display is broken

Even in this repo.

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

The dependency bluebird was updated from `3.5.3` to `3.5.4`.

🚨 View failing branch.

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

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

Proper version check supporting VSCode(#1576)

Commits

The new version differs by 6 commits.

e0222e3 Release v3.5.4
4b9fa33 missing --expose-gc flag (#1586)
63b15da docs: improve and compare Promise.each and Promise.mapSeries (#1565)
9dcefe2 .md syntax fix for coming-from-other-languages.md (#1584)
b97c0d2 added proper version check supporting VSCode (#1576)
499cf8e Update jsdelivr url in docs (#1571)

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

The dependency rollbar was updated from `2.6.1` to `2.7.0`.

🚨 View failing branch.

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

rollbar 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 v2.7.0

Pull Requests:

Allow enable/disable uncaught errors/rejections in .configure #729
Enable rate limiting for node/server environment #730
Lambda: Clear timer to avoid unexpected "Function timed out" errors #731

Commits

The new version differs by 10 commits.

fa0843d Release v2.7.0
ca1d6f1 Merge pull request #731 from rollbar/wj-cancel-lambda-timer
6a9d7ca Merge pull request #729 from rollbar/wj-capture-uncaught
cafe22d Merge pull request #730 from rollbar/wj-rate-limits
958ea0d fix: clear timer to avoid unexpected "Function timed out" errors
8a0b208 feat: enable rate limiting for node/server
2a8f44f feat: allow enable/disable uncaught errors and rejections in Rollbar.configure
d35e544 Merge pull request #727 from rollbar/wj-react-native-tests
c612630 test: add tests for react-native build
41dba62 build: migrate to webpack 4

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

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

Version 2.2.10 of rollbar was just published.

Branch	Build failing 🚨
Dependency	rollbar
Current Version	2.2.9
Type	dependency

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

rollbar 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

v2.2.10

Fixed a bug where maxItems was not properly respected when set in the initial configuration.

Commits

The new version differs by 9 commits.

b6a3fce Release v2.2.10
a3cdf8d Merge pull request #466 from rollbar/fix-global-config
2d40b94 we should only limit when the counter is strictly bigger than the limit and we should call global from configure as a fallback
eb83a3f add the ability to simulate slow loading of the full js library
41ab224 make sure global works in the constructor
0af1bb8 update angular 2 docs
bac22e8 Merge pull request #456 from rollbar/angular2
2f952f8 Moving to correct section of Angular2 docs
d54005a Adding troubleshooting for Angular2

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 engines config in 1 of your package.json files was updated to the new Node.js version

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

The dependency lodash was updated from `4.17.11` to `4.17.12`.

🚨 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 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 🌴

let's add customisation for badge SVG's

Hi!

The shields.io raised the bar allowing to customise the look of the badges, for example, make them flat and square by appending the attribute on the URL like:

https://img.shields.io/travis/codsen/ranges-sort.svg?style=flat-square

However, this does not work with native Greenkeeper badges:

https://badges.greenkeeper.io/codsen/ranges-sort.svg?style=flat-square

Notice the subtle difference between the two badges above.

Please implement the customisation to generate the flat and/or square SVG's upon request. Thank you.

Payment Required for Marketplace App

With a Greenkeeper purchased via the Marketplace I'm constantly seeing "payment required" on the badges.
We had a subscription running via the website before, so I'm not sure if this is interfering somehow.
Logging this here for now.

greenkeeperio / badges Goto Github PK

badges's People

Contributors

Stargazers

Watchers

Forkers

badges's Issues

Version 6.3.0 of pouchdb-mapreduce just got published.

The dependency bluebird was updated from 3.5.3 to 3.5.4.

The dependency rollbar was updated from 2.6.1 to 2.7.0.

Version 2.2.10 of rollbar was just published.

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

The dependency lodash was updated from 4.17.11 to 4.17.12.

Recommend Projects

Recommend Topics

Recommend Org

The dependency bluebird was updated from `3.5.3` to `3.5.4`.

The dependency rollbar was updated from `2.6.1` to `2.7.0`.

The dependency lodash was updated from `4.17.11` to `4.17.12`.