ryanfb / cts-cite-driver

Driver JavaScript app for CTS/CITE integration
http://ryanfb.github.com/cts-cite-driver/
1 stars 3 forks source link

Update github-pages: 200 → 201 (major) #41

Closed depfu[bot] closed 5 years ago

depfu[bot] commented 5 years ago

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ github-pages (200 → 201) · Repo

Release Notes

201

  • Update Rouge to v3.11.0 (#652)
  • Update jekyll-commonmark-ghpages to v0.1.6 (#652)

Does any of this look wrong? Please let us know.

Sorry, we couldn't find anything useful about this release.

↗️ faraday (indirect, 0.15.4 → 0.17.0) · Repo · Changelog

Release Notes

0.17.0

ATTENTION: This is a ROLLBACK RELEASE!

We apologise for the issues created by the v0.16.x release series, these were due to the Faraday team underestimating the latest changes applied to master since v0.15.4 (November 2018).
The v0.16.0 -> v0.16.2 releases will be removed from Rubygems and all changes contained in master will be released as v1.0.

v0.17.x will continue from where v0.15.4 left so it will not give any backwards-incompatible issues like the v0.16.x series did.

Extra Note: some gems using Faraday may keep a cache of request/responses data. We suggest you to clear any cache related to Faraday requests after upgrading to v0.17.0 (e.g. github-changelog-generator/github-changelog-generator#738 (comment))

Diff from v0.15.4

  • Include instructions for using custom middleware (#836)
  • Travis: add 2.6.0 to CI matrix, remove sudo: false (#839)
  • Explicitly require date for DateTime (#844)
  • README: Travis build badge for branch master (#849)

0.16.2

Bugs:

0.16.1

Bugs:

  • Restore backwards compatibility layer for Faraday errors under the Faraday::Error module #1030 (@michaelherold)

0.16.0

This release also includes all the updates from RC-1.

Features:

  • Create ParamPart class to allow multipart posts with JSON content and file upload at the same time #1017 (@jeremy-israel)
  • Rename UploadIO -> FilePart to be consistent with ParamPart class name. #1021 (@technoweenie)
    • UploadIO class name is preserved for backwards compatibility.
  • Enable response body streaming in Excon. #1026 (@technoweenie)

Bugs:

Misc:

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 6 commits:

↗️ jekyll-commonmark-ghpages (indirect, 0.1.5 → 0.1.6) · Repo

Commits

See the full diff on Github. The new version differs by 14 commits:

↗️ minitest (indirect, 5.11.3 → 5.12.2) · Repo · Changelog

Release Notes

5.12.2 (from changelog)

  • 1 bug fix:

    • After chatting w/ @y-yagi and others, decided to lower support to include ruby 2.2.

5.12.1 (from changelog)

  • 1 minor enhancement:

    • Added documentation for Reporter classes. (sshaw)

  • 3 bug fixes:

    • Avoid using 'match?' to support older ruby versions. (y-yagi)

    • Fixed broken link to reference on goodness-of-fit testing. (havenwood)

    • Update requirements in readme and Rakefile/hoe spec.

5.12.0 (from changelog)

  • 8 minor enhancements:

    • Added a descriptive error if assert_output or assert_raises called without a block. (okuramasafumi)

    • Changed mu_pp_for_diff to make having both n and \n easier to debug.

    • Deprecated $N for specifying number of parallel test runners. Use MT_CPU.

    • Deprecated use of global expectations. To be removed from MT6.

    • Extended Assertions#mu_pp to encoding validity output for strings to improve diffs.

    • Extended Assertions#mu_pp to output encoding and validity if invalid to improve diffs.

    • Extended Assertions#mu_pp_for_diff to make escaped newlines more obvious in diffs.

    • Fail gracefully when expectation used outside of `it`.

  • 3 bug fixes:

    • Check `option` klass before match. Fixes 2.6 warning. (y-yagi)

    • Fixed Assertions#diff from recalculating if set to nil

    • Fixed spec section of readme to not use deprecated global expectations. (CheezItMan)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 34 commits:

↗️ rouge (indirect, 2.2.1 → 3.11.0) · Repo · Changelog

Release Notes

3.11.0

This release includes some fixes for existing lexers and support for three new languages.

I'd also like to call out the updates to the Liquid lexer. Although this was submitted via a single PR, it represents a substantial amount of work and is a large upgrade to the previous version of the lexer. Special thanks to @EricFromCanada 🎉

3.10.0

This release includes a couple of fixes and support for five new languages.

3.9.0

This release includes fixes for a number of lexers and support for three new languages.

This is a lighter release in comparison to the past couple of versions. We've taken a bit of a summer break and perhaps been slightly distracted by the latest update to No Man's Sky.

3.8.0

This release includes continued improvements to the library, fixes for a number of lexers and support for seven new languages.

3.7.0

This release includes continued improvements to the library, fixes for a number of lexers and support for eight new languages.

3.6.0

This release includes continued improvements to the library, fixes for a number of lexers and—like v3.5.0—support for three new languages.

3.5.1

This release fixes a bug in the PowerShell lexer that was affecting some users.

3.5.0

This release includes continued improvements to the library, fixes for a number of lexers and support for three new languages.

3.4.1

This is an important update.

Version 3.4.0 mistakenly included a breaking change. For some consumers of the library, this could cause Rouge to crash. This release reverts the behaviour to be consistent with version 3.3.0.

We are sorry to everyone affected by the error.

3.4.0

UPDATE: We are sorry to say that v3.4.0 contains a breaking change that can cause Rouge to crash for some users. Please use v3.4.1 instead.


And we're back with a new release!

Thank you to all our contributors for making this release possible. Things have been quiet for the past few months but we're working our way through the outstanding PRs and issues and hope to return to a more regular cadence for future releases.

3.3.0

Release 3.3.0

3.2.0

Version 3.2.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)