build(edge3): regenerate compiled assets after vite/vitest bump #55622
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boring-cyborg
bot
added
area:providers
provider:edge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
build(edge3): regenerate compiled assets after vite/vitest bump
PR for #55562
This is a small follow-up to the UI toolchain upgrade.
Supersedes / replaces: #55593 (that PR was auto-closed during rebase/force-push).
Why
#55593 upgraded the UI toolchain (Vite → v7, Vitest → v3; requires Node ≥ 22).
After that change, the Edge3 provider’s compiled UI assets needed to be rebuilt so the published bundle and hash match the new toolchain.
What changed
Only generated artifacts in the Edge3 provider (no source changes):
providers/edge3/src/airflow/providers/edge3/plugins/www/dist/main.umd.cjsproviders/edge3/www-hash.txtHow it was produced
Built via the prek hook: