| Files | Last commit | Last update |
|---|---|---|
chore(release): publish prisma stable releases on prev (#30124) ## Summary - publish the `prisma` package under `prev` when the release tag is `latest` - preserve all other dist-tags for `prisma` - leave publishing behavior unchanged for every other package ## Validation - `pnpm exec eslint scripts/ci/publish.ts` (0 errors; existing warnings only) - `git diff --check` - no tests run (publish script has no tests) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Corrected the npm distribution tag used when publishing the Prisma package, ensuring it uses the appropriate `prev` tag instead of `latest`. * Updated publishing logs to accurately reflect the tag applied to each package. * Other packages continue using their requested distribution tags, helping ensure releases are published and identified consistently. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Steven McClankerton <tatarintsev@prisma.io> | 2 months ago | |
chore: bump execa version to 8.0.1 (#28099) | 1 year ago | |
chore: remove unused query engine related logic (#28463) Remove unused query engine dependencies, QE update logic, and QE-related test logic. Ref: https://linear.app/prisma-company/issue/TML-1554/remove-query-engine-from-prisma-engines Ref: https://github.com/prisma/prisma-engines/pull/5685 | 11 months ago | |
chore: engine overrides (#15014) | 4 years ago | |
feat(client): add `.createManyAndReturn()` top level method (#24064) | 2 years ago | |
chore: replace deprecated String.prototype.substr() (#12337) | 4 years ago | |
Complete CLI-owned prisma7 distribution identity (#29969) ## Overview Complete the CLI-owned `prisma7` identity pass by making executable selection explicit at every identity-sensitive CLI boundary and by proving the shipped behavior from packed artifacts instead of slice-local mocks. The compatibility invocation now renders `prisma7` across CLI-owned help, setup, completion, and version surfaces while ordinary `prisma` callers and tests pass `'prisma'` explicitly. ## Changes - **Explicit identity plumbing**: `packages/cli/src/bin.ts` and `packages/cli/src/completions/completion-entry.ts` are the only executable-boundary inference points, and they now pass the selected identity through `CLI`, CLI-owned commands, factories, and helpers. Existing ordinary call sites such as `scripts/run-studio.ts` and the updated CLI test suites pass `'prisma'` explicitly instead of relying on fallback defaults. - **CLI-owned output stays on the selected executable**: help, init/bootstrap/postgres guidance, completion scripts, version labels, mismatch messaging, and CLI-owned rerun/install text now derive from the selected identity. `prisma7 init` emits `prisma7/config` and `prisma7` next-step commands, while stable Prisma domain surfaces such as `prisma/schema.prisma`, `prisma.config.ts`, and `@prisma/client` stay unchanged. `packages/cli/src/CLI.ts` also avoids starting the update-check path for `prisma7`. - **Cross-platform execution and build aliases**: Bootstrap resolves the selected local CLI through its Unix shim or Windows `.cmd` shim. Workspace path mappings expose exact and wildcard `prisma`/`prisma7` entrypoints, and the esbuild resolver now handles explicit files, package directories, and wildcard subpaths consistently. - **Packed proof replaces slice-local mock coverage**: the four mock-heavy identity suites and the slice-added mock assertions are gone. Evidence now comes from the single packed E2E in `packages/client/tests/e2e/prisma7-compatibility/tests/main.test.ts`, which exercises real built/packed `prisma7 --help`, `validate --help`, text/JSON `--version`, `complete zsh`, `init`, `generate`, and `db push` flows. Identity-bearing command outputs use local inline snapshots with narrow path/version normalization; completion branding uses direct assertions rather than snapshotting the generated script. ## Why Keep the identity seam mechanically auditable: executable entrypoints infer identity once, everything identity-sensitive receives it explicitly, and ordinary `prisma` callers say so explicitly. Using one packed executable-boundary proof captures the shipped wrapper behavior without over-claiming visibility into internal update or mismatch paths, while preserving stable Prisma product names that are not distribution identity. ## Scope _CLI-owned identity completion only: explicit identity plumbing across `packages/cli`, compatibility-facing help/setup/completion/version surfaces, packed executable-boundary proof, and updated ordinary-Prisma call sites/tests. Lower-package guidance, release mirroring, and publication remain out of scope._ <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * CLI help, examples, errors, version output, completion commands, and generated project files now reflect the selected CLI command. * Initialization, linking, generation, migration, Studio, and database setup guidance use distribution-specific command names. * Added Prisma 7 compatibility coverage for help, version, completion, initialization, generation, and database operations. * **Bug Fixes** * Version mismatch warnings and dependency checks now reference the configured CLI. * Checkpoint checks and update messages appear only when applicable. * Existing projects use the selected local CLI for migration and generation. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Steven McClankerton <tatarintsev@prisma.io> | 2 months ago |
| Files | Last commit | Last update |
|---|---|---|
| 2 months ago | ||
| 1 year ago | ||
| 11 months ago | ||
| 4 years ago | ||
| 2 years ago | ||
| 4 years ago | ||
| 2 months ago |