Conversation
The parameter is no longer passed to the package manager by default, so a min-release-age configured in .npmrc or pnpm-workspace.yaml is kept instead of being overridden by the Vaadin default. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Documents vaadin/flow#25173
behavior deviation · flow/configuration · projects that configure
min-release-agefor npm, pnpm, or bun themselvesThe
minimumFrontendPackageAgeDaysparameter used to default to one dayand was always passed on the package manager command line, which beats
every configuration file. A project that had configured a minimum
release age of its own silently got the Vaadin default instead. The
parameter is now unset by default, and the configuration of the package
manager is kept where the project has one. The docs still described the
old behavior and the old default.
Risks:
✅ Docs only. Three pages reworded, no new page and no moved anchor.
Added a "Where the Minimum Age Comes From" section to the npm, pnpm &
bun page, listing the three-step order: the Vaadin parameter, then
the setting of the package manager, then the one-day default.
Described what
0means now: Vaadin adds no restriction of its own,and a minimum release age configured for the package manager still
applies.
Noted that bun can't be asked what it resolves, so a
minimumReleaseAgein abunfig.tomlis not detected.Corrected the parameter reference in the configuration properties and
the Maven plugin pages, where the default was documented as
1.🤖 Generated with Claude Code