chore(release): v0.2.0 - #143
Conversation
4659516 to
0304d78
Compare
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (32)
Knowledge base: Disabled due to Summary by CodeRabbit
WalkthroughPackage manifests across the repository were bumped from version 0.1.0 to 0.2.0. Workspace dependencies for framework, Prisma Cloud, public, integration, website, and example packages were updated to reference workspace version 0.2.0. Several example modules added Prisma packages to peer dependencies, and one build script message was reformatted without changing its control flow. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install timed out. The project may have too many dependencies for the sandbox. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
commit: |
Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
0304d78 to
c89e154
Compare
The v0.2.0 release PR (#143) went red across CI because the bump rewrote workspace:<version> pins in every manifest but left pnpm-lock.yaml at the old version, and CI installs with --frozen-lockfile. bump-minor now runs `pnpm install --lockfile-only` after set-version, the `pnpm bump-minor` script both docs already reference actually exists, and the skill/versioning docs call out the lockfile requirement. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The v0.2.0 release PR (#143) went red across CI because the bump rewrote workspace:<version> pins in every manifest but left pnpm-lock.yaml at the old version, and CI installs with --frozen-lockfile. bump-minor now runs `pnpm install --lockfile-only` after set-version, the `pnpm bump-minor` script both docs already reference actually exists, and the skill/versioning docs call out the lockfile requirement. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The v0.2.0 release PR (#143) went red across CI because the bump rewrote workspace:<version> pins in every manifest but left pnpm-lock.yaml at the old version, and CI installs with --frozen-lockfile. bump-minor now runs `pnpm install --lockfile-only` after set-version, the `pnpm bump-minor` script both docs already reference actually exists, and the skill/versioning docs call out the lockfile requirement. Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Release v0.2.0. Merging this triggers the
Publish to npmworkflow, which ships every package at 0.2.0 to npm under dist-taglatest(via OIDC trusted publishing) and cuts a GitHub Release with auto-generated notes.Bump produced by
scripts/bump-minor.ts: root version 0.1.0 → 0.2.0, stamped across all 32 workspace packages in lockstep.pnpm check:publish-depspasses (noworkspace:/catalog:leaks, exact internal pins).