chore: remove npm package age workaround 25.2 - #10153
Merged
Merged
Conversation
vaadin/flow#25620 excludes @vaadin packages from the minimum frontend package age, so bumping an @NpmPackage version no longer produces a failed snapshot for downstream projects and the 24h block is obsolete. The Flow change is now in 25.2. (cherry picked from commit f0a71e0) Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Flow now passes --config.minimum-release-age-exclude=@vaadin/* to the pnpm install it runs, so the per-module .pnpmfile.cjs that set the same exclusion is redundant on this branch too. (cherry picked from commit 8f6b28b) Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
ZheSun88
approved these changes
Sep 18, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Cherry-pick of: