Skip to content

chore: warn about deprecated packages instead of failing the update (#24619) (CP: 25.2)#24632

Merged
Artur- merged 1 commit into
25.2from
25.2-frontend-dep-script
Jun 16, 2026
Merged

chore: warn about deprecated packages instead of failing the update (#24619) (CP: 25.2)#24632
Artur- merged 1 commit into
25.2from
25.2-frontend-dep-script

Conversation

@Artur-

@Artur- Artur- commented Jun 15, 2026

Copy link
Copy Markdown
Member

The frontend dependency update script previously exited with an error when deprecated packages were detected, preventing the update PR from being created. Now the script always completes and exports the deprecation details via GITHUB_ENV so the workflow appends them as a warning to the commit message of the generated PR.

…24619) (CP: 25.2)

The frontend dependency update script previously exited with an error
when deprecated packages were detected, preventing the update PR from
being created. Now the script always completes and exports the
deprecation details via GITHUB_ENV so the workflow appends them as a
warning to the commit message of the generated PR.
@Artur- Artur- enabled auto-merge (squash) June 15, 2026 15:10
@sonarqubecloud

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

Test Results

 1 449 files  ±0   1 449 suites  ±0   1h 24m 37s ⏱️ - 4m 4s
10 229 tests ±0  10 161 ✅ ±0  68 💤 ±0  0 ❌ ±0 
10 701 runs  ±0  10 632 ✅ ±0  69 💤 ±0  0 ❌ ±0 

Results for commit ccd1821. ± Comparison against base commit 3579d13.

@Artur- Artur- requested a review from caalador June 15, 2026 15:28
@vaadin-bot

Copy link
Copy Markdown
Collaborator

Hi @Artur- and @Artur-, when i performed cherry-pick to this commit to 25.0, i have encountered the following issue. Can you take a look and pick it manually?
Error Message:
Error: Command failed: git cherry-pick 68333e6
error: could not apply 68333e6... chore: warn about deprecated packages instead of failing the update (#24619) (CP: 25.2) (#24632)
hint: After resolving the conflicts, mark them with
hint: "git add/rm ", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

vaadin-bot added a commit that referenced this pull request Jun 16, 2026
…24619) (CP: 25.2) (#24632) (CP: 24.10) (#24643)

This PR cherry-picks changes from the original PR #24632 to branch
24.10.
---
#### Original PR description
> The frontend dependency update script previously exited with an error
when deprecated packages were detected, preventing the update PR from
being created. Now the script always completes and exports the
deprecation details via GITHUB_ENV so the workflow appends them as a
warning to the commit message of the generated PR.
>

Co-authored-by: Artur Signell <artur@vaadin.com>
vaadin-bot added a commit that referenced this pull request Jun 16, 2026
…24619) (CP: 25.2) (#24632) (CP: 24.9) (#24644)

This PR cherry-picks changes from the original PR #24632 to branch 24.9.
---
#### Original PR description
> The frontend dependency update script previously exited with an error
when deprecated packages were detected, preventing the update PR from
being created. Now the script always completes and exports the
deprecation details via GITHUB_ENV so the workflow appends them as a
warning to the commit message of the generated PR.
>

Co-authored-by: Artur Signell <artur@vaadin.com>
vaadin-bot added a commit that referenced this pull request Jun 16, 2026
…24619) (CP: 25.2) (#24632) (CP: 25.1) (#24642)

This PR cherry-picks changes from the original PR #24632 to branch 25.1.
---
#### Original PR description
> The frontend dependency update script previously exited with an error
when deprecated packages were detected, preventing the update PR from
being created. Now the script always completes and exports the
deprecation details via GITHUB_ENV so the workflow appends them as a
warning to the commit message of the generated PR.
>

Co-authored-by: Artur Signell <artur@vaadin.com>
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.

3 participants