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.

Sign up for GitHub

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

Jump to bottom

Update config 4.2.1 → 5.5.1 (major) #613

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update config 4.2.1 → 5.5.1 (major) #613

wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented May 31, 2024

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?

✳️ config (4.2.1 → 5.5.1) · Repo · Changelog

Release Notes

5.5.1 (from changelog)

Documentation

  • Fix funding_url to funding_uri in gemspec (#361)

5.5.0

What's Changed

  • Allow arrays to be passed through env variables by @dominh in #354
  • Fix typos in the tests and documentation by @ydah in #359
  • Use funding_url rather than post_install_message by @pda in #360

New Contributors

Full Changelog: 5.4.0...5.5.0

5.4.0

New features

  • Add configuration option environment to override the use of Rails.env (#356)

5.3.0

  • Remove dry-validation from dependencies (#333)

5.2.0

New features

  • Allow to use custom filename && directory name to store configs (#341)

Bug fixes

  • Prevent name collision with private methods from ancestors (#351)

5.1.0 (from changelog)

  • Fix conflicts with Rails 7 active_support methods (#347)

5.0.0 (from changelog)

BREAKING CHANGES

  • No longer load deep_merge's monkey patch for Hash#deep_merge and Hash#deep_merge! (#342). If you rely on those methods and are not using Rails / Active Support, you can load the monkey patch via require 'deep_merge/deep_merge_hash'. This change fixes Rails 7.x support.

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

↗️ concurrent-ruby (indirect, 1.2.2 → 1.3.1) · Repo · Changelog

Release Notes

1.3.1

This release is essentially v1.3.0, but with a properly packaged gem. There was an issue publishing v1.3.0 and that gem needed to be yanked to avoid breaking downstream projects. The v1.3.0 changelog is reproduced below.

What's Changed

  • Add Concurrent.usable_processor_count that is cgroups aware by @casperisfine in #1038
  • Align Java Executor Service behavior for shuttingdown?, shutdown? by @bensheldon in #1042

New Contributors

Full Changelog: v1.2.3...v1.3.1

1.2.3

What's Changed

New Contributors

Full Changelog: v1.2.2...v1.2.3

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

Commits

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

↗️ dry-configurable (indirect, 1.0.1 → 1.1.0) · Repo · Changelog

Release Notes

1.1.0

Fixed

Compare v1.0.1...v1.0.2

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

Commits

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

↗️ dry-core (indirect, 1.0.0 → 1.0.1) · Repo · Changelog

Release Notes

1.0.1

Fixed

  • [equalizer] Add Dry::Core.Equalizer method to make include Dry::Core.Equalizer(...) work as documented (via #79) (@timriley)

    Users of Equalizer should now only need to require "dry/core" first.

Compare v1.0.0...v1.0.1

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

Commits

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

↗️ dry-schema (indirect, 1.13.3 → 1.13.4) · Repo · Changelog

Release Notes

1.13.4

Added

Fixed

  • Fix json-schema type of objects nested under arrays (issue #400 fixed via #462) (@tomgi)

Changed

Compare v1.13.3...v1.13.4

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

Commits

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

↗️ dry-types (indirect, 1.7.1 → 1.7.2) · Repo · Changelog

Release Notes

1.7.2

Fixed

  • Fixed BigDecimal warning due to not being required in gemspec (@bkuhlmann in #464)

Compare v1.7.1...v1.7.2

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

Commits

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

↗️ zeitwerk (indirect, 2.6.12 → 2.6.15) · Repo · Changelog

Release Notes

2.6.15 (from changelog)

  • Internal improvements.

2.6.14 (from changelog)

  • Implements Zeitwerk::Loader#all_expected_cpaths, which returns a hash that maps the absolute paths of the files and directories managed by the receiver to their expected constant paths.

    Please, check its documentation for further details.

2.6.13 (from changelog)

  • There is a new experimental null inflector that simply returns its input unchanged:

    loader.inflector = Zeitwerk::NullInflector.new

    Projects using this inflector are expected to define their constants in files and directories with names exactly matching them:

    User.rb       -> User
HTMLParser.rb -> HTMLParser
Admin/Role.rb -> Admin::Role

    Please see its documentation for further details.

  • Documentation improvements.

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

Commits

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

🆕 bigdecimal (added, 3.1.8)

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 recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​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)

@depfu depfu bot added the depfu label May 31, 2024
@depfu depfu bot mentioned this pull request May 31, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
depfu
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants