Skip to content

Move artifact promotion from SharedActions to GradleUtils #20

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

Open
Jonathing opened this issue Mar 16, 2025 · 0 comments · May be fixed by #23
Open

Move artifact promotion from SharedActions to GradleUtils #20

Jonathing opened this issue Mar 16, 2025 · 0 comments · May be fixed by #23
Assignees

Comments

@Jonathing
Copy link
Member

Currently, SharedActions is completely responsible for promoting artifacts that have been published to our maven. While it's been working well, this can cause an issue if there is a problem with publishing or if the artifact has changed in some unexpected way that wasn't accounted for in the related project's repository. So, the solution would be to move this promotion to GradleUtils and add it as a finalization of the publishing to forge maven.

This also has the added benefit of alerting us to any issues caused by artifact promotion failures, instead of us having to find out late when a new artifact isn't being promoted on the files site.

@Jonathing Jonathing self-assigned this Mar 16, 2025
@Jonathing Jonathing linked a pull request Apr 20, 2025 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant