chore: remove pnpm release age exclude config - #10125
Merged
Merged
Conversation
vaadin/flow#25620 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. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
DiegoCardoso
approved these changes
Sep 15, 2026
sissbruecker
enabled auto-merge
September 15, 2026 10:25
|
sissbruecker
added a commit
that referenced
this pull request
Sep 15, 2026
…0127) This PR cherry-picks changes from the original PR #10125 to branch 25.3. --- #### Original PR description > Follow-up to #10118 > Related to vaadin/flow#25620 > > - Removed the `.pnpmfile.cjs` from all 52 integration test modules, which excluded `@vaadin/*` packages from pnpm's minimum release age check > - Removed the step in `scripts/mergeITs.js` that copied that file into the merged IT module > - Removed the `!**/.pnpmfile.cjs` entry from `vaadin-spreadsheet-flow-parent/.gitignore`, which only existed to un-ignore the file from the `.pnpm*` pattern > > Flow now passes `--config.minimum-release-age-exclude=@vaadin/*` to the pnpm install it runs, so the project-level exclusion is redundant. Every pnpm install in this repository goes through Flow — the IT builds, `jetty:run`, and `scripts/wtr.js` — so nothing else relies on it. The files stay on 25.2, which builds against a Flow version without the exclusion. > Co-authored-by: Sascha Ißbrücker <sissbruecker@vaadin.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
ZheSun88
pushed a commit
that referenced
this pull request
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
3 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.
Follow-up to #10118
Related to vaadin/flow#25620
.pnpmfile.cjsfrom all 52 integration test modules, which excluded@vaadin/*packages from pnpm's minimum release age checkscripts/mergeITs.jsthat copied that file into the merged IT module!**/.pnpmfile.cjsentry fromvaadin-spreadsheet-flow-parent/.gitignore, which only existed to un-ignore the file from the.pnpm*patternFlow now passes
--config.minimum-release-age-exclude=@vaadin/*to the pnpm install it runs, so the project-level exclusion is redundant. Every pnpm install in this repository goes through Flow — the IT builds,jetty:run, andscripts/wtr.js— so nothing else relies on it. The files stay on 25.2, which builds against a Flow version without the exclusion.