create-yosr-seed 0.1.0-alpha.2 → 0.1.0-alpha.4

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # create-yosr-seed
 
+## 0.1.0-alpha.4
+
+### Patch Changes
+
+- A fresh Yosr Seed project already contains the Next.js agent block, so the first dev server does not edit AGENTS.md. The closing suggestion asks for a delete button on each note. The initial commit step is labeled Initial commit. Note times show a local date and time, and the README gives the alpha install command.
+- The create command depends on Yosr Seed 0.1.0-alpha.4.
+
+## 0.1.0-alpha.3
+
+### Patch Changes
+
+- A Yosr Seed first run checks the machine before asking, shows plain labels and a summary, and adds `doctor`, `info`, and a profile menu.
+- Ctrl+C during a Yosr Seed check records the run as not green, and later checks do not start.
+- The create command depends on Yosr Seed 0.1.0-alpha.3.
+
 ## 0.1.0-alpha.2
 
 ### Patch Changes

package/README.md

@@ -4,6 +4,11 @@ Creates a Yosr Seed project. Binary: `create-yosr-seed`. It is the same flow as
 
 ```text
 npx create-yosr-seed@alpha
+npx create-yosr-seed@<version>
 ```
 
+`@alpha@<version>` is invalid. Use `@alpha` or `@<version>`.
+
+`yosr-seed doctor` prints the preflight checks and versions. `yosr-seed info` reads `.seed/` inside a generated project. `yosr-seed profile` with no subcommand opens an arrow menu on a terminal and prints usage on a pipe.
+
 Commands and flags are in the [repository README](https://github.com/getyosr/yosr-seed#readme).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-yosr-seed",
-  "version": "0.1.0-alpha.2",
+  "version": "0.1.0-alpha.4",
   "description": "Create a Yosr Seed project. Forwards to yosr-seed create.",
   "license": "MIT",
   "repository": {
@@ -20,6 +20,6 @@
     "node": ">=24"
   },
   "dependencies": {
-    "yosr-seed": "0.1.0-alpha.2"
+    "yosr-seed": "0.1.0-alpha.4"
   }
 }