Add mechanism to remove published extensions #137
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.
Fixes rancher/dashboard#13645
manifest.json
main
branch is always protected and it causes the workflow to fail (although it created the PR which is the important part)To test:
run this branch locally and do
./scripts/sync-charts
/charts
calleddummy-ext
, so that we can check the resilience of the script when a folder exists but no entries are found onmanifest.json
elemental
version3.0.1-rc.2
and check if the sync mechanism still works finemanifest.json
to see the removal part in actionindex.yaml
, especially after the removal of a given extension versionFixes rancher/dashboard#13717
extensions catalog
automatically after the PR to update the helm chart gets merged. It will get the "latest" version from the docker hub repo and bump the minor version so that we can keep all catalog images publishedextensions catalog
job is finished -> test done in https://github.com/aalves08/test-release-tag/actions/runs/17123969356/job/48571230902?pr=3 + https://github.com/aalves08/test-release-tag/releases/tag/v2.12.1