Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure publishing on tag #10

Open
propensive opened this issue Aug 2, 2022 · 1 comment
Open

Configure publishing on tag #10

propensive opened this issue Aug 2, 2022 · 1 comment

Comments

@propensive
Copy link
Owner

We should publish a new release of each library to Sonatype (or alternatively to GitHub) whenever a version is tagged. This should be possible using Irk's publish command, though it has not been widely tested, and has very little error handling.

One way this could work is to have a GitHub action which matches on "pending" tags, e.g. v1.0.4-pending and runs the build/publish script, then removes the v1.0.4-pending tag and adds v1.0.4 to the same commit. This would help to reduce the risk of repeated publishing attempts The script should also automatically ignore/delete v<x>-pending tags if a corresponding v<x> tag already exists, since its existence means that the release has already been published: it's likely that git push --tags would happen occasionally by accident, and we would want to avoid doing multiple releases.

@propensive
Copy link
Owner Author

Every library is now configured to run a publish workflow when its tagged with pending/<some version>, and will replace that tag with release/<some version> in the process. The publish workflow itself does nothing at the moment... that work still needs to be done in Irk, but we're a step closer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant