fix(DagCalendarTab): improve background color retrieval and loading overlay handling

[MFWhen]

Refactor Playwright page object for the DAG Calendar Tab to use getComputedStyle and web-first assertions

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Generated-by: Github Copilot following the guidelines

• 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, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[jscheffl]

If you make UI changes it is always very good for reviewers to have a "before" and "after" ascreenshot. Or a video showing the change. Can you add this to the PR?

[MFWhen]

If you make UI changes it is always very good for reviewers to have a "before" and "after" ascreenshot. Or a video showing the change. Can you add this to the PR?

Hello,

There are no visual differences in the ui for this code. The change is limited to Playwright e2e test refactoring (locators/waits/assertions).

[choo121600]

yes, no need to include screenshots 👍
However, it looks like the CI is failing—could you please take a look?

[Copilot]

Pull request overview

This PR primarily targets Playwright E2E stability around the DAG Calendar tab by changing how the page object waits for “ready” states and how it derives calendar cell background colors. It also introduces a new developer script intended to automate updates to .github/ branch-related configuration when a new release branch is created.

Changes:

• Refactors DagCalendarTab E2E page-object waits to use Playwright web-first assertions and adjusts calendar readiness logic.
• Changes background color retrieval logic for active calendar cells in E2E tests.
• Adds dev/update_github_branch_config.py to automate updating several .github/ configs and docs when creating a new vX-Y-test branch.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 3 comments.

File	Description
dev/update_github_branch_config.py	New automation script for updating branch-related GitHub configs and docs.
airflow-core/src/airflow/ui/tests/e2e/pages/DagCalendarTab.ts	Updates calendar E2E page-object waiting strategy and active-cell color extraction.

[bbovenzi]

One comment

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker a02fbaa v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[vatsrahul1001]

Manual backport PR #66860 up for review @choo121600 @bbovenzi