Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update nock to version 6.0.1 πŸš€ #461

Merged
merged 1 commit into from
Jan 25, 2016
Merged

Update nock to version 6.0.1 πŸš€ #461

merged 1 commit into from
Jan 25, 2016

Conversation

greenkeeperio-bot
Copy link
Member

Hello πŸ‘‹

πŸš€πŸš€πŸš€

nock just published its new version 6.0.1, which is not covered by your current version range.

If this pull request passes your tests you can publish your software with the latest version of nock – otherwise use this branch to work on adaptions and fixes.

Happy fixing and merging 🌴


The new version differs by 33 commits .

  • 589a895 v6.0.1
  • 22becbe Merge branch 'alekbarszczewski-reply-headers-fix'
  • 2d4ccb9 browserify bundle update
  • 24738e9 Fixed issue with header function evaluation + added 2 tests
  • c2cdc57 changelog update
  • 2c96d8c v6.0.0
  • 0224c21 Merge branch 'BinChang-complex_query_string'
  • 8f11c8d add qs into package dependency block.
  • e9e2741 add test_complex_querystring into test list
  • aa18d8a minor update
  • 4dc1a28 support complex GET query based the behavior of request module.
  • c1904b7 changelog update
  • a4314d6 v5.5.0
  • c3ae1b6 Merge branch 'BinChang-parse_json_content'
  • ab2ac7f clean up tests

There are 33 commits in total. See the full diff.

gr2m added a commit that referenced this pull request Jan 25, 2016
Update nock to version 6.0.1 πŸš€
@gr2m gr2m merged commit 01cef2c into next Jan 25, 2016
@gr2m gr2m deleted the greenkeeper-nock-6.0.1 branch January 25, 2016 11:58
@gr2m gr2m removed the in progress label Jan 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants