chore(ci): let release-please own the package versions - #74
Open
jpmewenemesse wants to merge 4 commits into
Open
chore(ci): let release-please own the package versions#74jpmewenemesse wants to merge 4 commits into
jpmewenemesse wants to merge 4 commits into
Conversation
… updated each package tag line the bot should update and updated workflows to considere release workflow
jpmewenemesse
force-pushed
the
chore/release-please
branch
from
August 31, 2026 14:07
17606f4 to
34457cd
Compare
…hanges without packages bump guardrail
jpmewenemesse
force-pushed
the
chore/release-please
branch
from
August 31, 2026 15:24
59dbd38 to
98e0efb
Compare
Contributor
Author
|
#18 must be closed before this one because there is no per package unit release and it does not make any sense |
jpmewenemesse
changed the title
…anging the tag that the next step will use
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The published version of a package is a literal typed into its manifest
Several consequences of a hand-typed version:
-pNNis not a usable version. Under SemVer a hyphen introduces apre-release.
There is no release. Zero git tags, zero GitHub Releases,
.release-please-manifest.jsonis empty. release-please has been installed thewhole time but configured for the wrong repo shape.
What changes
One release-please component per package, following the pattern already used
in
OKDP/helm-charts-utilities. Tags becometrino/v1.0.0, each package getsits own
CHANGELOG.md, andseparate-pull-requests: falsegroups them into asingle release pull request.
release-please writes the OCI tag. The
genericupdater replaces the versionon any line carrying an
x-release-please-versionannotation.Every package restarts at
1.0.0. The existing-pNNtags stay on theregistry; nothing is deleted.
Publishing is triggered by a release, for the released packages only.
release-please.ymlpassespaths_releasedto the package template, whichresolves each released directory to its manifest.
Shared charts are guarded.
airflow,supersetandtrinoembedcharts/internal-secretsby relative path, andjupyterhubembedscharts/oidc-client. release-please assigns commits to packages by directory,and
charts/sits outside every package, so a charts-only change would releasenothing and never reach the registry.
Related Issue
Fixes #68
Type of Change
How to Test
Checklist