Correct version guard for dune formatting change#11486
Conversation
|
Sounds fair enough, especially as it would be nice to release 3.18 soon-ish. Can you promote the failures? |
I promoted some of the failures, but I cannot reproduce the rest in my machine. Can you help me by pushing the corrected test files to this branch? Thanks! |
f2434d4 to
e321b7a
Compare
|
I was confused about this as well as it worked for me too. But the issue was that I had too old of a |
Signed-off-by: Nicolás Ojeda Bär <n.oje.bar@gmail.com>
e321b7a to
f42b812
Compare
f42b812 to
11d0f1c
Compare
Thanks, now almost everything passes. However there's still one failure that looks unrelated. Do you confirm? |
Leonidas-from-XIV
left a comment
There was a problem hiding this comment.
Yes, the Dynlink failure happens (more than) occasionally but is unrelated.
|
Thanks for the confirmation! |
Signed-off-by: Nicolás Ojeda Bär <n.oje.bar@gmail.com>
Signed-off-by: Nicolás Ojeda Bär <n.oje.bar@gmail.com>
The formatting change introduced in #10892 was guarded under version 3.18 in #11175 to avoid breaking existing users of the unversioned
dune format-dune-file(see #10892 (comment)). However, its replacement action(format-dune-file)introduced #11166 will only appear in 3.18, so the format change should in fact be guarded under version 3.19 to give users time to adapt.