Skip to content

feat(utils): Automate generating release testing artifacts#439

Draft
CryptoRodeo wants to merge 11 commits intomainfrom
feat/automate-dynamic-plugins.yaml
Draft

feat(utils): Automate generating release testing artifacts#439
CryptoRodeo wants to merge 11 commits intomainfrom
feat/automate-dynamic-plugins.yaml

Conversation

@CryptoRodeo
Copy link
Contributor

@CryptoRodeo CryptoRodeo commented Feb 26, 2026

  • Add update-rhdh-dynamic-plugin-tags utility that resolves placeholders in dynamic-plugins.yaml with the latest GHCR OCI artifact tags using the GitHub API.
  • Rename update-dynamic-plugins to update-tssc-dynamic-plugin-tags for clarity.
  • Migrate dynamic-plugins.yaml from local dist paths to OCI references.
  • Consolidate testing/README into docs/release-preparation.md and add convenience scripts to package.json
  • Add workflow to auto-generate release testing artifacts.

@CryptoRodeo CryptoRodeo self-assigned this Feb 26, 2026
…ase docs

- Add update-rhdh-dynamic-plugin-tags utility that resolves <tag> placeholders
  in dynamic-plugins.yaml with the latest GHCR OCI artifact tags using the
  GitHub API.
- Rename update-dynamic-plugins to update-tssc-dynamic-plugin-tags
  for clarity.
- Migrate dynamic-plugins.yaml from local dist paths to OCI references.
- Consolidate testing/README into docs/release-preparation.md and
  add convenience scripts to package.json

Signed-off-by: Bryan Ramos <bramos@redhat.com>
@CryptoRodeo CryptoRodeo force-pushed the feat/automate-dynamic-plugins.yaml branch from 02f3119 to a5d10b2 Compare February 26, 2026 19:27
@CryptoRodeo
Copy link
Contributor Author

CryptoRodeo commented Feb 26, 2026

Release testing now should be mostly automated. The base release workflow updates the TSSC-plugin artifacts to the latest release version and now you can update the other artifacts from RHDH like this:

update:rhdh-dynamic-plugins

Then all you have to do is copy the dynamic-plugins.yaml file to RHDH to test locally.

- use `backstage-plugins` by default so it matches what is used in prod
- update and fix wording on registry, images and repositories

Signed-off-by: Bryan Ramos <bramos@redhat.com>
This is mostly used for local testing. The changes done here should get
reverted, not committed.

Signed-off-by: Bryan Ramos <bramos@redhat.com>
- Add MSSV-Backend plugin
- Add force-pull attributes for testing

Signed-off-by: Bryan Ramos <bramos@redhat.com>
It should match what is used to test with RHDH-local

Signed-off-by: Bryan Ramos <bramos@redhat.com>
Signed-off-by: Bryan Ramos <bramos@redhat.com>
Signed-off-by: Bryan Ramos <bramos@redhat.com>
Signed-off-by: Bryan Ramos <bramos@redhat.com>
Signed-off-by: Bryan Ramos <bramos@redhat.com>
@CryptoRodeo CryptoRodeo changed the title feat(utils): add RHDH dynamic plugin tag updater and consolidate release docs feat(utils): Automate release-testing artifacts Feb 26, 2026
@CryptoRodeo CryptoRodeo changed the title feat(utils): Automate release-testing artifacts feat(utils): Automate generating release testing artifacts Feb 26, 2026
@CryptoRodeo
Copy link
Contributor Author

CryptoRodeo commented Feb 26, 2026

Added a release-testing workflow. It'll generate the release artifacts in a PR, including an updated dynamic-plugins.yaml file pointing to the latest plugins (TSSC and RHDH). These artifacts can be used to test everything locally on RHDH.

Release testing should be much easier now, no manual file edits.... 🤞

Same as bash script

Signed-off-by: Bryan Ramos <bramos@redhat.com>
Signed-off-by: Bryan Ramos <bramos@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant