You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.github/workflows/ci.yml's python job pinned actions/setup-python@v5. The action's current release is v7.0.0 (confirmed via the action's GitHub releases) — two majors behind, while every other action in this workflow (actions/checkout@v7, actions/setup-node@v6, pnpm/action-setup@v6) is kept current. This looked like drift rather than an intentional pin.
Solution
Bumped the pin to actions/setup-python@v7. Checked the v7.0.0action.yml: the python-version input this workflow relies on is unchanged (the only removed input, pip-install, isn't used here), so this is a drop-in version bump with no other workflow changes needed.
Verification
I can't execute GitHub Actions from this sandbox, but:
Confirmed v7.0.0 is the action's current release via its GitHub release metadata.
Diffed the v5 vs v7action.yml inputs — python-version (the only input this job passes) is untouched.
The diff is a single-line version bump; no other step, dependency version, or metadata was touched, per the issue's scope.
The PR's own CI run is the actual verification that the python job (poetry install, ruff check, compileall) still passes on v7.
The bundle file is available in the agent artifact in the workflow run linked above.
To create a pull request with the changes:
# Download the artifact from the workflow run
gh run download 31101926321 -n agent -D /tmp/agent-31101926321
# Fetch the bundle into a temporary ref, then update the local branch
git fetch /tmp/agent-31101926321/aw-pinecone-io-pinecone-neo4j-explorer-agent-maintenance-issue-63.bundle refs/heads/agent/maintenance/issue-63:refs/bundles/create-pr-agent-maintenance-issue-63-0c6281a426d35db6-4d1ea317
git update-ref refs/heads/agent/maintenance/issue-63-0c6281a426d35db6 refs/bundles/create-pr-agent-maintenance-issue-63-0c6281a426d35db6-4d1ea317
git checkout agent/maintenance/issue-63-0c6281a426d35db6
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d refs/bundles/create-pr-agent-maintenance-issue-63-0c6281a426d35db6-4d1ea317
# Push the branch to origin
git push origin agent/maintenance/issue-63-0c6281a426d35db6
# Create the pull request
gh pr create --title 'chore: bump actions/setup-python v5 → v7 in ci.yml' --base main --head agent/maintenance/issue-63-0c6281a426d35db6 --repo pinecone-io/pinecone-neo4j-explorer
Problem
.github/workflows/ci.yml'spythonjob pinnedactions/setup-python@v5. The action's current release isv7.0.0(confirmed via the action's GitHub releases) — two majors behind, while every other action in this workflow (actions/checkout@v7,actions/setup-node@v6,pnpm/action-setup@v6) is kept current. This looked like drift rather than an intentional pin.Solution
Bumped the pin to
actions/setup-python@v7. Checked thev7.0.0action.yml: thepython-versioninput this workflow relies on is unchanged (the only removed input,pip-install, isn't used here), so this is a drop-in version bump with no other workflow changes needed.Verification
I can't execute GitHub Actions from this sandbox, but:
v7.0.0is the action's current release via its GitHub release metadata.v5vsv7action.ymlinputs —python-version(the only input this job passes) is untouched.The PR's own CI run is the actual verification that the
pythonjob (poetry install,ruff check,compileall) still passes onv7.Closes #63
Note
This was originally intended as a pull request, but the git push operation failed.
Original error: The process '/usr/bin/git' failed with exit code 128
Workflow Run: View run details and download bundle artifact
The bundle file is available in the
agentartifact in the workflow run linked above.To create a pull request with the changes: