3 Commits

Author	SHA1	Message	Date
Bilal Godil	7125a9eff4	feat(hexclave): rename @stackframe/* → @hexclave/* (PR 3) ... Source rename across the monorepo. Every publishable package now ships under its @hexclave/* name natively, no rewrite-at-publish indirection. Workflow + tooling: - Delete scripts/rewrite-packages-to-hexclave.ts (one-shot mirror). - Remove the mirror-publish block from .github/workflows/npm-publish.yaml. The remaining `pnpm publish -r` step publishes @hexclave/* natively. - Flip the auto-bump changeset target from @stackframe/stack to @hexclave/next so 'Update package versions on dev' keeps working. - Delete packages/template/src/internal/deprecation-warning.ts and its imports — @hexclave/* never warns about itself, and after PR 3 no @stackframe/* artifact is ever built from source again. Package renames (publishable): @stackframe/react → @hexclave/react @stackframe/stack → @hexclave/next @stackframe/js → @hexclave/js @stackframe/stack-shared → @hexclave/shared @stackframe/stack-ui → @hexclave/ui @stackframe/stack-sc → @hexclave/sc @stackframe/stack-cli → @hexclave/cli @stackframe/tanstack-start → @hexclave/tanstack-start @stackframe/dashboard-ui-components → @hexclave/dashboard-ui-components Internal monorepo packages (private, never published) also renamed for brand consistency: backend, dashboard, docs, mcp, skills, e2e-tests, example apps, the swift-sdk, the monorepo root, etc. Cost is mechanical; payoff is no stray @stackframe/* names left under apps/, examples/, sdks/. Carve-outs intentionally kept under their legacy names: - @stackframe/emails — virtual module imported by customer-stored email templates; the renderer in apps/backend/src/lib/email-rendering.tsx dual-aliases both names to the same backing module indefinitely. - @stackframe/template — internal codegen source, never published; per docs-mintlify/migration.mdx 'internal packages keep names'. - @stackframe/init-stack — deprecated; now marked private: true so the last published version on npm continues to serve old install commands but the workspace stops publishing it. Backward-compat detection (so projects still on the last @stackframe/* release keep working): - packages/stack-shared/src/config-rendering.ts — CONFIG_IMPORT_PACKAGES table includes both @hexclave/* (canonical, first match wins) and legacy @stackframe/* names. Function renamed detectStackframeImportPackage → detectConfigImportPackage. - apps/dashboard/src/lib/github-config-push.ts — import detection regex now matches both @hexclave/<name> and @stackframe/<name>, hexclave preferred. Versions: every renamed package reset to 1.0.0 in source. The repo's existing 'bump versions before merging to main' flow will move them to 1.0.1 on the first publish run, so the dual-publish 1.0.0 from PR 2 is not overwritten. Other touch-ups discovered during sweep: - Root package.json: 'fern' script filter was @stackframe/docs (legacy typo, never resolved) → @hexclave/docs. - README.md contributor note: @stackframe/XYZ → @hexclave/XYZ. - packages/stack-cli/package.json: register `hexclave` bin alongside the legacy `stack` bin so `npx @hexclave/cli init` works on the natively-published artifact (PR 1481's rewrite script did this at publish time; now it's in source). - packages/template/package-template.json: per-platform names + version flipped to hexclave + 1.0.0 to stay in sync with generated package.json. - docs/package.json (legacy fumadocs folder, otherwise carved out of the brand sweep): workspace deps and name updated minimally so `pnpm install` resolves — content (MDX) intentionally untouched per the PR 2 scoping decision. Carve-out files (skipped entirely by the sweep, intentional history): - docs-mintlify/migration.mdx — teaches the rename, references both. - RENAME-TO-HEXCLAVE.md — planning doc, references both indefinitely. - legacy docs/ folder — content untouched per PR 2 carve-out. generate-sdks regenerated packages/{react,stack,js} from template. pnpm-lock.yaml regenerated. Typecheck green on stack-shared, stack, js, react. Dashboard typecheck has pre-existing 'X is of type unknown' errors that need to be investigated separately (likely a local node_modules build state issue, not source).	2026-05-23 17:41:53 -07:00
Konstantin Wohlwend	be6970cd81	Fix Docker build scripts	2026-04-18 23:50:50 -07:00
Mantra	bb277d33c9	Backend fallback (cloud run) (#1306) ... - Added support for `@opentelemetry/sdk-node` in the backend. - Updated various dependencies including AWS SDK and OpenTelemetry packages. - Implemented graceful shutdown handling for non-Vercel runtimes in `prisma-client.tsx`. - Enhanced AWS credentials retrieval to support GCP Workload Identity Federation. - Introduced a Dockerfile for Cloud Run deployment, optimizing the backend build process. - Updated `.gitignore` to include Terraform runtime files and secrets. This commit improves the backend's observability and deployment flexibility, particularly for Cloud Run environments. <!-- Make sure you've read the CONTRIBUTING.md guidelines: https://github.com/stack-auth/stack-auth/blob/dev/CONTRIBUTING.md --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * OpenTelemetry observability with dynamic provider selection per deployment. * Cloud Run trusted-proxy support for accurate client IP handling. * Graceful shutdown that waits for in-flight background work. * New background-task handling to improve async webhook/email delivery reliability. * AWS credential providers added (Vercel OIDC & GCP Workload Identity Federation). * Dockerized backend image for Cloud Run / self-host deployments. * **Chores** * Updated dependencies for OpenTelemetry and AWS SDK support. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Konstantin Wohlwend <n2d4xc@gmail.com>	2026-04-11 00:57:37 +00:00