[PR #885] [CLOSED] num-bigint-dig: future incompatibility #1850

New issue

Closed

opened 2026-03-14 15:36:23 +03:00 by kerem · 0 comments

kerem commented

2026-03-14 15:36:23 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/aome510/spotify-player/pull/885
Author: @kn0sys
Created: 12/8/2025
Status: ❌ Closed

Base: master ← Head: kn0sys-dev

📝 Commits (1)

617702d num-bigint-dig: future incompatibility

📊 Changes

1 file changed (+2 additions, -2 deletions)

View changed files

📝 Cargo.lock (+2 -2)

📄 Description

The following warnings were discovered during the build. These warnings are an indication that the packages contain code that will become an error in a future release of Rust. These warnings typically cover changes to close soundness problems, unintended or undocumented behavior, or critical problems that cannot be fixed in a backwards-compatible fashion, and are not expected to be in wide use.

Each warning should contain a link for more information on what the warning means and how to resolve it.

To solve this problem, you can try the following approaches:

Some affected dependencies have newer versions available. You may want to consider updating them to a newer version to see if the issue has been fixed.

num-bigint-dig v0.8.5 has the following newer versions available: 0.8.6, 0.9.0, 0.9.1

If the issue is not solved by updating the dependencies, a fix has to be implemented by those dependencies. You can help with that by notifying the maintainers of this problem (e.g. by creating a bug report) or by proposing a fix to the maintainers (e.g. by creating a pull request):
- num-bigint-dig@0.8.5
- Repository: https://github.com/dignifiedquire/num-bigint
- Detailed warning command: cargo report future-incompatibilities --id 2 --package num-bigint-dig@0.8.5
If waiting for an upstream fix is not an option, you can use the [patch] section in Cargo.toml to use your own version of the dependency. For more information, see:
https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/aome510/spotify-player/pull/885 **Author:** [@kn0sys](https://github.com/kn0sys) **Created:** 12/8/2025 **Status:** ❌ Closed **Base:** `master` ← **Head:** `kn0sys-dev` --- ### 📝 Commits (1) - [`617702d`](https://github.com/aome510/spotify-player/commit/617702d548c7b1403190d4598917729f98283c67) num-bigint-dig: future incompatibility ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `Cargo.lock` (+2 -2) </details> ### 📄 Description The following warnings were discovered during the build. These warnings are an indication that the packages contain code that will become an error in a future release of Rust. These warnings typically cover changes to close soundness problems, unintended or undocumented behavior, or critical problems that cannot be fixed in a backwards-compatible fashion, and are not expected to be in wide use. Each warning should contain a link for more information on what the warning means and how to resolve it. To solve this problem, you can try the following approaches: - Some affected dependencies have newer versions available. You may want to consider updating them to a newer version to see if the issue has been fixed. num-bigint-dig v0.8.5 has the following newer versions available: 0.8.6, 0.9.0, 0.9.1 - If the issue is not solved by updating the dependencies, a fix has to be implemented by those dependencies. You can help with that by notifying the maintainers of this problem (e.g. by creating a bug report) or by proposing a fix to the maintainers (e.g. by creating a pull request): - num-bigint-dig@0.8.5 - Repository: https://github.com/dignifiedquire/num-bigint - Detailed warning command: `cargo report future-incompatibilities --id 2 --package num-bigint-dig@0.8.5` - If waiting for an upstream fix is not an option, you can use the `[patch]` section in `Cargo.toml` to use your own version of the dependency. For more information, see: https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>