[release-2.9] build-extension-catalog fails

[masap]

Summary

Fixes #12993.

Occurred changes and/or fixed issues

Empty tagged_release causes trailing error.

Run yarn parse-tag-name  12645625456 "catalog"
yarn run v1.22.22
warning package.json: No license field
$ ./node_modules/@rancher/shell/scripts/extension/parse-tag-name 12645625456 catalog Parse tag name - evaluating release tag 12645625456 release tag doesn't match any chart tag: 12645625456. Check your pkg/<!-YOUR-EXT-> folders and corresponding versions to complete the match invalid run-id "catalog"
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. error Command failed with exit code 1.
Error: Process completed with exit code 1.

Technical notes summary

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

[richard-cox]

Checklist needs filling out

@aalves08 same question here, do the builds now reference branches or use a baked in version originating from main? would this change need to go into all branches?

[masap]

I confirmed master and release-2.8 branch does not have this issue.

[aalves08]

I don't know how we've missed this... 🤦 I'll need to add tests for the workflows on the creators. The issue to track it exists already.

It's not the only branch that has problems @masap . In master, for example, we are missing the tagged_release as well.

If you don't mind @masap , I am going to close this PR a create all the PRs needed with the bump of the creators version as well. It all needs to go in so that I can release new versions for each branch.

@richard-cox both shell and creators packages are per branch, meaning that if you create an extension targeting legacy-v1 tag (rancher 2.8.x), https://extensions.rancher.io/extensions/next/extensions-getting-started#creating-an-extension-for-legacy-versions you will get created a system that is reliant on the branch release-2.8, with the necessary compatible files and the workflows that we ship from that creator will target reusable workflows in release-2.8 branch.

Same analogy goes for legacy-v2 tag (rancher 2.9.x) and release-2.9 branch + latest tag (rancher 2.10.x and above) and master branch

[masap]

If you don't mind @masap , I am going to close this PR a create all the PRs needed with the bump of the creators version as well. It all needs to go in so that I can release new versions for each branch.

Ok, no problem.