Prepare v1 RC 3

Author: TDanks2000

CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 1.0.0-rc.3
+
+### Changed
+
+- Refreshes the V1 release candidate from the corrected publish workflow so prerelease publishes resolve to the npm `next` dist-tag by default.
+- Keeps the generated manifest examples aligned with the next prerelease version.
+
 ## 1.0.0-rc.2
 
 ### Changed

docs/manifest.md

@@ -23,10 +23,10 @@ Breaking manifest migrations require a documented migration path before release.
 
 ```json
 {
-  "$schema": "https://unpkg.com/create-electrobun-stack@1.0.0-rc.2/docs/ces.schema.json",
-  "version": "1.0.0-rc.2",
+  "$schema": "https://unpkg.com/create-electrobun-stack@1.0.0-rc.3/docs/ces.schema.json",
+  "version": "1.0.0-rc.3",
   "createdAt": "2026-05-10T00:00:00.000Z",
-  "reproducibleCommand": "bunx create-electrobun-stack@1.0.0-rc.2 my-app --template minimal ...",
+  "reproducibleCommand": "bunx create-electrobun-stack@1.0.0-rc.3 my-app --template minimal ...",
   "projectName": "my-app",
   "packageName": "my-app",
   "appIdentifier": "dev.electrobun.myapp",

docs/v1-plan.md

@@ -187,7 +187,7 @@ Exit criteria:
 
 Goal: publish a real prerelease and use it like a user.
 
-- Bump to a fresh RC version. The current prepared candidate is `1.0.0-rc.2` because `v1.0.0-rc.1` was tagged before the Phase 1-5 corrections.
+- Bump to a fresh RC version. The current prepared candidate is `1.0.0-rc.3` because `v1.0.0-rc.2` was released before the corrected prerelease npm dist-tag workflow could publish.
 - Publish under an npm prerelease tag, for example `next`.
 - Test the published prerelease with:
   - `npm create electrobun-stack@next my-app`,

package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-electrobun-stack",
-  "version": "1.0.0-rc.2",
+  "version": "1.0.0-rc.3",
   "description": "Scaffold a modern Electrobun desktop app.",
   "type": "module",
   "main": "./dist/index.mjs",