please tag next version (0.23.0 ?)

[velimir]

No description provided.

[carlisom]

Looks like they bumped it to 1.0.0 internally recently.

c9f1c5d

[velimir]

@tsloughter do you mind tagging it 1.0.0?

[velimir]

@tsloughter @ericbmerritt @lrascao @jwilberding package is bumped to 1.0 according to c9f1c5d do you have any objections to tag repo with 1.0 tag?

[tsloughter]

Sure. I tend not to tag them anymore since I just publish to hex with the version and don't use git dependencies.

[velimir]

thank you @tsloughter !

Tag created: https://github.com/erlware/erlware_commons/releases/tag/1.0.0

[velimir]

@tsloughter I just realised you tagged not a HEAD of the master, but version from Jan 8. Is that possible to tag current master, please?

[tsloughter]

That is 1.0.0, current master hasn't been published yet.

[carlisom]

1.0.0 is broken for project that have not moved to rebar3 yet on and run on erlang 19.1, any ETA for the new release that will fix this issues?

[carlisom]

@tsloughter please see above comment

[tsloughter]

What do you mean? Is there a patch that fixes the issue you have?

[velimir]

@tsloughter I think this one #107 it's been merged already

[paulo-ferraz-oliveira]

4 years in, I don't think tagged/published versions are an issue any more 😄

[velimir]

Don't work for the project any longer. @carlisom do you still need this tagged? I already forgot why we needed this :)

[ferd]

yeah we've kept versioning things, just differently. I'll close this, I don't think this is really relevant anymore.