Skip to content

🔧 Move to devEngines.packageManager#6996

Merged
dubzzz merged 6 commits into
mainfrom
claude/resolve-merge-conflicts-TNHJ6
May 18, 2026
Merged

🔧 Move to devEngines.packageManager#6996
dubzzz merged 6 commits into
mainfrom
claude/resolve-merge-conflicts-TNHJ6

Conversation

@dubzzz

@dubzzz dubzzz commented May 18, 2026

Copy link
Copy Markdown
Owner

Contrary to my first attempt of move done by Claude at #6957, this one has been achieved fully manually and from a Windows machine.

We expect it will pass.

dubzzz and others added 5 commits May 15, 2026 15:19
Contrary to my first attempt of move done by Claude at #6957, this one has been achieved fully manually and from a Windows machine.

We expect it will pass.
## Description

This PR updates the CI/CD workflows to use `pnpm` instead of `npm` for
publishing packages to NPM registry. The changes include:

1. **Preview generation**: Added `--pnpm` flag to `pkg-pr-new publish`
commands to ensure pnpm is used for preview builds
2. **Package publishing**: Replaced `npm publish` with `pnpm publish
--no-git-checks` across all 7 package publishing jobs (fast-check, ava,
jest, packaged, poisoning, vitest, worker)
3. **pnpm setup**: Added explicit `pnpm/action-setup` step to all
publishing jobs to ensure pnpm is available before Node.js setup
4. **Line number updates**: Updated zizmor.yml ignore rules to reflect
the new line numbers after adding pnpm installation steps

These changes ensure consistency with the project's use of pnpm as the
package manager and prevent potential issues with npm's git checks
during CI publishing.

## Checklist

- [ ] I have a full understanding of every line in this PR — whether the
code was hand-written, AI-generated, copied from external sources or
produced by any other tool
- [ ] I flagged the impact of my change (minor / patch / major) either
by running `pnpm run bump` or by following the instructions from the
changeset bot
- [ ] I kept this PR focused on a single concern and did not bundle
unrelated changes
- [ ] I followed the [gitmoji](https://gitmoji.dev/) specification for
the name of the PR, including the package scope (e.g. `🐛(vitest)
Something...`) when the change targets a package other than `fast-check`
- [ ] I added relevant tests and they would have failed without my PR
(when applicable)

https://claude.ai/code/session_01DdKMHpjQaQjZ3i6o5qd95q

---------

Co-authored-by: Claude <[email protected]>
@changeset-bot

changeset-bot Bot commented May 18, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 0dd3369

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@socket-security

socket-security Bot commented May 18, 2026

Copy link
Copy Markdown

@pkg-pr-new

pkg-pr-new Bot commented May 18, 2026

Copy link
Copy Markdown
@fast-check/ava

npm i https://pkg.pr.new/@fast-check/ava@6996

fast-check

npm i https://pkg.pr.new/fast-check@6996

@fast-check/jest

npm i https://pkg.pr.new/@fast-check/jest@6996

@fast-check/packaged

npm i https://pkg.pr.new/@fast-check/packaged@6996

@fast-check/poisoning

npm i https://pkg.pr.new/@fast-check/poisoning@6996

@fast-check/vitest

npm i https://pkg.pr.new/@fast-check/vitest@6996

@fast-check/worker

npm i https://pkg.pr.new/@fast-check/worker@6996

commit: 0dd3369

…conflicts-TNHJ6

# Conflicts:
#	.github/workflows/build-status.yml
#	.github/zizmor.yml
@dubzzz
dubzzz force-pushed the claude/resolve-merge-conflicts-TNHJ6 branch from cd5aa82 to 0dd3369 Compare May 18, 2026 22:14
@dubzzz
dubzzz enabled auto-merge (squash) May 18, 2026 22:15
@dubzzz
dubzzz merged commit bd997fe into main May 18, 2026
50 checks passed
@dubzzz
dubzzz deleted the claude/resolve-merge-conflicts-TNHJ6 branch May 18, 2026 22:31
@codecov

codecov Bot commented May 18, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.78%. Comparing base (e1520e3) to head (0dd3369).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6996   +/-   ##
=======================================
  Coverage   94.78%   94.78%           
=======================================
  Files         212      212           
  Lines        5832     5832           
  Branches     1535     1535           
=======================================
  Hits         5528     5528           
  Misses        296      296           
  Partials        8        8           
Flag Coverage Δ
tests 94.78% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants