linkerd2/jaeger
Alejandro Pedraza c2eb296df3
Automate edge releases (#12175)
* Automate edge releases

Followup to #12132

Now one only needs to tag in order to trigger the release. Please see the updated `RELEASE.md` file for the new instructions.

The last action in the release workflow, `helm-publish`, now runs:

- `bin/helm-bump-edge`: This has been modified to calculate the new edge version by inspecting https://run.linkerd.io/install-edge and bumping the version found there, using a new scheme `YYYY.M.N` (also droppping the `-edge` suffix) shared across all the charts (except for `partials`, `patch` and `linkerd-multicluster-link` which remain static). The `version` entry in the Chart.yaml files no longer needs to be manually updated, and its value is not used for the new version computation, so it was changed to `0.0.0-undefined`. Also note this script validates that the current git tag matches the expected new version.
- `bin/helm-docs`: Called just to update the charts READMEs with the new version. We also still call it in the `helm.yml` workflow to check the values.yaml entries are in sync. So after any change to those values, we still need to manually run `bin/helm-docs`.
- `bin/helm-build package`: As the previous two steps mutate the local checked out source, this no longer validates that there are no uncommited changes.

---------

Co-authored-by: Oliver Gould <ver@buoyant.io>
2024-03-01 09:03:50 -05:00
..
charts/linkerd-jaeger Automate edge releases (#12175) 2024-03-01 09:03:50 -05:00
cmd policy: regenerate Server go bindings (#11920) 2024-01-15 11:09:31 +02:00
injector dev: Update Go to v1.22 (#12114) 2024-02-22 09:39:33 -05:00
pkg/labels jaeger: add data-plane injection checks (#5719) 2021-02-19 00:39:24 +05:30
static Remove old build constraints (#7392) 2021-12-08 14:36:24 -07:00