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

ci: add automated release workflow #138

Closed
lread opened this issue Jan 15, 2023 · 3 comments
Closed

ci: add automated release workflow #138

lread opened this issue Jan 15, 2023 · 3 comments

Comments

@lread
Copy link
Collaborator

lread commented Jan 15, 2023

I don't see one. We should add one.
I can steal from the many other projects I've done this on.
As per the clj-commons team preference, should be triggered by the push of a release tag.

@lread
Copy link
Collaborator Author

lread commented Jan 17, 2023

Before being adopted by clj-commons, I think the pomegranate release was manually created (i.e. from developer's computer) using Clojure Core team's build.pom support. So via mvn commands.

After clj-commons adoption, it seems like a release is manually created via depstar and deployed via deps-deploy.

I'll switch us over to tools.build, automate and document.

@lread
Copy link
Collaborator Author

lread commented Jan 17, 2023

Also, the released pom seems to be pointing to HEAD, I'll make sure it instead points to the git commit of the release.

@lread
Copy link
Collaborator Author

lread commented Feb 5, 2023

Closed by PR #160

@lread lread closed this as completed Feb 5, 2023
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