@hamedb89/localghost 0.2.0 → 0.3.0

package/docs/github.md

@@ -115,12 +115,12 @@ https://hamedb89.github.io/localghost/
 `.github/workflows/ci.yml` runs on pull requests and pushes to `main`. It uses `npm ci`, then runs:
 
 ```sh
-npm run release:check
+./bin/ghost check
 ```
 
-That command typechecks, builds the package, builds the static site, and runs `npm pack --dry-run`.
+That command typechecks, builds the package, builds the static site, and runs `npm pack --dry-run`. From a checkout, the same verification is available as `./bin/ghost check`.
 
-`.github/workflows/publish-npm.yml` publishes to npm when a `v*` tag is pushed, or from manual workflow dispatch. The workflow checks that tag names match `package.json` versions, reruns `npm run release:check`, and then uses:
+`.github/workflows/publish-npm.yml` publishes to npm when a `v*` tag is pushed, or from manual workflow dispatch. The workflow checks that tag names match `package.json` versions, reruns `./bin/ghost check`, and then uses:
 
 ```sh
 npm run publish:public
@@ -153,12 +153,12 @@ For a normal patch release:
 
 ```sh
 git status --short
-npm run release:check
+./bin/ghost check
 npm version patch
 git push origin main --tags
 ```
 
-Pushing the `v*` tag starts the npm publish workflow automatically. The workflow reruns `npm run release:check` before publishing. Create the GitHub release afterwards if you want release notes on GitHub.
+Pushing the `v*` tag starts the npm publish workflow automatically. The workflow reruns `./bin/ghost check` before publishing. Create the GitHub release afterwards if you want release notes on GitHub.
 
 If publishing from a local terminal instead of GitHub Actions, omit provenance and provide the npm two-factor code:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hamedb89/localghost",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "Friendly local hostnames for app repos with .localghost, Caddy, /etc/hosts, and Vite.",
   "type": "module",
   "bin": {