Update 3.1.56's release date#21537
Conversation
After emscripten-core#21518 landed, the previous 3.1.56 release (emscripten-core#1353) turned out to be broken so we replaced 3.1.56 with the new one (emscripten-core#1360). So here to be precise we update the date of the new 3.1.56 release.
|
I guess we need to force push the tag too? I actually hadn't realized that we had made a tag yes :-/ Force pushing a tag might have repercussions that we are not aware of, but I guess we have no choice now. |
I didn't push emsdk's 3.1.56 tag with the broken release, so that's fine. I will push it with the correct release once emscripten-core/emsdk#1360 lands. |
|
I'm not aware of any workflows here or elsewhere that would mind. I think it's fine. |
After #21518 landed, the previous 3.1.56 release (emscripten-core/emsdk#1353) turned out to be broken so we replaced 3.1.56 with the new one (emscripten-core/emsdk#1360). So here to be precise we update the date of the new 3.1.56 release.