fixup! chore: Declare workspace packages where they are imported

Author: JPeer264

docs/new-sdk-release-checklist.md

@@ -12,8 +12,7 @@ differ slightly for other SDKs depending on how they are structured and how they
   - [ ] The package has a working unit testing environment
   - [ ] The package builds correctly (inspect `<package>/build` directory)
   - [ ] The package is in the `packages` list of `pnpm-workspace.yaml` and in the `workspaces` list of the root
-        `package.json` (in the same order), and it is in the root `devDependencies` with the version `workspace:*`.
-        `scripts/verify-packages-versions.js` checks this.
+        `package.json` (in the same order). `scripts/verify-packages-versions.js` checks this.
 
 - [ ] Make sure that the `README.md` content is up to date and contains at least:
   - [ ] The correct name + a brief description of the SDK

scripts/verify-packages-versions.js

@@ -59,19 +59,4 @@ must contain the same packages in the same order.
   process.exit(1);
 }
 
-// Configs import workspace packages that they do not declare, so every workspace package must be linked into the
-// root node_modules folder, as Yarn did.
-const missingRootDevDependencies = pkg.workspaces
-  .map(workspace => require(path.join(__dirname, '..', workspace, 'package.json')).name)
-  .filter(name => pkg.devDependencies[name] !== 'workspace:*');
-
-if (missingRootDevDependencies.length > 0) {
-  console.error(`
-[MISSING ROOT DEV DEPENDENCIES]: Every workspace package must be in the \`devDependencies\` of the root package.json
-with the version \`workspace:*\`. Missing:
-${missingRootDevDependencies.join('\n')}
-`);
-  process.exit(1);
-}
-
 process.exit(0);