Skip to content

Conversation

@mgol
Copy link
Member

@mgol mgol commented Sep 23, 2025

package-lock.json versions 2 & 3 keep version in two fields - a top-level version one and a deep packages[ "" ].version one. Update both.

#117 needs to land first to fix CI.

@mgol mgol self-assigned this Sep 23, 2025
@timmywil
Copy link
Member

timmywil commented Oct 13, 2025

I forget where this is in the process, but an npm install would update the version in the lock file as well. Also, that may be more future-proof if there are multiple places it needs to be updated. Use npm version without committing.

@timmywil
Copy link
Member

Please add Needs Review back when updated.

module.exports = function( Release ) {

Release.define( {
_jsonFiles: [ "package.json", "package-lock.json", "bower.json" ],
Copy link
Member Author

Choose a reason for hiding this comment

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

I thought I first need to remove version from UI's bower.json but I do not - the version field was only added on tagged releases, on main it's not there.

`package-lock.json` versions 2 & 3 keep `version` in two fields - a top-level
`version` one and a deep `packages[ "" ].version` one. Update both.
@mgol
Copy link
Member Author

mgol commented Jan 12, 2026

I did a test release of jQuery UI and I verified the release still works and the version is properly updated in the lockfile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants