SPEC0 action failing to reach PR

[tsbinns]

This week our SPEC0-like rules should have updated several minimum dependency versions, but the workflow failed to produce a PR: https://github.com/mne-tools/mne-python/actions/runs/21123144706/job/60739270331

I can replicate this locally that pyproject.toml gets updated as expected, but when the pre-commit hook update-env-file is run (copying the changes to environment.yml), the hook fails because it does introduce changes to environment.yml. Therefore the action errors out before the PR can be created.

I question whether we need to call pre-commit prior to creating the PR. It is enough to update pyproject.toml, open the PR, then let the pre-commit PR action auto-fix copying the changes to environment.yml.

The pre-commit call was added in #13534, and I think this is the first time the SPEC0 action has had a minimum version to update since then.

[tsbinns]

Also, it seems mne-bot added the pre-commit call alongside the SPEC0 changes. Is this expected?

[larsoner]

It was intentional just to try to avoid CircleCI auth issues but we can remove it if it's being a problem. I would just add a || true (or whatever it is) to the pre-commit call though, it should still push changes after that

[larsoner]

@tsbinns do you want to open a PR with || true and temporarily on: pr in it to get it to run? The "open PR" step should fail but we should see it try to do it and be able to see the diff. Then we can merge it and I can workflow_dispatch: run the PR in main