Skip to content

Conversation

@NotMyFault
Copy link
Member

The change proposed updates the couple of dependencies to their maintained LTS versions, instead of shipping a version that is ~8 years out of date (and 6 years out of maintenance).

Copy link
Member

@basil basil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two paths forward: (1) accepting the suggestion made previously to remove the version numbers from this file, or (2) updating the version numbers in this file and filing downstream PRs for all consumers to stop setting custom versions in favor of the global versions being proposed in this PR.

@NotMyFault NotMyFault changed the title Update Node from 4.0.0 to 16.17.1 and npm from 2.13.1 to 8.19.2 Remove node.version and npm.version defaults Oct 10, 2022
Co-authored-by: Basil Crow <[email protected]>
@NotMyFault
Copy link
Member Author

Your proposal makes more sense then, given almost every consumer did already define their own properties.

Do we want to label this as breaking nevertheless? In case this affects some closed source consumers using the default value, which didn't occur in the search?

@NotMyFault NotMyFault requested a review from basil October 10, 2022 19:31
@basil basil merged commit 03913f7 into jenkinsci:master Oct 10, 2022
@basil basil added the breaking label Oct 10, 2022
@NotMyFault NotMyFault deleted the build/master/node branch October 10, 2022 20:56
@NotMyFault NotMyFault restored the build/master/node branch October 10, 2022 20:56
@NotMyFault NotMyFault deleted the build/master/node branch October 10, 2022 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants