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.

Sign up for GitHub

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

Jump to bottom

Add support for automatic Maven Central releases #11237

Closed
nathanklick opened this issue Jan 29, 2024 · 1 comment · Fixed by #11731
Closed

Add support for automatic Maven Central releases #11237

nathanklick opened this issue Jan 29, 2024 · 1 comment · Fixed by #11731
Assignees
@nathanklick
Labels
Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. P1 High priority issue, which must be completed in the milestone otherwise the release is at risk.

Comments

@nathanklick
Copy link
Contributor

nathanklick commented Jan 29, 2024 •
edited
Loading

Description

We need to add support to automatically release the existing artifacts published to Maven Central currently. Additionally, we want to enable publishing of the remaining hedera-* artifacts with the exception of hedera-mono-service and test-clients. No changes required to the com.swirlds artifacts which are being published except to automatically release them. The new block-node folder and it's projects should be published and automatically released as well.
@nathanklick nathanklick mentioned this issue Jan 29, 2024
Closed
@github-project-automation github-project-automation bot moved this to 🆕 New in FST Suite Jan 29, 2024
@nathanklick nathanklick self-assigned this Jan 29, 2024
@nathanklick nathanklick moved this from 🆕 New to 📋 Backlog in FST Suite Jan 29, 2024
@nathanklick nathanklick added P1 High priority issue, which must be completed in the milestone otherwise the release is at risk. Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. labels Jan 29, 2024
@jjohannes jjohannes mentioned this issue Feb 26, 2024
Merged
2 tasks
@jjohannes
Copy link
Contributor

This PR addresses both topics automated publishing and publish all components from services and blocknode.

Contrary to the issue description, I think hedera-mono-services needs to be published as well, because other published components depend on it.

Not published services projects are: cli-clients and test-clients

I had to made a few other decisions were we still might need to adjust something. See comments on: #11731

@nathanklick nathanklick mentioned this issue Apr 4, 2024
Closed
@github-project-automation github-project-automation bot moved this from 📋 Backlog to ✅ Done in FST Suite May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nathanklick nathanklick

Labels
Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. P1 High priority issue, which must be completed in the milestone otherwise the release is at risk.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

build: automate publishing to Maven Central hiero-ledger/hiero-consensus-node
2 participants
@jjohannes @nathanklick