v0.5.3

chore(release): 0.5.3

v0.5.2

chore(release): 0.5.2

v0.5.1

chore(release): 0.5.1

v0.5.0

fix(ci): x86_64 macOS cross-compiles from Apple Silicon

`macos-13` was the last Intel runner and has been retired. A job requesting
it does not fail — it queues, indefinitely. v0.4.1's release run has been
waiting on this single job for 23 hours with its other four targets green,
which is why that release never produced assets and why the npm shim could
never be published against it.

The Apple toolchain targets both architectures and the workflow already
installs `matrix.target`, so building the Intel binary on `macos-14` needs no
other change.

v0.4.1

release: 0.4.1

v0.4.0

fix(release): bump the npm CLI shim too, and tag before publishing npm

The `surrealguard` npm package lives in npm/, not packages/, and is unscoped —
so the bump loop (which searched only packages/ and matched only @surrealguard/*)
skipped it entirely. It sat at 0.1.0 while everything else moved, which is why
`npx surrealguard` installed a long-stale CLI.

That package and the Zed extension both download a prebuilt binary from the
GitHub Release for their own version, and those assets are produced by
.github/workflows/release.yml on a v* tag. Publishing npm before the tag exists
would turn a stale install into a 404 — strictly worse. `publish` now checks for
the tag, explains what to push, and offers to do crates.io alone (which has no
such dependency) rather than half-publishing.

v0.1.0

SurrealGuard v0.1.0 — CLI + LSP binaries for npx and the Zed extension