Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor mechanism to fix extension annotations #12503

Open
aalves08 opened this issue Nov 5, 2024 · 0 comments
Open

Refactor mechanism to fix extension annotations #12503

aalves08 opened this issue Nov 5, 2024 · 0 comments
Labels
area/extensions QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@aalves08
Copy link
Collaborator

aalves08 commented Nov 5, 2024

We will need to refactor the current implementation of mechanism to fix extension annotations

yarn publish-pkgs -e -g

since the main usecase for extension developers is that the Helm chart is deployed on the gh-pages branch which doesn't have any package.json, therefore, no alias for the publish-pkgs yarn command/script.

Additionally, it was repackaging extension versions in Elemental that didn't have their Chart.yaml edited

@github-actions github-actions bot added QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this and removed area/extensions labels Nov 5, 2024
@aalves08 aalves08 added this to the v2.11.0 milestone Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/extensions QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

1 participant