Skip to content

Change FAB asset compilation from yarn to pnpm#61958

Open
jscheffl wants to merge 2 commits intoapache:mainfrom
jscheffl:feature/change-yarn-to-pnpm
Open

Change FAB asset compilation from yarn to pnpm#61958
jscheffl wants to merge 2 commits intoapache:mainfrom
jscheffl:feature/change-yarn-to-pnpm

Conversation

@jscheffl
Copy link
Contributor

As a follow-iup of #56456 I'd like to alos remove static compiled assets from repo... and in order to get it streamlined as a first step would propose to switch from yarn to pnpm in fab assets - then all in the repo is consistently using pnpm.

Alongside - as of switching package manager, upgrading all dependencies.


Was generative AI tooling used to co-author this PR?
  • No (please specify the tool below)

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

@boring-cyborg boring-cyborg bot added area:dev-tools area:providers backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch provider:fab labels Feb 15, 2026
@jscheffl jscheffl removed the backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch label Feb 15, 2026
@jscheffl
Copy link
Contributor Author

No backport needed in my view

@potiuk
Copy link
Member

potiuk commented Feb 15, 2026

Indeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants