Which packages are affected?

• @eslint/compat
• @eslint/config-array
• @eslint/config-helpers
• @eslint/core
• @eslint/mcp
• @eslint/migrate-config
• @eslint/object-schema
• @eslint/plugin-kit

Environment

GitHub Actions

What did you do?

CI fails when a Release Please PR is created or updated, for example #365:

• https://github.com/eslint/rewrite/actions/runs/21663746988?pr=365

Same error on the main branch when the PR is merged, e.g.:

• https://github.com/eslint/rewrite/actions/runs/20856061969/attempts/1

What did you expect to happen?

The CI run should pass.

What actually happened?

The workflow is failing because some packages rely on a version of another package that hasn't been yet published. For example, in https://github.com/eslint/rewrite/actions/runs/21663746988/job/62454109130, config-array is updated to depend on @eslint/object-schema v3.0.1, which is currently not published.

Apparently, package managers other than npm don't resolve the dependency from the local workspace and instead complain that it doesn't exist.

Run yarn add ./*.tgz -D
  yarn add ./*.tgz -D
  shell: /usr/bin/bash -e {0}
yarn add v1.22.22
info No lockfile found.
[1/4] Resolving packages...
error Couldn't find any versions for "@eslint/object-schema" that matches "^3.0.1"
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
Error: Process completed with exit code 1.

Link to Minimal Reproducible Example

See above

Participation

• I am willing to submit a pull request for this issue.

Additional comments

The workflow description is located in eslint/workflows, but the problem only occurs here because this is a monorepo.

I think the workflow should be updated so that dependencies from this repo are looked up locally by package managers, like npm does. If that's not possible, we could disable the workflow for Release Please PRs and their respective merge commits. That should be safe since those autogenerated PRs don't change the build infrastructure.