Repository navigation
Releases
blodemd@0.2.1
Patch Changes
-
af075cc: Accept
seo.siteUrlindocs.json, so a site proxied behind your own domain
can declare where it is actually published. Canonical tags,og:url, JSON-LD,
the sitemap,llms.txtand the.mdalternates are all built from that value
instead of being inferred from the request, which a proxy makes impossible.Validation now distinguishes authoring from serving:
blodemd validatestill
rejects unknown keys so typos fail before they ship, while a published site
renders through them rather than being replaced by an error page.
blodemd@0.2.0
Minor Changes
-
c248a58: Split the heavy Next.js dev-server payload out of the
blodemdCLI into a new
companion package,blodemd-dev.npx blodemd push(and every other CLI command) now installs a lean CLI with
nonext/react/Tailwind/shiki payload.blodemd devkeeps working: inside
the monorepo it runsapps/dev-serverdirectly as before, and when installed
from npm it delegates toblodemd-dev(pinned to the matching version) which
vendors and boots the Next.js dev server on demand. The two packages version
and publish together.
blodemd@0.1.0
Minor Changes
-
661f04a: CI-grade deploys with project-scoped keys.
blodemd pushnow authenticates in CI with a project-scoped deploy key via
--api-keyorBLODEMD_API_KEY(sent as a Bearer token). Keys are created in
the dashboard (Settings → Deploy keys) or printed once whenpushauto-creates
a project.--jsononpushandvalidatefor machine-readable output; progress and
errors go to stderr in non-interactive/CI environments so stdout stays clean.- New
blodemd projectscommand lists your projects. - Clearer failures: 401s map to a distinct exit code with an actionable hint, and
a top-level boundary prints the message + hint (no raw stack traces).
blodemd@0.0.15
Patch Changes
- 5e66722:
blodemd pushnow authenticates with an API key via the--api-keyflag or the
BLODEMD_API_KEYenvironment variable, resolved before storedblodemd login
credentials. This matches the documented credential order and unblocks
non-interactive CI deploys, which previously failed with "Not logged in".
blodemd@0.0.14
Patch Changes
-
e6b6149: Bug fixes bundled into the CLI's vendored preview/prebuild pipeline:
- Preserve code content containing
$&,$1,$`, or$$when generating agent markdown (was corrupted by substitution patterns). extractTocnow strips~~~fenced blocks (not just backticks) and guarantees unique heading ids.- Return
listFilespaths relative to the listed directory so collections with a non-empty root resolve correctly. - Validate parsed OpenAPI specs are objects with a record-shaped
pathsbefore use, failing with a clear error instead of crashing. - Reject malformed slugs (bare, leading/trailing, or consecutive hyphens) in docs config.
Internal: decomposed the CLI entry into focused command modules (no behavior or flag changes).
- Preserve code content containing
blodemd@0.0.13
Patch Changes
- 8260a9e: Harden
blodemd devruntime scaffolding so the CLI works under hoisted / npx-cache layouts where<cliPackageRoot>/node_modules/nextisn't the package's own copy. The standalone runtime now resolvesnext/package.jsonthroughrequire.resolveand uses the owningnode_modulesdirectory, fixing "next not found" errors when the CLI is installed as a global or executed vianpxwithout local hoisting.
blodemd@0.0.12
Patch Changes
- 85c7a6a: Fix
npx blodemdfailing withCannot find package '@repo/common'. The CLI build now builds the workspace@repo/*packages before running tsdown so their compiled output is inlined into the published bundle, and the npm publish workflow runs the CLI build through turbo so^buildordering is respected.
blodemd@0.0.11
Patch Changes
- Split display name from deploy slug in project config and fix deploy workflow issues
blodemd@0.0.10
Patch Changes
- Fix SiteConfig format validation in docs.json previewing
blodemd@0.0.9
Patch Changes
- Refactor API with CORS support, header-based auth, and domains/tenants overhaul; add new CLI commands (new, scaffold, upload, logout, whoami); improve docs UI components and search