chore: version and release 0.10.0

0.9.0 was published from an earlier state (baked templates ref 4f54cb7,
SOLID_CLI_TEMPLATES_REF, "Solid 2.0 (Beta)"), so its changelog entry is
corrected to describe what actually shipped and the live-HEAD work moves
to 0.10.0.

Also skip begit's fetch_latest_commit: resolving HEAD to a sha goes
through api.github.com, rate limited to 60 requests/hour unauthenticated,
which the pinned version never had to call. The archive endpoint is not
rate limited, so scaffolds fetch the tarball directly.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Tommypop2

packages/create-solid/CHANGELOG.md

@@ -1,16 +1,26 @@
 # create-solid
 
+## 0.10.0
+
+### Minor Changes
+
+- Always scaffold from the latest templates
+
+  - Template downloads are no longer pinned to a baked-in solidjs/templates commit. Scaffolds come from live HEAD of the default branch, matching the `templates.json` manifest, so upstream template changes and dependency repins reach users without a CLI release.
+  - Removed the `SOLID_CLI_TEMPLATES_REF` environment override that shipped in 0.9.0, along with the pin it existed to escape.
+  - Scaffolding still avoids api.github.com, which is rate limited to 60 requests/hour for unauthenticated users: templates are fetched straight from the archive endpoint rather than resolving HEAD to a commit sha first.
+  - Solid 2.0 is labelled "Solid 2.0 (RC)" in the project picker now that Solid 2.0 core is a release candidate. It stays listed first but not preselected.
+
 ## 0.9.0
 
 ### Minor Changes
 
 - 68caa9f: Solid 2.0 template support
 
-  - New "Solid 2.0" top-level project type scaffolding the `solid-v2/*` templates from solidjs/templates (basic, bare, fullstack, fullstack-tanstack, with-\*). Listed first but not preselected while Solid 2.0 core is a release candidate; existing flags (`-s`, `-v`, `-l`, `--v2`) keep their meaning, plus new `--solid` and `--ssr` flags.
+  - New "Solid 2.0" top-level project type scaffolding the `solid-v2/*` templates from solidjs/templates (basic, bare, fullstack, fullstack-tanstack, with-\*). Listed first but not preselected while Solid 2.0 core is in beta; existing flags (`-s`, `-v`, `-l`, `--v2`) keep their meaning, plus new `--solid` and `--ssr` flags.
   - Optional streaming SSR on templates that support it (currently `basic`): a scaffold-time flip that sets `ssr: true` in `vite.config.ts`, adds the generic production `server.js`, and points the `start` script at it. Defaults to No.
   - JavaScript variants of the Solid 2.0 templates via the existing sucrase TS→JS conversion (no `index.html` rewrite; `.ts`/`.tsx` references inside `vite.config` are retargeted, `.d.ts` files dropped, minimal `jsconfig.json`).
   - Template lists, subdir paths and per-template flags are now read from a `templates.json` manifest at the templates repo HEAD (2s timeout), with silent fallback to the baked-in lists — so new templates and future repo reorganizations no longer require a CLI release.
-  - Template tarball downloads track live HEAD of the templates repo, matching the `templates.json` manifest, so template contents and their dependency updates reach users without a CLI release.
 
 ## 0.8.1
 

packages/create-solid/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "create-solid",
-	"version": "0.9.0",
+	"version": "0.10.0",
 	"description": "Create Solid apps with low configuration",
 	"author": "Thomas Beer",
 	"contributors": [

packages/create/CHANGELOG.md

@@ -1,16 +1,26 @@
 # @solid-cli/create
 
+## 0.10.0
+
+### Minor Changes
+
+- Always scaffold from the latest templates
+
+  - Template downloads are no longer pinned to a baked-in solidjs/templates commit. Scaffolds come from live HEAD of the default branch, matching the `templates.json` manifest, so upstream template changes and dependency repins reach users without a CLI release.
+  - Removed the `SOLID_CLI_TEMPLATES_REF` environment override that shipped in 0.9.0, along with the pin it existed to escape.
+  - Scaffolding still avoids api.github.com, which is rate limited to 60 requests/hour for unauthenticated users: templates are fetched straight from the archive endpoint rather than resolving HEAD to a commit sha first.
+  - Solid 2.0 is labelled "Solid 2.0 (RC)" in the project picker now that Solid 2.0 core is a release candidate. It stays listed first but not preselected.
+
 ## 0.9.0
 
 ### Minor Changes
 
 - 68caa9f: Solid 2.0 template support
 
-  - New "Solid 2.0" top-level project type scaffolding the `solid-v2/*` templates from solidjs/templates (basic, bare, fullstack, fullstack-tanstack, with-\*). Listed first but not preselected while Solid 2.0 core is a release candidate; existing flags (`-s`, `-v`, `-l`, `--v2`) keep their meaning, plus new `--solid` and `--ssr` flags.
+  - New "Solid 2.0" top-level project type scaffolding the `solid-v2/*` templates from solidjs/templates (basic, bare, fullstack, fullstack-tanstack, with-\*). Listed first but not preselected while Solid 2.0 core is in beta; existing flags (`-s`, `-v`, `-l`, `--v2`) keep their meaning, plus new `--solid` and `--ssr` flags.
   - Optional streaming SSR on templates that support it (currently `basic`): a scaffold-time flip that sets `ssr: true` in `vite.config.ts`, adds the generic production `server.js`, and points the `start` script at it. Defaults to No.
   - JavaScript variants of the Solid 2.0 templates via the existing sucrase TS→JS conversion (no `index.html` rewrite; `.ts`/`.tsx` references inside `vite.config` are retargeted, `.d.ts` files dropped, minimal `jsconfig.json`).
   - Template lists, subdir paths and per-template flags are now read from a `templates.json` manifest at the templates repo HEAD (2s timeout), with silent fallback to the baked-in lists — so new templates and future repo reorganizations no longer require a CLI release.
-  - Template tarball downloads track live HEAD of the templates repo, matching the `templates.json` manifest, so template contents and their dependency updates reach users without a CLI release.
 
 ## 0.8.1
 

packages/create/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@solid-cli/create",
-	"version": "0.9.0",
+	"version": "0.10.0",
 	"description": "Create Solid apps with low configuration",
 	"author": "Thomas Beer",
 	"contributors": [

packages/create/src/utils/download.ts

@@ -8,6 +8,19 @@ export const TEMPLATES_REPO = { owner: "solidjs", name: "templates" } as const;
  * No ref is pinned: scaffolds always come from live HEAD of the default branch,
  * matching the `templates.json` manifest, so template updates reach users
  * without a CLI release.
+ *
+ * `fetch_latest_commit` is off because resolving HEAD to a sha goes through
+ * api.github.com, which is rate limited to 60 requests/hour for unauthenticated
+ * users — the archive download itself is not. Without a sha there is nothing to
+ * key a cache on, so caching is off too and every scaffold fetches a fresh
+ * tarball, which is what tracking HEAD means.
  */
 export const downloadTemplate = (subdir: string, destination: string) =>
-	downloadRepo({ repo: { ...TEMPLATES_REPO, subdir }, dest: destination }, GithubFetcher);
+	downloadRepo(
+		{
+			repo: { ...TEMPLATES_REPO, subdir },
+			dest: destination,
+			opts: { cache: false, fetch_latest_commit: false },
+		},
+		GithubFetcher,
+	);