-
Notifications
You must be signed in to change notification settings - Fork 489
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
Fix for windows-targets::link
doc compatibility
#2868
Conversation
windows-target
link doc compatwindows-targets::link
doc compat
windows-targets::link
doc compatwindows-targets::link
doc compatibility
Not sure whether it will impact anyone in practice, but I've yanked |
I'm seeing this exact error using |
I noticed that Cargo doesn't reliably grab the latest when an older version is yanked that you happen to already have downloaded. My issue was resolved after I forced a download of 0.52.2 and after that it just worked as before. For example, this will force your local cache to get updated: [dependencies.windows-targets]
version = "0.52.2" After running Cargo, you can remove this dependency and its cache should be updated. This seems like a Cargo or crates.io bug but I'm not sure. |
Presumably you can also run |
yes, if a But this does not solve my issue. My problem occurred when pushing a branch that triggered a CI: since I don't have a lock file committed, cargo will use the latest versions of all (semver compatible) dependencies. Meaning it will use I then tried to downgrade to 0.52.0. I did report that it worked, but actually I get a different error:
On my local windows vm I tried to update to 0.52.2 explicitly but surprisingly it failed:
Modifying the
This is mysterious... |
You may also be hitting this issue: #2870 |
I just checked my logs and CI was using 0.52.1 🤔 I guess an updated version (0.52.3?) will be released with the linking issue fixed (#2870). I'll see if that version helps out. |
Yep 0.52.3 is on its way. |
0.52.3 has now been published - let me know if you have any further issues. |
I've relaunched my CI job (still without lock file) and it picked up 0.52.3; it now builds without issue. Thanks a lot!! 👍 |
@kennykerr It seems since this was shipped I'm seeing doc failures for
|
Just making sure we preserve link macro compatibility in some cases as shown in this test failure:
https://github.com/microsoft/windows-rs/actions/runs/8005925420/job/21866485024