Skip to content

ci: skip upgrading brew-managed pip on macOS runner - #23

Merged
Junbo-Zheng merged 1 commit into
mainfrom
ci
Aug 4, 2026
Merged

Junbo-Zheng merged 1 commit into
mainfrom
ci

Conversation

@Junbo-Zheng

Copy link
Copy Markdown
Collaborator

Summary

The macOS dependency-install step ran pip3 install -U pip setuptools,
which aborts on the GitHub-hosted macOS runner. Homebrew's python@3
formula installs pip without a RECORD file, so pip install -U pip
cannot uninstall the existing pip first:

error: uninstall-no-record-file
Cannot uninstall pip 26.1.2
The package's contents are unknown: no RECORD file was found for pip.

pynvim does not require a newer pip, so the upgrade is unnecessary.
This drops the upgrade line so the brew-managed pip is left untouched
and pynvim installs against stock pip.

The failure is environmental, not a code regression: the same install
step passed on the pull_request run (07-29) but failed on the
push-to-main run (08-01). Between those dates the GitHub macOS runner
image bumped brew's python@3 formula; the newer pip (26.1.2) it ships
lacks the RECORD file the upgrade path needs.

Impact

  • Users: None -- no end-user-facing behavior change; this only
    affects the CI install workflow.
  • Build: The install plugins from scratch workflow's macOS job no
    longer attempts a pip upgrade that fails on the brew-managed
    environment. Linux jobs are unchanged.
  • Hardware: None.
  • Documentation: None.
  • Security & Compatibility: None -- pynvim still installs; only
    the redundant pip/setuptools self-upgrade is removed.

Testing

Verified via the install plugins from scratch GitHub Actions workflow
on this branch. The macOS job previously failed at the dependency step
with error: uninstall-no-record-file (Cannot uninstall pip 26.1.2);
with the upgrade line removed, pip3 install pynvim --break-system-packages
succeeds on brew's stock pip and the job proceeds. Ubuntu jobs continue
to pass unchanged.

Before:

pip3 install -U pip setuptools --break-system-packages
-> error: uninstall-no-record-file (Cannot uninstall pip 26.1.2)

After:

pynvim installs on brew's stock pip; no pip upgrade attempted.

Signed-off-by: Junbo Zheng 3273070@qq.com

The macOS step ran `pip3 install -U pip setuptools`, which aborts on
the GitHub-hosted macOS runner: Homebrew's `python@3` installs pip
without a RECORD file, so `pip install -U pip` cannot uninstall the
old pip first:

  error: uninstall-no-record-file
  Cannot uninstall pip 26.1.2
  The package's contents are unknown: no RECORD file was found for pip.

pynvim does not require a newer pip, so the upgrade is unnecessary;
dropping it avoids the brew-managed-pip uninstall entirely.

The identical commit passed on the pull_request run (07-29) yet failed
on the push-to-main run (08-01) -- environmental, not a code regression.
Between those dates the GitHub macOS runner image bumped brew's
`python@3` formula; the newer pip (26.1.2) it ships lacks the RECORD
file the upgrade path needs. The PR run hit the older image where the
upgrade still worked.

Before:
  pip3 install -U pip setuptools --break-system-packages
  -> error: uninstall-no-record-file (Cannot uninstall pip 26.1.2)

After:
  pynvim installs on brew's stock pip; no pip upgrade attempted.

Assisted-by: Claude Code (GLM-5.2) <claude@anthropic.com>
Signed-off-by: Junbo Zheng <3273070@qq.com>
@Junbo-Zheng

Junbo-Zheng commented Aug 2, 2026 •

Copy link
Copy Markdown
Collaborator Author

@xaljer
Since the main branch, the last commit CI failed; see CI failure https://github.com/xaljer/nvide/actions/runs/30684375897

@Junbo-Zheng
Junbo-Zheng requested a review from xaljer August 2, 2026 16:26
@Junbo-Zheng
Junbo-Zheng merged commit 6e6b277 into main Aug 4, 2026
3 checks passed
@Junbo-Zheng
Junbo-Zheng deleted the ci branch August 4, 2026 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant