octokit / fixtures-server Goto Github PK
View Code? Open in Web Editor NEWFixtures server for browser & language agnositic octokit testing
License: MIT License
Fixtures server for browser & language agnositic octokit testing
License: MIT License
Branch | Build failing 🚨 |
---|---|
Dependency | semantic-release |
Current Version | 15.9.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release 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.
cli.js
(43d0646)The new version differs by 1 commits.
43d0646
fix: also hide sensitive info when loggin from cli.js
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
😎
Branch | Build failing 🚨 |
---|---|
Dependency | semantic-release |
Current Version | 15.9.11 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
semantic-release 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.
fail
/success
plugin params (dffe148)The new version differs by 1 commits.
dffe148
fix: hide sensitive data in relesae notes and fail
/success
plugin params
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
All mocks loaded with nock are stored globally. When loading the same fixture twice, nock cannot differentiate between the two instances as they use the same domain as scope.
To workaround that we can dynamically override the scope when loading the fixtures as well as in the proxy to contain the unique fixture id
Branch | Build failing 🚨 |
---|---|
Dependency | supertest |
Current Version | 3.2.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
supertest 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.
#509 - Fix #486, bug in _assertBody, switch to deepStrictEqual
(thanks @mikelax)
#510 - Refactor test files to use const/let (thanks @rimiti)
The new version differs by 10 commits.
e910e85
chore: Prepare for v3.3.0 release.
bd864de
Merge pull request #511 from visionmedia/bugfix-486-equal
101fbf5
Merge branch 'master' into bugfix-486-equal
04230bb
Merge pull request #510 from visionmedia/refact-const-let
510a7ae
bugfix: 486 Change method to use deepStrictEqual. (#509)
913150d
chore(.editorconfig) [*.md] block removed
82e0828
refact(test/supertest.js) vars replaced by const and let
5443136
chore(.editorconfig) configuration file created
7233ba6
chore(.eslintrc) parserOptions option added to use es6
322ebf6
bugfix: 486 Change method to use deepStrictEqual.
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
This issue contains a list of Renovate updates and their statuses.
These updates are awaiting their schedule. Click on a checkbox to ignore the schedule.
master
branch failed. 🚨I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
The npm token configured in the NPM_TOKEN
environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/
.
If you are using Two-Factor Authentication, make configure the auth-only
level is supported. semantic-release cannot publish with the default auth-and-writes
level.
Please make sure to set the NPM_TOKEN
environment variable in your CI with the exact value of the npm token.
Good luck with your project ✨
Your semantic-release bot 📦🚀
13.2.2
to 13.2.4
.This version is covered by your current version range and after updating it in your project the build failed.
yargs 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.
The new version differs by 14 commits.
a6e67f1
chore(release): 13.2.4
fc13476
chore: update standard-verison dependency
bf46813
fix(i18n): rename unclear 'implication failed' to 'missing dependent arguments' (#1317)
a3a5d05
docs: fix a broken link to MS Terminology Search (#1341)
b4f8018
build: add .versionrc that hides test/build
0c39183
chore(release): 13.2.3
08e0746
chore: update deps (#1340)
843e939
docs: make --no-
boolean prefix easier to find in the docs (#1338)
84cac07
docs: restore removed changelog of v13.2.0 (#1337)
b20db65
fix(deps): upgrade cliui for compatibility with latest chalk. (#1330)
c294d1b
test: accept differently formatted output (#1327)
ac3f10c
chore: move .hbs templates into .js to facilitate webpacking (#1320)
0295132
fix: address issues with dutch translation (#1316)
9f2468e
doc: clarify parserConfiguration object structure (#1309)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:
.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.
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 🤖
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Branch | Build failing 🚨 |
---|---|
Dependency | @octokit/fixtures |
Current Version | 7.0.2 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
@octokit/fixtures 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.
last-modified
Header (aa5f062)Content-Length: 0
Header for empty response (7e0326e)The new version differs by 11 commits.
ac427af
test(normalization): adapt for async normalization function
0915d8e
feat(scenario): get archive
f71c563
build(package): get-stream, gunzip-maybe, into-stream, tar-stream
6fe9ca6
feat(normalization): archive
af653a2
build(fixtures): updated normalized fixtures
01640ac
fix(normalize): get redirect URL from location header
7e0326e
fix(normalize): don’t set Content-Length: 0
Header for empty response
aa5f062
fix(normalize): last-modified
Header
1464607
fix: don’t bump fixture entity ID for previously calculated entity IDs
ad0b356
feat(normalization): async normalization methods
2b03562
chore(package): update axios to version 0.18.0
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.
Location: package.json
Error type: The renovate configuration file contains some invalid settings
Message: Invalid configuration option: author, Invalid configuration option: bin, Invalid configuration option: files, Invalid configuration option: keywords, Invalid configuration option: license, Invalid configuration option: main, Invalid configuration option: name, Invalid configuration option: now, Invalid configuration option: packageRules[0].@octokit/fixtures, Invalid configuration option: packageRules[0].cachimo, Invalid configuration option: packageRules[0].console-log-level, Invalid configuration option: packageRules[0].cors, Invalid configuration option: packageRules[0].express, Invalid configuration option: packageRules[0].glob, Invalid configuration option: packageRules[0].http-proxy-middleware, Invalid configuration option: packageRules[0].lodash, Invalid configuration option: packageRules[0].yargs, Invalid configuration option: packageRules[1].axios, Invalid configuration option: packageRules[1].pkg, Invalid configuration option: packageRules[1].prettier, Invalid configuration option: packageRules[1].proxyquire, Invalid configuration option: packageRules[1].semantic-release, Invalid configuration option: packageRules[1].supertest, Invalid configuration option: packageRules[1].tap, Invalid configuration option: pkg, Invalid configuration option: publishConfig, Invalid configuration option: release, Invalid configuration option: renovate, Invalid configuration option: scripts, Invalid configuration option: version
the problem is the implementation of the mapValuesDeep
function, I'm looking into it
3.3.0
to 3.4.0
.This version is covered by your current version range and after updating it in your project the build failed.
supertest 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.
The new version differs by 14 commits.
5640ac9
3.4.0
60f8a9e
Merge pull request #532 from visionmedia/v3.4.0
43bfae1
doc(History.md) changelog updated
fc1568d
doc(README.md) cookie example added
3192d96
chore(package-lock.json) file updated
b3d271f
chore(package.json) blocks reorganized, nock removed
aeae0f3
chore(.travis.yml) pipeline more explicit
53feddc
chore(test/supertest.js) obscure test removed
50c59d6
Merge pull request #519 from oprogramador/patch-3
6ca3897
Merge pull request #517 from oprogramador/patch-2
0146d81
auth info in README
d853b37
fix typo in README
8158979
Merge pull request #513 from rubendg/use-isarray
550613b
Use more robust Array instance check
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.