use changeset marker file for code owner tagging

Author: clavery

.github/CODEOWNERS

@@ -1,7 +1,7 @@
 #GUSINFO:CC Cosmos,B2C CLI and Developer Tools
 *       @clavery
+/.changeset/RELEASE @SalesforceCommerceCloud/b2c-developer-experience
 /packages/b2c-dx-mcp/       @yhsieh1 @patricksullivansf @wei-liu-sf
-/packages/b2c-dx-mcp/src/tools/storefrontnext/    @commerce-emu/cc-sharks
 /packages/b2c-vs-extension/    @wei-liu-sf
 /docs/mcp/       @wei-liu-sf @yhsieh1 @patricksullivansf
 /docs/.vitepress/       @wei-liu-sf @yhsieh1 @patricksullivansf

CONTRIBUTING.md

@@ -99,6 +99,10 @@ You **don't need** a changeset for:
 
 5. Commit the generated `.changeset/*.md` file with your PR
 
+## Release Process
+
+When changesets are merged to `main`, an automated PR is created that bumps versions and updates changelogs. This release PR requires approval from the B2C Developer Experience team before it can be merged. Once merged, packages are published automatically.
+
 ## Notes
 
 - Changesets are optional - maintainers can add them later if needed

package.json

@@ -21,7 +21,7 @@
     "skills:eval": "uv run skills/eval/run_eval.py --model us.anthropic.claude-sonnet-4-6 --verbose",
     "skills:eval:optimize": "uv run skills/eval/run_loop.py --model us.anthropic.claude-sonnet-4-6 --verbose",
     "changeset": "changeset",
-    "version": "changeset version && node scripts/sync-plugin-versions.mjs",
+    "version": "changeset version && node scripts/sync-plugin-versions.mjs && date -u > .changeset/RELEASE",
     "release": "echo 'Releases are handled by CI (publish.yml). Use workflow_dispatch for manual releases.' && exit 1"
   },
   "keywords": [],