Skip to content
This repository was archived by the owner on Dec 24, 2019. It is now read-only.

Conversation

@depfu
Copy link

@depfu depfu bot commented Apr 18, 2018

We've updated a dependency and here is what you need to know:

name version specification old version new version
jquery-rails 4.3.1 4.3.3

Additionally, the update changed a few other dependencies as well:

action name old version new version
updated crass 1.0.3 1.0.4
updated erubi 1.7.0 1.7.1
updated i18n 0.9.1 0.9.5
updated loofah 2.1.1 2.2.2
updated minitest 5.10.3 5.11.3
updated nokogiri 1.8.1 1.8.2
updated rack 2.0.3 2.0.4
updated rack-test 0.7.1 1.0.0
updated rails-html-sanitizer 1.0.3 1.0.4
updated rake 12.3.0 12.3.1
updated tzinfo 1.2.4 1.2.5

You should probably take a good look at the info here and the test results before merging this pull request, of course.

What changed?

✳️ jquery-rails (4.3.1 → 4.3.3) · Repo · Changelog

Commits

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

↗️ crass (indirect, 1.0.3 → 1.0.4) · Repo · Changelog

Release Notes

From the Github release:

Commits

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

↗️ erubi (indirect, 1.7.0 → 1.7.1) · Repo · Changelog

Commits

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

↗️ i18n (indirect, 0.9.1 → 0.9.5) · Repo · Changelog

Release Notes

From the Github release:

  • #404 reported a regression in 0.9.3, which wasn't fixed by 0.9.4. #408 fixes this issue.

Thanks @wjordan!

Commits

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

↗️ loofah (indirect, 2.1.1 → 2.2.2) · Repo · Changelog

Release Notes

From the Github release:

2.2.2 / 2018-03-22

Make public Loofah::HTML5::Scrub.force_correct_attribute_escaping!,
which was previously a private method. This is so that downstream gems
(like rails-html-sanitizer) can use this logic directly for their own
attribute scrubbers should they need to address CVE-2018-8048.

Commits

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

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

↗️ nokogiri (indirect, 1.8.1 → 1.8.2) · Repo · Changelog

Commits

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

↗️ rack (indirect, 2.0.3 → 2.0.4) · Repo · Changelog

Commits

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

↗️ rack-test (indirect, 0.7.1 → 1.0.0) · Repo · Changelog

Release Notes

From the Github release:

1.0.0 / 2018-03-27

  • The first release in the 1.0.0 series. 🎉 For the 1.x releases, we will follow Semantic Versioning very strictly; please keep this in mind when submitting fixes/suggesting changes.

  • Breaking changes:

    • Always set CONTENT_TYPE for non-GET requests
      (Per Lundberg #223)
  • Minor enhancements / bug fixes:

    • Create tempfile using the basename without extension
      (Edouard Chin #201)
    • Save session during follow_redirect!
      (Alexander Popov #218)
    • Document how to use URL params with DELETE method
      (Timur Platonov #220)
Commits

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

↗️ rails-html-sanitizer (indirect, 1.0.3 → 1.0.4) · Repo · Changelog

Release Notes

From the Github release:

Commits

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

↗️ rake (indirect, 12.3.0 → 12.3.1) · Repo · Changelog

Commits

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

↗️ tzinfo (indirect, 1.2.4 → 1.2.5) · Repo · Changelog

Release Notes

From the Github release:

  • Support recursively (deep) freezing Country and Timezone instances. #80.
  • Allow negative daylight savings time offsets to be derived when reading from zoneinfo files. The utc_offset and std_offset are now derived correctly for Europe/Dublin in the 2018a and 2018b releases of the Time Zone Database.

TZInfo v1.2.5 on RubyGems.org

Commits

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


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.

Depfu Status

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant