Closed mciantyre closed 4 years ago
See here. It hasn't generated any pre-releases, as expected.
I'm re-thinking this pre-release job. It's going to result in us having many, many releases. I'll probably remove it, rather than fix it.
Instead, I'll add a workflow to package our specific, intended releases. It should work like this:
v0.1.2
We can do these after specific, notable milestones in development.
We could also do this building manually, but it's less error-prone to have an automated system do it for us.
Created a test release, v0.0.0-test0, and the new workflow worked. See the [releases page] for the output.
v0.0.0-test0
Here is the successful job!
See here. It hasn't generated any pre-releases, as expected.
I'm re-thinking this pre-release job. It's going to result in us having many, many releases. I'll probably remove it, rather than fix it.
Instead, I'll add a workflow to package our specific, intended releases. It should work like this:
or through GitHub. He assigns a tag, likev0.1.2
, to the release.We can do these after specific, notable milestones in development.
We could also do this building manually, but it's less error-prone to have an automated system do it for us.