@spaethtech/svelte-ui 0.3.0 → 0.3.1-dev.4.9724ad8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +15 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -159,9 +159,23 @@ CI verifies the tag matches `package.json`, type-checks, then runs `npm publish`
|
|
|
159
159
|
script builds `dist/` fresh — never commit `dist/`). Versions are **immutable**: a number can't be
|
|
160
160
|
republished, so don't tag until the CHANGELOG/version are right.
|
|
161
161
|
|
|
162
|
+
### Dev / canary builds
|
|
163
|
+
|
|
164
|
+
Every push to `main` also publishes a prerelease under the **`dev`** dist-tag (same workflow, no git
|
|
165
|
+
tag needed) — version `<next patch>-dev.<run>.<sha>`. It never touches `latest`, and caret ranges
|
|
166
|
+
(`^0.3.0`) skip prereleases, so it's invisible unless a consumer opts in:
|
|
167
|
+
|
|
168
|
+
```bash
|
|
169
|
+
npm install @spaethtech/svelte-ui@dev # newest main build; re-run / npm update to refresh
|
|
170
|
+
```
|
|
171
|
+
|
|
172
|
+
Use it to test unreleased work in a consumer before cutting a real release. (Publishing on every push
|
|
173
|
+
does accumulate prerelease versions on the registry — that's expected.)
|
|
174
|
+
|
|
162
175
|
**One-time setup (already done once, listed for reference):** on npmjs.com → the package → Settings →
|
|
163
176
|
add a **Trusted Publisher** for GitHub Actions (org `spaethtech`, repo `svelte-ui`, workflow
|
|
164
|
-
`publish.yml
|
|
177
|
+
`publish.yml`, "Allow npm publish"). Both the release and dev paths live in that one workflow file, so
|
|
178
|
+
the single trusted-publisher entry covers both.
|
|
165
179
|
|
|
166
180
|
## Known issues
|
|
167
181
|
|