fix(scripts): handle --force-registry flag when no bump commits exist

Previously when no version bump commits were found, the script would exit early before checking the --force-registry flag. Now it checks for the flag and attempts to publish at HEAD even when there are no bump commits.

Author: jdalton

scripts/publish-npm-packages.mjs

@@ -585,6 +585,14 @@ async function main() {
 
     if (bumpCommits.length === 0) {
       logger.info('No version bump commits found')
+      // If --force-registry is set, still try to publish at HEAD.
+      if (forceRegistryFlag) {
+        logger.log(
+          '\nForce-registry flag is set, checking HEAD for unpublished packages...',
+        )
+        const headSha = await getCommitSha('HEAD')
+        await publishAtCommit(headSha)
+      }
       return
     }