chore: add dry-run before publishing to avoid mistakes (#5183)

Author: nmerget

scripts/github/publish-npm.js

@@ -87,10 +87,24 @@ for (const REGISTRY of registries) {
 		process.exit(1);
 	}
 
-	for (const PACKAGE of packages) {
-		console.log(`⤴ Publish ${PACKAGE} with tag ${TAG} to ${REGISTRY}`);
-		execSync(
-			`npm publish --tag ${TAG} db-ux-${PACKAGE}-${VALID_SEMVER_VERSION}.tgz --provenance`
-		);
+	// We do a try-run to check if everything is alright
+
+	for (const step of ['dry-run', 'provenance']) {
+		for (const PACKAGE of packages) {
+			console.log(
+				`⤴ (${step}) Publish ${PACKAGE} with tag ${TAG} to ${REGISTRY}`
+			);
+			try {
+				execSync(
+					`npm publish --tag ${TAG} db-ux-${PACKAGE}-${VALID_SEMVER_VERSION}.tgz --${step}`
+				);
+			} catch (error) {
+				console.error(
+					`❌ ${step} publish failed for ${PACKAGE} with tag ${TAG} to ${REGISTRY}`
+				);
+				console.error(error.message || error);
+				process.exit(1);
+			}
+		}
 	}
 }