chore: warn about deprecated packages instead of failing the update (#24619) (CP: 25.2)#24632
Conversation
…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.
|
|
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? |
…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>
…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>
…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>



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.