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.

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

Update Rust crate serde_yaml to v0.9.34 #1286

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 25, 2024

This PR contains the following updates:

Package Type Update Change
serde_yaml dependencies patch =0.9.33 -> =0.9.34

Release Notes

dtolnay/serde-yaml (serde_yaml)

v0.9.34

Compare Source

As of this release, I am not planning to publish further versions of serde_yaml as none of my projects have been using YAML for a long time, so I have archived the GitHub repo and marked the crate deprecated in the version number. An official replacement isn't designated for those who still need to work with YAML, but https://crates.io/search?q=yaml\&sort=relevance and https://crates.io/keywords/yaml has a number of reasonable-looking options available.


Configuration

📅 Schedule: 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.

Copy link
Contributor Author

renovate bot commented Mar 25, 2024

⚠ 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: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.9.34
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?

  [email protected]+deprecated

@renovate renovate bot force-pushed the renovate/serde_yaml-0.x branch 11 times, most recently from e2e0b31 to 006d096 Compare April 2, 2024 01:28
@renovate renovate bot force-pushed the renovate/serde_yaml-0.x branch 10 times, most recently from 93e9366 to 0fba4ce Compare April 15, 2024 09:00
@renovate renovate bot force-pushed the renovate/serde_yaml-0.x branch from 0fba4ce to 082bb71 Compare April 16, 2024 15:48
@renovate renovate bot force-pushed the renovate/serde_yaml-0.x branch from 082bb71 to caa9dd3 Compare June 26, 2024 23:05
Copy link
Contributor Author

renovate bot commented Jun 26, 2024

⚠️ 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: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.9.34
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?

  [email protected]+deprecated

@renovate renovate bot force-pushed the renovate/serde_yaml-0.x branch from caa9dd3 to e4ac008 Compare June 26, 2024 23:17
@renovate renovate bot force-pushed the renovate/serde_yaml-0.x branch 2 times, most recently from 86d17b4 to 61417a3 Compare July 22, 2024 11:04
@renovate renovate bot force-pushed the renovate/serde_yaml-0.x branch from 61417a3 to 067fc74 Compare July 29, 2024 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants