what is your go-to publish library flow? I curren...
# library-development
a
what is your go-to publish library flow? I currently build the library and release to maven from my macbook but im getting tired of waiting for it to finish, so i have started considering automating it. Maybe have github actions start the publishing process after I create release on github? Might be confusing for people to see the github release but the actual thing not being available yet
e
can create an action triggered from a draft release, or a workflow dispatch action
a
can it then update the draft release to a non-draft?
e
through the api or the
gh
command, sure
I'd manually update it out of draft after some verification but you can do what you like
j
Pushing a tag (which is done by pressing a button with a workflow dispatch). Then automatically • Patches changelog file • Publish to central • Publish the GitHub release
a
Patches changelog file
what do u mean by that?
j
When I do some commit, I update the
[Unreleased]
changelog with the changes, for example
Copy code
## [Unreleased]

### Added

### Changed

### Deprecated

### Fixed

- Sonar crash `File can't be indexed twice`

### Removed

### Updated
A Gradle task patches the changelog based on the version that is going to be published, which means everything inside
[Unreleased]
is moved to a new block with the version and the date
Copy code
## [Unreleased]

### Added

### Changed

### Deprecated

### Fixed

### Removed

### Updated

## [1.2.3] - 2024-10-18

### Fixed

- Sonar crash `File can't be indexed twice`
👍 1