game version detection is weird #94
-
so not sure if that is just an error on my side, but I tried the automatic game version detection, and it didn't seem to work correctly
for 1.19.2 it chose 1.19.2, 1.19.3, 1.19.4
for 1.19.3 it chose 1.19.3, 1.19.4
for 1.19.4 it worked
now here comes the weird part on forge it correctly chose the version, although again up to 1.20.2, even when not specified
I saw that 3.3 adds an and for future stuff, is it possible to let the action run in some kind of dummy state, where it will not publish stuff, but tell what version it got? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
With that said, your issues with
Actually, it did. It functioned precisely as described in the README at the time. By default,
This part was indeed a bug, and even As a side note, this bug is already addressed in the latest build of
No, However, had you used
Not at the moment, I'm afraid, but I'm planning to introduce a spec-compliant debug mode in |
Beta Was this translation helpful? Give feedback.
v3.2
has been out of support since May 18th, 2023. It's not even supposed to work at all anymore, as it requires a framework which is no longer available in the GitHub Actions context, namely Node 12. I assume GitHub now forcefully runs outdated Node 12 actions on Node 16. This might work for simple actions, but will undoubtedly causemc-publish
to blow up somewhere down the road in the most unexpected way possible. So, please, do not continue to use it. Update tov3.3
instead.With that said, your issues with
mc-publish
are as outdated asv3.2
is, but I'll still provide some insight into them.Actually, it did. …