Update pulldown-cmark version#59349
Conversation
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
|
☔ The latest upstream changes (presumably #57810) made this pull request unmergeable. Please resolve the merge conflicts. |
e2539c7 to
56771eb
Compare
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Why was the atomics doc change included in this PR? |
|
I saw the error and I removed the useless full path. :-. |
56771eb to
633622e
Compare
633622e to
9c605e8
Compare
|
And fixed the error. |
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
|
... Or maybe not... |
Looks like the test |
|
☔ The latest upstream changes (presumably #59464) made this pull request unmergeable. Please resolve the merge conflicts. |
|
Ping from triage, @GuillaumeGomez, you need to rebase and also see #59349 (comment). |
|
I also need to wait for a new pulldown-cmark release. |
|
If we need to wait for upstream pulldown to update, should we even keep this PR open? |
|
As you prefer? |
|
If we expect it to be a while before the crate updates (and if we require the update to fix the test issue), i would rather close this PR so we don't have it dangling. |
|
Let's close it then. |
|
pulldown-cmark 0.4.1 was published today: https://crates.io/crates/pulldown-cmark |
|
Thanks for the notification. I'll make another PR. |
Fixes #59194.
r? @QuietMisdreavus