Update windows-core requirement from >=0.50, <=0.51 to >=0.50, <=0.52

[dependabot]

Updates the requirements on windows-core to permit the latest version.

Release notes

Sourced from windows-core's releases.

0.51.1

This is mainly for publishing an update of the windows-bindgen crate but also fixes a few minor readme and version issues to avoid confusion.

• The windows and windows-core crates are updated to 0.51.1 to update the readme but are otherwise unchanged.
• The windows-targets crate and arch-specific crates are updated to 0.48.3 to update the readme and bring the lib file names in line with the crate version.

Those are all semver-compatible updates.

• The windows-bindgen crate is updated to 0.51.1 and includes the new riddle-based metadata processing capabilities and is compatible with the windows and windows-core crates.
• The windows-metadata crate is updated to 0.51.1 and includes many refinements but is largely for internal use.

Those are major breaking changes.

The windows-sys crate will not be updated at this time.

What's Changed

• Make riddle available as a library by @​kennykerr in microsoft/windows-rs#2609
• Improve windows-bindgen for std usage by @​kennykerr in microsoft/windows-rs#2610
• Version 0.51.1 by @​kennykerr in microsoft/windows-rs#2611

Full Changelog: microsoft/windows-rs@0.51.0...0.51.1

Commits

• f18811c Version 0.51.1 (#2611)
• 8f47253 Improve windows-bindgen for std usage (#2610)
• f1b1edd Make riddle available as a library (#2609)
• 78a0dbe Version 0.51.0 (#2605)
• f0c7eda Metadata processing improvements (#2598)
• 53eed86 Metadata parsing improvements (#2592)
• a20dbba Riddle dialects (#2586)
• f31b44e Prefer explicit casts (#2582)
• 3cb54c7 Metadata parsing and indexing improvements (#2581)
• a98ae05 Update Win32 and WDK metadata (#2573)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[astraw]

I don't understand this. It updates dependencies to allow windows-core 0.52, but that's not released as of now. The most recent release of windows-core is 0.51.1, which is allowed currently.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[Kijewski]

I am not sure how the expression <=0.51 is parsed by cargo and dependabot. Is it the same as <=0.51.* or <=0.51.0? From experience I can tell that dependabot does not always understand version ranges for python's requirements.txt.

Maybe we should replace the expression with < 0.52 to be sure? That should be understood the same and correctly by both dependabot and cargo.

[astraw]

I checked and our CI is building with windows-core 0.51.1 so Cargo parses it as <=0.51.*. Given this PR, yes, I guess dependabot uses <=0.51.0.

Maybe we should replace the expression with < 0.52 to be sure? That should be understood the same and correctly by both dependabot and cargo.

I'm not sure - will e.g. alpha versions of 0.52 be included by Cargo? We don't want that. I'm happy to just keep things as they are and close PRs from dependabot affected by this.

[Kijewski]

Thanks for verifying! Then cargo is consistent in this regard.

Cargo never selects a pre-release. You always have to type the exact version to get an alpha version, i.e. 0.1.0-alpha.0 and 0.1.0-alpha.1 are not version compatible with one another in either direction, or with any other version.

But given that dependabot said "OK, I won't notify you again about this release, but will get in touch when a new version is available", I guess we can keep the current version requirement. If dependabot opens a PR for windows-core 0.51.2, we can close it again, and for 0.52.0 we can update it requirement manually.