Skip to content

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Oct 10, 2025

We've tested your project with an updated dependency and the build failed.

This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name version specification new version
bigdecimal ~> 3.1 3.3.1

Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.

If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)

We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of bigdecimal for this test run.

What changed?

✳️ bigdecimal (~> 3.1 → 3.3.1) · Repo · Changelog

Release Notes

3.3.1

What's Changed

  • Fix modulo/remainder of negative zero by @tompng in #441
  • Unify all precision validation to be consistent with BigDecimal#add by @tompng in #442
  • Bump version to 3.3.1 by @tompng in #443

Full Changelog: v3.3.0...v3.3.1

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

Commits

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

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant