Fix PyPI version mismatch - build jobs now checkout version bump tag

[Copilot]

Build jobs were checking out the PR merge commit instead of the version bump commit, causing PyPI to receive wheels with stale versions while GitHub releases showed the correct version.

Changes

Build jobs (linux-wheels, os-wheels):

• Explicitly checkout version tag: ref: v${{ needs.version-bump.outputs.new_version }}
• Add conditional: if: needs.version-bump.outputs.version_changed == 'true'

Publish job (pypi-publish):

• Add version-bump to needs (required for output access)
• Add conditional: if: needs.version-bump.outputs.version_changed == 'true'

linux-wheels:
  needs: [version-bump]
  if: needs.version-bump.outputs.version_changed == 'true'
  steps:
    - uses: actions/checkout@v4
      with:
        ref: v${{ needs.version-bump.outputs.new_version }}

Without an explicit ref, actions/checkout@v4 defaults to the workflow trigger commit (PR merge), which precedes the version bump commit. Build jobs now checkout the tag created by version-bump, ensuring source files contain the bumped version.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>GitHub Release is correct version but PyPi publish is not synced to latest version</issue_title>
<issue_description></issue_description>

<agent_instructions>the publish CI is not pushing the correctly versioned release to PyPI</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes GitHub Release is correct version but PyPi publish is not synced to latest version #61

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.