Use canonical manylinux image in Linux release workflow

[Copilot]

The Linux release workflow failed during container initialization because it resolved the build image from the fork namespace (ghcr.io/<fork>/sapling/manylinux_2_34:latest), which was not reliably pullable at runtime. This blocked the release job before build steps started.

• Root cause

  • Release workflow container image was derived from github.repository, so fork-triggered runs attempted to pull the fork’s package path.

• Change

  • Updated .github/workflows/sapling-cli-manylinux-release.yml to use the canonical upstream image directly:
    • ghcr.io/facebook/sapling/manylinux_2_34:latest

• Impact

  • Fork-triggered release runs now consume the same known-good manylinux base image as upstream, avoiding fork package/tag resolution failures.

jobs:
  build:
    container:
      image: ghcr.io/facebook/sapling/manylinux_2_34:latest

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[facebook-github-tools]

@Copilot has updated the pull request. You must reimport the pull request before landing.

[facebook-github-tools]

@Copilot has updated the pull request. You must reimport the pull request before landing.

[meta-codesync]

@facebook-github-bot has imported this pull request. If you are a Meta employee, you can view this in D96661376. (Because this pull request was imported automatically, there will not be any future comments.)