Emscripten: Current stable version?

[ilovezfs]

Based on https://github.com/kripken/emscripten/releases and https://github.com/kripken/emscripten/latest I cannot tell if 1.37.5 or 1.37.22 is the current stable version.

Which version should be in Homebrew's stable spec? Thanks!

[kripken]

The first link shows 1.37.22 (the last tagged version), the second gives me a 404?

[ilovezfs]

sorry I meant https://github.com/kripken/emscripten/releases/latest

[kripken]

Hmm, I don't know why it redirects releases/latest to 1.37.5. Both tags and releases show later ones. I guess I don't understand how github decides that.

[kripken]

The only "special" thing about 1.37.5 is that it has some release notes in it. I guess github treats those in a special way?

[ilovezfs]

I guess github treats those in a special way?

@kripken yup. If you create any explicit release, then GitHub will always point releases/latest at the newest explicit release (excluding any of the explicit releases that have the pre-release checkbox checked). So you can resolve this either by making 1.37.22 an explicit release or by deleting https://github.com/kripken/emscripten/releases/tag/1.37.4 and https://github.com/kripken/emscripten/releases/tag/1.37.5

[kripken]

Hmm, but we do want those tags. I guess I could delete them and then create them "non explicitly", on the commandline, is that the difference?

[trzecieu]

Is 1.37.23 somewhere on the horizon?

[kripken]

There is currently a bunch of broken stuff, https://github.com/kripken/emscripten/commit/c23ee7a59f2855f9ec1208d66e13897af139fc97 and https://github.com/kripken/emscripten/commit/93479ecbd390aec4f8a3765fe04bcb365d0b31b2 , but after that's resolved we can tag it.

[ilovezfs]

Deleting the release doesn't delete the tag.

[saschanaz]

It seems undescribed tags are not really 'releases' and adding release notes makes them real 'releases'. (Clicking "Add release note" opens publishing page.)

[ilovezfs]

@saschanaz that's correct. So either you have to always create an explicit release with the GitHub GUI (https://help.github.com/articles/creating-releases/) or the GitHub releases API (https://developer.github.com/v3/repos/releases/), or you have to never do it. Mixing them, sometimes doing it and sometimes not doing it, leads to the current ambiguous situation.

[kripken]

And is there a way to remove the description from a tag, so it becomes a non-explicit release? (Or should we delete it and create it again without a comment?)

[ilovezfs]

You should be able to go to https://github.com/kripken/emscripten/releases/tag/1.37.4 and in the upper right hand corner click the delete button. That shouldn't affect the underlying tag.

[ilovezfs]

Then do the same for https://github.com/kripken/emscripten/releases/tag/1.37.5 and it should all be fixed :)

[kripken]

Thanks! Done, and it looks fixed.

We need to remember to not create tags explicitly on github going forward. Odd github works that way though, seems confusing...

[ilovezfs]

Thanks! :heart: