Mithril.js: Latest release is v0.2.3 latest tag is v1.0.1

[winksaville]

Is there a reason for not marking the v1.0.x tags as releases?

[pygy]

I suppose you mean GH releases...

[winksaville]

@pygy, yes

[isiahmeadows]

Consider our laziness as the driving reason - we already have npm, why duplicate the work? :wink:

[FibreFoX]

@isiahmeadows I came recently to mithril (and it really seems to be nice), but I don't use NPM for everything, especially when I don't require it. As mithril works without NPM, and does not require it, and for pre-1.0 version github-releases were provided, I personally would see this as a bad sign, makes it feel like mithril isn't being updated. "Oh, a new tool, lets check when the last commit have been made ... nice, just yesterday. Now lets check how often they are releasing ... oh, thats a bummer, no release, lets check a different tool", and there you go mister potential mithril-user.

[isiahmeadows]

In general, our community has very heavily relied on package management. And for what it's worth, even Angular doesn't document their releases via GitHub - they just use Git tags like most others.

As I don't see anything actionable with this (we already use Git tags, and we advertise updates elsewhere), I'm going to close this.

[winksaville]

What about automatically creating a release tag when you publish to npm? Apparently it's possible using the GitHub API if you'd like I can try to make a PR.

@isiahmeadows, BTW I just looked at that link to Angular and it looks to me both Angular Releases and Tags are the same and up to date, but maybe I'm misinterpreting what I'm seeing.

[isiahmeadows]

@winksaville You're probably misinterpreting what you're seeing. All those are tags, not releases. To see what I mean, compare this tag with this release.

[pygy]

I don't know what I'm doing with j2c, but GH marks every vX.Y.Z tag as a release automatically... There's no extra info though.

I have "prepublish": "(in-publish && git push --follow-tags) || not-in-publish", in my package.json (where in-publish asserts that we really did npm publish, not npm install.

Pinging both @tivac (for his automation know-how) and @lhorie (who does the releases): would you mind having it added?

[pygy]

@isiahmeadows We don't even have Angular-like stub releases in Mithril... It is better than nothing. Oh, now I see... We have the stubs, hidden unless you click the "Show N newer tags" button, because we have actual releases.