Release a v1.0.0

[dominykas]

If there's no objections, I'm going to tag a v1.0.0 next week?

I'll also move a v1 tag there and update all the @main references to @v1.

I intend to just use npm version for the time being to bump versions, and a small workflow to automatically move the major tag forward whenever there's a new tag on HEAD (main).

[ljharb]

How many things are using this so far? it seems like usage should be somewhat extensive before we’re sure it’s ready for v1.

[dominykas]

At the same time, people don't want to use it, because it's @main :)

From the API perspective, the surface is small enough to hopefully not require breaking changes immediately?

[ljharb]

We could release a v0.1.0 tag, at least?

[dominykas]

So from a perspective of someone using it, they'd start at @v0 and have to expect breaking changes (or start at @v0.1 and fiddle with updates) - which is not much different than @main.

[ljharb]

v0.1.0 to v0.1.1 has no breaking changes, only v0.2 or higher would have breaking changes.

[dominykas]

Semver does not prescribe that (i.e. neither does it prescribe that you must bump minor when there's breaking changes, nor that you shouldn't bump minor when there aren't any) - anything goes in pre-v1.

Updated #39 to set a vX.Y when a vX.Y.Z is pushed.

Will poke around to see what people think about using this at @v0.1.

[ljharb]

semver v1 does, as does npm’s semver module which is really the arbiter here given the intended market

In vX.Y.Z, and v0.X.Y, and v0.0.X, X is the major, Y the minor, and Z the patch.

[dominykas]

Released a v0.1.0. The v0 and v0.1 tags got created automatically.

Opened a #40 until there's better automation (or until we split off the private actions into separate repos) - we don't want to keep the @main as it could potentially break things for people importing the action at an older tag.

[wesleytodd]

It looks like this has not happened yet? I was wondering if before we did this would you be open to me making a few changes to expand the feature set of this package a bit more? I have been working on a few workflows which support more and I would love to make those OSS. Just been a while since I have engaged in here and want to make sure we would be aligned on the direction before committing to the work.

[dominykas]

Sure, I'm all for it!