| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
chore(release): bump to 8.0.0-rc.10 (#30268) `8.0.0-rc.9` → `8.0.0-rc.10`. ## What ships The user-facing changes are in [`docs/releases/v8.0.0-rc.10.md`](docs/releases/v8.0.0-rc.10.md), mirrored into `CHANGELOG.md`. Review that file as the release's public statement. In short: the Prisma 8 rename reaches every identifier a project can see (schema header, environment variables, config directory, primer file), the emitted contract gains `Models`, `Scalars`, `Shape`, and a working `ResultType` on ORM queries, `db sign` sets the `db` ref so the first plan after adoption stays incremental, and the language server completes attribute names. ## Skill audit I checked the bundled `prisma-8` skill against every PR in the range. The in-range PRs had already updated the references for `db sign` ref advancement and its two flags (#30251), the rename (#30262), the `Models` and `Shape` types (#30231), and the rc.9-to-rc.10 upgrade recipes for both audiences. Two gaps are fixed in the second commit: the skill date stamp, and `references/contract.md` never mentioned the `// use prisma-8` schema header at all. `library_version` was stamped to rc.10 by `pnpm bump-version`. ## Merging this PR ships the release The push to `main` carries the bumped root `version`. The `Publish to npm` workflow publishes `8.0.0-rc.10` under the `latest` dist-tag and creates a matching pre-release GitHub Release whose body is the notes file above. See [`docs/oss/versioning.md`](docs/oss/versioning.md). A matching prisma/web PR updates the docs site for this release and should merge once this one is published. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added named model and result types for contracts. * Added language-server completion for attributes and named arguments. * Added nullable metadata and validation for to-one relations. * Added reference-selection controls and JSON metadata to `db sign`; the `db` reference now advances by default. * **Bug Fixes** * Improved migration planning and PostgreSQL connection handling. * Corrected package tag handling in `orm init`. * **Documentation** * Documented Prisma 8 schema headers, renamed CLI environment variables, and updated upgrade guidance. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> | 2 天前 | |
chore(release): bump to 8.0.0-rc.10 (#30268) `8.0.0-rc.9` → `8.0.0-rc.10`. ## What ships The user-facing changes are in [`docs/releases/v8.0.0-rc.10.md`](docs/releases/v8.0.0-rc.10.md), mirrored into `CHANGELOG.md`. Review that file as the release's public statement. In short: the Prisma 8 rename reaches every identifier a project can see (schema header, environment variables, config directory, primer file), the emitted contract gains `Models`, `Scalars`, `Shape`, and a working `ResultType` on ORM queries, `db sign` sets the `db` ref so the first plan after adoption stays incremental, and the language server completes attribute names. ## Skill audit I checked the bundled `prisma-8` skill against every PR in the range. The in-range PRs had already updated the references for `db sign` ref advancement and its two flags (#30251), the rename (#30262), the `Models` and `Shape` types (#30231), and the rc.9-to-rc.10 upgrade recipes for both audiences. Two gaps are fixed in the second commit: the skill date stamp, and `references/contract.md` never mentioned the `// use prisma-8` schema header at all. `library_version` was stamped to rc.10 by `pnpm bump-version`. ## Merging this PR ships the release The push to `main` carries the bumped root `version`. The `Publish to npm` workflow publishes `8.0.0-rc.10` under the `latest` dist-tag and creates a matching pre-release GitHub Release whose body is the notes file above. See [`docs/oss/versioning.md`](docs/oss/versioning.md). A matching prisma/web PR updates the docs site for this release and should merge once this one is published. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added named model and result types for contracts. * Added language-server completion for attributes and named arguments. * Added nullable metadata and validation for to-one relations. * Added reference-selection controls and JSON metadata to `db sign`; the `db` reference now advances by default. * **Bug Fixes** * Improved migration planning and PostgreSQL connection handling. * Corrected package tag handling in `orm init`. * **Documentation** * Documented Prisma 8 schema headers, renamed CLI environment variables, and updated upgrade guidance. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> | 2 天前 | |
chore(release): bump to 8.0.0-rc.10 (#30268) `8.0.0-rc.9` → `8.0.0-rc.10`. ## What ships The user-facing changes are in [`docs/releases/v8.0.0-rc.10.md`](docs/releases/v8.0.0-rc.10.md), mirrored into `CHANGELOG.md`. Review that file as the release's public statement. In short: the Prisma 8 rename reaches every identifier a project can see (schema header, environment variables, config directory, primer file), the emitted contract gains `Models`, `Scalars`, `Shape`, and a working `ResultType` on ORM queries, `db sign` sets the `db` ref so the first plan after adoption stays incremental, and the language server completes attribute names. ## Skill audit I checked the bundled `prisma-8` skill against every PR in the range. The in-range PRs had already updated the references for `db sign` ref advancement and its two flags (#30251), the rename (#30262), the `Models` and `Shape` types (#30231), and the rc.9-to-rc.10 upgrade recipes for both audiences. Two gaps are fixed in the second commit: the skill date stamp, and `references/contract.md` never mentioned the `// use prisma-8` schema header at all. `library_version` was stamped to rc.10 by `pnpm bump-version`. ## Merging this PR ships the release The push to `main` carries the bumped root `version`. The `Publish to npm` workflow publishes `8.0.0-rc.10` under the `latest` dist-tag and creates a matching pre-release GitHub Release whose body is the notes file above. See [`docs/oss/versioning.md`](docs/oss/versioning.md). A matching prisma/web PR updates the docs site for this release and should merge once this one is published. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added named model and result types for contracts. * Added language-server completion for attributes and named arguments. * Added nullable metadata and validation for to-one relations. * Added reference-selection controls and JSON metadata to `db sign`; the `db` reference now advances by default. * **Bug Fixes** * Improved migration planning and PostgreSQL connection handling. * Corrected package tag handling in `orm init`. * **Documentation** * Documented Prisma 8 schema headers, renamed CLI environment variables, and updated upgrade guidance. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> | 2 天前 | |
chore: organize directories by domain and layer | 8 个月前 | |
chore(release): bump to 8.0.0-rc.10 (#30268) `8.0.0-rc.9` → `8.0.0-rc.10`. ## What ships The user-facing changes are in [`docs/releases/v8.0.0-rc.10.md`](docs/releases/v8.0.0-rc.10.md), mirrored into `CHANGELOG.md`. Review that file as the release's public statement. In short: the Prisma 8 rename reaches every identifier a project can see (schema header, environment variables, config directory, primer file), the emitted contract gains `Models`, `Scalars`, `Shape`, and a working `ResultType` on ORM queries, `db sign` sets the `db` ref so the first plan after adoption stays incremental, and the language server completes attribute names. ## Skill audit I checked the bundled `prisma-8` skill against every PR in the range. The in-range PRs had already updated the references for `db sign` ref advancement and its two flags (#30251), the rename (#30262), the `Models` and `Shape` types (#30231), and the rc.9-to-rc.10 upgrade recipes for both audiences. Two gaps are fixed in the second commit: the skill date stamp, and `references/contract.md` never mentioned the `// use prisma-8` schema header at all. `library_version` was stamped to rc.10 by `pnpm bump-version`. ## Merging this PR ships the release The push to `main` carries the bumped root `version`. The `Publish to npm` workflow publishes `8.0.0-rc.10` under the `latest` dist-tag and creates a matching pre-release GitHub Release whose body is the notes file above. See [`docs/oss/versioning.md`](docs/oss/versioning.md). A matching prisma/web PR updates the docs site for this release and should merge once this one is published. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added named model and result types for contracts. * Added language-server completion for attributes and named arguments. * Added nullable metadata and validation for to-one relations. * Added reference-selection controls and JSON metadata to `db sign`; the `db` reference now advances by default. * **Bug Fixes** * Improved migration planning and PostgreSQL connection handling. * Corrected package tag handling in `orm init`. * **Documentation** * Documented Prisma 8 schema headers, renamed CLI environment variables, and updated upgrade guidance. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> | 2 天前 | |
chore(release): bump to 8.0.0-rc.10 (#30268) `8.0.0-rc.9` → `8.0.0-rc.10`. ## What ships The user-facing changes are in [`docs/releases/v8.0.0-rc.10.md`](docs/releases/v8.0.0-rc.10.md), mirrored into `CHANGELOG.md`. Review that file as the release's public statement. In short: the Prisma 8 rename reaches every identifier a project can see (schema header, environment variables, config directory, primer file), the emitted contract gains `Models`, `Scalars`, `Shape`, and a working `ResultType` on ORM queries, `db sign` sets the `db` ref so the first plan after adoption stays incremental, and the language server completes attribute names. ## Skill audit I checked the bundled `prisma-8` skill against every PR in the range. The in-range PRs had already updated the references for `db sign` ref advancement and its two flags (#30251), the rename (#30262), the `Models` and `Shape` types (#30231), and the rc.9-to-rc.10 upgrade recipes for both audiences. Two gaps are fixed in the second commit: the skill date stamp, and `references/contract.md` never mentioned the `// use prisma-8` schema header at all. `library_version` was stamped to rc.10 by `pnpm bump-version`. ## Merging this PR ships the release The push to `main` carries the bumped root `version`. The `Publish to npm` workflow publishes `8.0.0-rc.10` under the `latest` dist-tag and creates a matching pre-release GitHub Release whose body is the notes file above. See [`docs/oss/versioning.md`](docs/oss/versioning.md). A matching prisma/web PR updates the docs site for this release and should merge once this one is published. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added named model and result types for contracts. * Added language-server completion for attributes and named arguments. * Added nullable metadata and validation for to-one relations. * Added reference-selection controls and JSON metadata to `db sign`; the `db` reference now advances by default. * **Bug Fixes** * Improved migration planning and PostgreSQL connection handling. * Corrected package tag handling in `orm init`. * **Documentation** * Documented Prisma 8 schema headers, renamed CLI environment variables, and updated upgrade guidance. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> | 2 天前 | |
chore(release): bump to 8.0.0-rc.10 (#30268) `8.0.0-rc.9` → `8.0.0-rc.10`. ## What ships The user-facing changes are in [`docs/releases/v8.0.0-rc.10.md`](docs/releases/v8.0.0-rc.10.md), mirrored into `CHANGELOG.md`. Review that file as the release's public statement. In short: the Prisma 8 rename reaches every identifier a project can see (schema header, environment variables, config directory, primer file), the emitted contract gains `Models`, `Scalars`, `Shape`, and a working `ResultType` on ORM queries, `db sign` sets the `db` ref so the first plan after adoption stays incremental, and the language server completes attribute names. ## Skill audit I checked the bundled `prisma-8` skill against every PR in the range. The in-range PRs had already updated the references for `db sign` ref advancement and its two flags (#30251), the rename (#30262), the `Models` and `Shape` types (#30231), and the rc.9-to-rc.10 upgrade recipes for both audiences. Two gaps are fixed in the second commit: the skill date stamp, and `references/contract.md` never mentioned the `// use prisma-8` schema header at all. `library_version` was stamped to rc.10 by `pnpm bump-version`. ## Merging this PR ships the release The push to `main` carries the bumped root `version`. The `Publish to npm` workflow publishes `8.0.0-rc.10` under the `latest` dist-tag and creates a matching pre-release GitHub Release whose body is the notes file above. See [`docs/oss/versioning.md`](docs/oss/versioning.md). A matching prisma/web PR updates the docs site for this release and should merge once this one is published. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added named model and result types for contracts. * Added language-server completion for attributes and named arguments. * Added nullable metadata and validation for to-one relations. * Added reference-selection controls and JSON metadata to `db sign`; the `db` reference now advances by default. * **Bug Fixes** * Improved migration planning and PostgreSQL connection handling. * Corrected package tag handling in `orm init`. * **Documentation** * Documented Prisma 8 schema headers, renamed CLI environment variables, and updated upgrade guidance. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> | 2 天前 | |
chore(release): bump to 8.0.0-rc.10 (#30268) `8.0.0-rc.9` → `8.0.0-rc.10`. ## What ships The user-facing changes are in [`docs/releases/v8.0.0-rc.10.md`](docs/releases/v8.0.0-rc.10.md), mirrored into `CHANGELOG.md`. Review that file as the release's public statement. In short: the Prisma 8 rename reaches every identifier a project can see (schema header, environment variables, config directory, primer file), the emitted contract gains `Models`, `Scalars`, `Shape`, and a working `ResultType` on ORM queries, `db sign` sets the `db` ref so the first plan after adoption stays incremental, and the language server completes attribute names. ## Skill audit I checked the bundled `prisma-8` skill against every PR in the range. The in-range PRs had already updated the references for `db sign` ref advancement and its two flags (#30251), the rename (#30262), the `Models` and `Shape` types (#30231), and the rc.9-to-rc.10 upgrade recipes for both audiences. Two gaps are fixed in the second commit: the skill date stamp, and `references/contract.md` never mentioned the `// use prisma-8` schema header at all. `library_version` was stamped to rc.10 by `pnpm bump-version`. ## Merging this PR ships the release The push to `main` carries the bumped root `version`. The `Publish to npm` workflow publishes `8.0.0-rc.10` under the `latest` dist-tag and creates a matching pre-release GitHub Release whose body is the notes file above. See [`docs/oss/versioning.md`](docs/oss/versioning.md). A matching prisma/web PR updates the docs site for this release and should merge once this one is published. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added named model and result types for contracts. * Added language-server completion for attributes and named arguments. * Added nullable metadata and validation for to-one relations. * Added reference-selection controls and JSON metadata to `db sign`; the `db` reference now advances by default. * **Bug Fixes** * Improved migration planning and PostgreSQL connection handling. * Corrected package tag handling in `orm init`. * **Documentation** * Documented Prisma 8 schema headers, renamed CLI environment variables, and updated upgrade guidance. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> | 2 天前 | |
chore(release): bump to 8.0.0-rc.10 (#30268) `8.0.0-rc.9` → `8.0.0-rc.10`. ## What ships The user-facing changes are in [`docs/releases/v8.0.0-rc.10.md`](docs/releases/v8.0.0-rc.10.md), mirrored into `CHANGELOG.md`. Review that file as the release's public statement. In short: the Prisma 8 rename reaches every identifier a project can see (schema header, environment variables, config directory, primer file), the emitted contract gains `Models`, `Scalars`, `Shape`, and a working `ResultType` on ORM queries, `db sign` sets the `db` ref so the first plan after adoption stays incremental, and the language server completes attribute names. ## Skill audit I checked the bundled `prisma-8` skill against every PR in the range. The in-range PRs had already updated the references for `db sign` ref advancement and its two flags (#30251), the rename (#30262), the `Models` and `Shape` types (#30231), and the rc.9-to-rc.10 upgrade recipes for both audiences. Two gaps are fixed in the second commit: the skill date stamp, and `references/contract.md` never mentioned the `// use prisma-8` schema header at all. `library_version` was stamped to rc.10 by `pnpm bump-version`. ## Merging this PR ships the release The push to `main` carries the bumped root `version`. The `Publish to npm` workflow publishes `8.0.0-rc.10` under the `latest` dist-tag and creates a matching pre-release GitHub Release whose body is the notes file above. See [`docs/oss/versioning.md`](docs/oss/versioning.md). A matching prisma/web PR updates the docs site for this release and should merge once this one is published. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added named model and result types for contracts. * Added language-server completion for attributes and named arguments. * Added nullable metadata and validation for to-one relations. * Added reference-selection controls and JSON metadata to `db sign`; the `db` reference now advances by default. * **Bug Fixes** * Improved migration planning and PostgreSQL connection handling. * Corrected package tag handling in `orm init`. * **Documentation** * Documented Prisma 8 schema headers, renamed CLI environment variables, and updated upgrade guidance. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> | 2 天前 | |
chore(release): bump to 8.0.0-rc.10 (#30268) `8.0.0-rc.9` → `8.0.0-rc.10`. ## What ships The user-facing changes are in [`docs/releases/v8.0.0-rc.10.md`](docs/releases/v8.0.0-rc.10.md), mirrored into `CHANGELOG.md`. Review that file as the release's public statement. In short: the Prisma 8 rename reaches every identifier a project can see (schema header, environment variables, config directory, primer file), the emitted contract gains `Models`, `Scalars`, `Shape`, and a working `ResultType` on ORM queries, `db sign` sets the `db` ref so the first plan after adoption stays incremental, and the language server completes attribute names. ## Skill audit I checked the bundled `prisma-8` skill against every PR in the range. The in-range PRs had already updated the references for `db sign` ref advancement and its two flags (#30251), the rename (#30262), the `Models` and `Shape` types (#30231), and the rc.9-to-rc.10 upgrade recipes for both audiences. Two gaps are fixed in the second commit: the skill date stamp, and `references/contract.md` never mentioned the `// use prisma-8` schema header at all. `library_version` was stamped to rc.10 by `pnpm bump-version`. ## Merging this PR ships the release The push to `main` carries the bumped root `version`. The `Publish to npm` workflow publishes `8.0.0-rc.10` under the `latest` dist-tag and creates a matching pre-release GitHub Release whose body is the notes file above. See [`docs/oss/versioning.md`](docs/oss/versioning.md). A matching prisma/web PR updates the docs site for this release and should merge once this one is published. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added named model and result types for contracts. * Added language-server completion for attributes and named arguments. * Added nullable metadata and validation for to-one relations. * Added reference-selection controls and JSON metadata to `db sign`; the `db` reference now advances by default. * **Bug Fixes** * Improved migration planning and PostgreSQL connection handling. * Corrected package tag handling in `orm init`. * **Documentation** * Documented Prisma 8 schema headers, renamed CLI environment variables, and updated upgrade guidance. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> | 2 天前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 天前 | ||
| 2 天前 | ||
| 2 天前 | ||
| 8 个月前 | ||
| 2 天前 | ||
| 2 天前 | ||
| 2 天前 | ||
| 2 天前 | ||
| 2 天前 | ||
| 2 天前 |