zkat / figgy-pudding

Cascading, controlled-visibility options object management.

Hi there 👋

I'm Kat!

I'm a Rust, C#, and JavaScript developer working at Microsoft and I do a bunch of open source stuff.

You can also find me on Mastodon as @[email protected] and Matrix as @kat:zkat.tech, or on Discord as kat#8645.

figgy-pudding's Issues

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

Version 10.3.3 of tap just got published.

Branch	Build failing 🚨
Dependency	tap
Current Version	10.3.2
Type	devDependency

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

As tap 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
• ✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
• ✅ coverage/coveralls First build on greenkeeper/tap-10.3.3 at 91.304% Details

---

Commits

The new version differs by 6 commits.

• ec47ea5 v10.3.3
• 12255f8 update nyc to 11.0.2 release candidate
• 7a66dba --debug removed in node 8
• 69d6097 bump nyc dep
• e0b319a Drop 0.10 from travis-ci
• 81aa913 Fix tests on 0.10

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 🌴