From a792968214c173badd95db2c937349b791a7ef59 Mon Sep 17 00:00:00 2001 From: LGLabGreg Date: Wed, 5 Aug 2026 18:20:34 +0100 Subject: [PATCH] chore: drop minimumReleaseAgeExclude entries for next 16.3.0 next@16.3.0 published 2026-08-03 and now clears pnpm's release-age gate on its own, so the exact-version waivers are dead weight. pnpm install leaves the lockfile untouched and does not re-add them. --- pnpm-workspace.yaml | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml index ae637ef..4133b7d 100644 --- a/pnpm-workspace.yaml +++ b/pnpm-workspace.yaml @@ -5,18 +5,6 @@ packages: allowBuilds: sharp: true -minimumReleaseAgeExclude: - - '@next/env@16.3.0' - - '@next/swc-darwin-arm64@16.3.0' - - '@next/swc-darwin-x64@16.3.0' - - '@next/swc-linux-arm64-gnu@16.3.0' - - '@next/swc-linux-arm64-musl@16.3.0' - - '@next/swc-linux-x64-gnu@16.3.0' - - '@next/swc-linux-x64-musl@16.3.0' - - '@next/swc-win32-arm64-msvc@16.3.0' - - '@next/swc-win32-x64-msvc@16.3.0' - - next@16.3.0 - onlyBuiltDependencies: - esbuild - sharp