Release Please is this nice tool from Google for automating package releases across languages. I don’t have any involvement with it but I have trying it in a rust package and really like it. They support about ~20 languages right now including go, rust, node, and python. I think Julia support would…

I tend to think that a changelog is for users while commit log is for maintainers, and that using commit messages for both (instead of manually writing changelog entries) makes for complicated changelogs that are hard to read for users who just want to know what changed. An commit-based changelog i…

That’s a good point. At the same time this might encourage you to have good, multi-line commit messages that have quality on par with changelogs, rather than small messages like "update feature X". But to me the changelog automation is just gravy on top of the release infrastructure. I also really …

This would be quite nice for my DataToolkit.jl packages I think. It’s exactly the case of multiple packages in a single repo, and if you look at the commit history you can see it’s all scoped conventional commits.

I have no insights about this tool but [image] MilesCranmer: I think it could be used to wrap JuliaRegistrator and automatically trigger new registrations. and [image] MilesCranmer: Release please works by creating release PRs that you merge. Then other CI tools would run to actually pu…

[image] GunnarFarneback: seems contradictory? They are slightly different things. The “release PR” feature of Release Please is a pull request that updates the changelog and version information and kicks off the packaging CI. So for Julia it could update Project.toml. Then the act of merging…

[image] MilesCranmer: Then the act of merging Release Please’s PR will trigger CI to run specific to the language. In Julia’s case, that’s what would trigger JuliaRegistrator to run and register the package. That sounds largely orthogonal to what Relase Please helps you do and would be the sa…

[image] jmair: Sounds like a good project proposal for the JuliaCon 2024 hackathon ! :metal: [image] GunnarFarneback: That sounds largely orthogonal to what Relase Please helps you do and would be the same if you created the PR manually or with some other tool. I’m not sure what you m…

I might be misunderstanding things but from what I read Release Please automates a PR for you and whatever happens in CI after you merge that PR has nothing to do with Release Please.

So the PR bumps the version (i.e., in Project.toml) according to SemVer – which is parsed from Conventional Commits, and also updates the CHANGELOG.md according to the feat for new features, fix for fixes, feat! for breaking features, etc. After merging, there’s another CI step (part of Release Ple…

Release Please: a tool for multi-package multi-language releases

Tooling

jmair July 1, 2024, 6:57am 7

Sounds like a good project proposal for the JuliaCon 2024 hackathon!

3 Likes

Topic		Replies	Views
[ANN] Easier release automation with "Release Please" CI tool Package Announcements package	17	557	March 31, 2026
JuliaRegisterChangelog, a workflow for automatic package registration and changelogs based on Conventional Commits Package Management release , workflow , registry , tagbot	3	257	April 14, 2026
New automerge requirement: Release notes required for breaking package releases Package Announcements general-registry , registryci	50	1812	January 2, 2025
[ANN] TagBot: Creates tags and releases for your Julia packages when they're registered Package Announcements tagbot	53	6106	January 6, 2020
Make breaking change releases easier to handle. Add release notes to tags via JuliaRegistrator Package Management tagbot	5	437	August 28, 2023

Release Please: a tool for multi-package multi-language releases

Related topics