Skip to content

Update dependency boost.multiprecision to v1.90.0.bcr.1#359

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/boost.multiprecision-1.x
Open

Update dependency boost.multiprecision to v1.90.0.bcr.1#359
renovate[bot] wants to merge 1 commit intomainfrom
renovate/boost.multiprecision-1.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Nov 3, 2025

This PR contains the following updates:

Package Type Update Change
boost.multiprecision bazel_dep minor 1.83.0.bcr.21.90.0.bcr.1

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Nov 3, 2025
@renovate renovate bot requested a review from a team November 3, 2025 06:37
@renovate renovate bot changed the title chore(deps): update dependency boost.multiprecision to v1.88.0.bcr.1 chore(deps): update dependency boost.multiprecision to v1.88.0.bcr.2 Nov 6, 2025
@renovate renovate bot force-pushed the renovate/boost.multiprecision-1.x branch from 7d7ed95 to 6df49cc Compare November 6, 2025 12:06
@renovate renovate bot changed the title chore(deps): update dependency boost.multiprecision to v1.88.0.bcr.2 chore(deps): update dependency boost.multiprecision to v1.89.0.bcr.1 Nov 11, 2025
@renovate renovate bot force-pushed the renovate/boost.multiprecision-1.x branch from 6df49cc to dd7222c Compare November 11, 2025 19:08
@renovate renovate bot changed the title chore(deps): update dependency boost.multiprecision to v1.89.0.bcr.1 chore(deps): update dependency boost.multiprecision to v1.89.0.bcr.2 Dec 13, 2025
@renovate renovate bot force-pushed the renovate/boost.multiprecision-1.x branch from dd7222c to f14c849 Compare December 13, 2025 16:48
@renovate renovate bot force-pushed the renovate/boost.multiprecision-1.x branch from f14c849 to 8a9d542 Compare January 19, 2026 16:45
@renovate renovate bot changed the title chore(deps): update dependency boost.multiprecision to v1.89.0.bcr.2 chore(deps): update dependency boost.multiprecision to v1.90.0.bcr.1 Feb 15, 2026
@renovate renovate bot force-pushed the renovate/boost.multiprecision-1.x branch from 8a9d542 to 23c29e7 Compare February 15, 2026 20:58
@renovate renovate bot force-pushed the renovate/boost.multiprecision-1.x branch from 23c29e7 to 40167fb Compare March 13, 2026 12:15
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Mar 13, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: MODULE.bazel.lock
Command failed: bazel mod deps --lockfile_mode=update
 no actions running
 no actions running
ERROR: boost.multiprecision@1.90.0.bcr.1 depends on boost.assert@1.90.0.bcr.1 with compatibility level 0, but boost.math@1.83.0 depends on boost.assert@1.83.0.bcr.1 with compatibility level 108300 which is different. Type 'bazel help mod' for syntax and help.

@renovate renovate bot changed the title chore(deps): update dependency boost.multiprecision to v1.90.0.bcr.1 Update dependency boost.multiprecision to v1.90.0.bcr.1 Apr 8, 2026
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.

0 participants