Skip to content

Update yabeda 0.14.0 → 0.15.0 (major)#1436

Open
depfu[bot] wants to merge 1 commit intomasterfrom
depfu/update/yabeda-0.15.0
Open

Update yabeda 0.14.0 → 0.15.0 (major)#1436
depfu[bot] wants to merge 1 commit intomasterfrom
depfu/update/yabeda-0.15.0

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Mar 5, 2026

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?

✳️ yabeda (0.14.0 → 0.15.0) · Repo · Changelog

Release Notes

0.15.0

Fixed

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

Commits

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

↗️ anyway_config (indirect, 2.7.2 → 2.8.0) · Repo · Changelog

Release Notes

2.8.0

Features

  • Allow specifying data sources on per-class basis:
class MyConfig < Anyway::Config
  # Only load configuraiton data from ENV and credentials
  self.configuration_sources = [:env, :credentials]
  # ...
end

Changes

  • Improved gem boot time by avoiding loading optional providers and limiting refinements usage (ref)

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

Commits

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

↗️ concurrent-ruby (indirect, 1.3.5 → 1.3.6) · Repo · Changelog

Release Notes

1.3.6

What's Changed

New Contributors

Full Changelog: v1.3.5...v1.3.6

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

Commits

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

↗️ dry-initializer (indirect, 3.0.4 → 3.2.0) · Repo · Changelog

Release Notes

3.2.0

Changed

  • Set minimal supported Ruby version to 3.1 (@flash-gordon)
  • Exclude block forwarding from Root#initialize. This helps
    with tracking down calls that shouldn't pass a block in Ruby 3.4 (see #109) (@flash-gordon)

Compare v3.1.1...v3.2.0

3.1.1

Changed

  • Improved error messages were rolled back, they created an implicit dependency on dry-types (@flash-gordon)

Compare v3.1.0...v3.1.1

3.1.0

Changed

  • Improved error messages on type mismatch (@swerling)
  • [BREAKING] Minimal supported Ruby version is 2.7 (@flash-gordon)

Compare v3.0.4...v3.1.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.

↗️ ruby-next-core (indirect, 1.1.2 → 1.2.0) · Repo · Changelog

Release Notes

1.2.0

This release brings better compatibility with Ruby 4.0 and some new features.

Features

Some new Ruby 4.0 core APIs are added:

  • Array#rfind.
  • String#strip w/ selectors (e.g., "R1u2b3y4".strip("0-4") #=> Ruby).
  • UpdatedEnumerator.produce to support the new size: argument.

Fixes

  • Upgraded it rewriter to better work with Prism and use local variables instead of numbered params to support nesting.

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

Commits

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


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 Mar 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants