Remove check-latest-npm validation (#57797)

Package publishing via GitHub Actions is currently broken because the actions are not passing the npm version check. This check was introduced when package-lock formats were changing frequently and causing issues. Those difficulties seem to have passed for the most part.
WordPress · Jan 16, 2024 · 598afa7 · 598afa7 · github-actions · Jan 16, 2024
1 parent aac3406
commit 598afa7
Show file tree

Hide file tree

Showing 3 changed files with 1 addition and 137 deletions.
diff --git a/bin/check-latest-npm.js b/bin/check-latest-npm.js
diff --git a/bin/tsconfig.json b/bin/tsconfig.json
@@ -17,7 +17,6 @@
 	},
 	"files": [
 		"./api-docs/update-api-docs.js",
-		"./check-latest-npm.js",
 		"./plugin/config.js",
 		"./plugin/commands/changelog.js",
 		"./plugin/commands/performance.js",

diff --git a/package.json b/package.json
@@ -359,8 +359,7 @@
 			"wp-scripts lint-style"
 		],
 		"package-lock.json": [
-			"npm run lint:lockfile",
-			"node ./bin/check-latest-npm.js"
+			"npm run lint:lockfile"
 		],
 		"packages/*/package.json": [
 			"wp-scripts lint-pkg-json"