fix: publish the vite build so the package ESM entry resolves

The exports map pointing at dist/index.mjs and dist/index.cjs has been on
main since the vite migration, but npm latest is still 2.18.0 and ships the
old dual-.js bundle that Node cannot load. Every commit since the v2.18.0 tag
used a type outside the default release rules, so semantic-release ran green
and published nothing.

Declare the plugin list so commit-analyzer can treat build changes and
dependency bumps as patch releases. Shipped output and vendored dependencies
reach users, so a change to either warrants a version.

Author: wescopeland

package.json

@@ -70,6 +70,27 @@
     "branches": [
       "main",
       "next"
+    ],
+    "plugins": [
+      [
+        "@semantic-release/commit-analyzer",
+        {
+          "releaseRules": [
+            {
+              "type": "build",
+              "release": "patch"
+            },
+            {
+              "type": "chore",
+              "scope": "deps",
+              "release": "patch"
+            }
+          ]
+        }
+      ],
+      "@semantic-release/release-notes-generator",
+      "@semantic-release/npm",
+      "@semantic-release/github"
     ]
   },
   "publishConfig": {