Skip to content

chore(actions)(deps): bump actions/setup-python from 6.2.0 to 7.0.0 - #29

Merged
bbasketballer75 merged 1 commit into
mainfrom
dependabot/github_actions/actions/setup-python-7.0.0
Aug 3, 2026
Merged

chore(actions)(deps): bump actions/setup-python from 6.2.0 to 7.0.0#29
bbasketballer75 merged 1 commit into
mainfrom
dependabot/github_actions/actions/setup-python-7.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 3, 2026

Copy link
Copy Markdown

Bumps actions/setup-python from 6.2.0 to 7.0.0.

Release notes

Sourced from actions/setup-python's releases.

v7.0.0

What's Changed

Enhancements

Bug Fix

Dependency Upgrade

New Contributors

Full Changelog: actions/setup-python@v6...v7.0.0

v6.3.0

What's Changed

Enhancement

Dependency update

Documentation

New Contributors

Full Changelog: actions/setup-python@v6.2.0...v6.3.0

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [actions/setup-python](https://github.com/actions/setup-python) from 6.2.0 to 7.0.0.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@a309ff8...5fda3b9)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Aug 3, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: github-actions. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Aug 3, 2026

@bbasketballer75 bbasketballer75 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 hermes automated review

  • 4 files changed, 4 additions, 4 deletions
  • ❌ tests failed
    npm error Missing script: "test"
    npm error
    npm error To see a list of scripts, run:
    npm error   npm run
    npm error A complete log of this run can be found in: C:\Users\bbask\AppData\Local\npm-cache\_logs\2026-08-03T11_01_02_710Z-debug-0.log
    
    

No heuristic issues detected.


Review generated by hermes pr-reviewer. Trust but verify.

@bbasketballer75 bbasketballer75 added the ci-reviewed CI-sensitive changes reviewed label Aug 3, 2026
@bbasketballer75
bbasketballer75 merged commit ad962e5 into main Aug 3, 2026
100 of 103 checks passed
@bbasketballer75
bbasketballer75 deleted the dependabot/github_actions/actions/setup-python-7.0.0 branch August 3, 2026 19:01
bbasketballer75 added a commit that referenced this pull request Aug 4, 2026
Backport of the fix proposed upstream in NousResearch#78107,
applied here so this fork's CI stops failing slice 8/8 on every PR while that
one is in review.

`stream_consumer.py:1718` computes preview age as
`time.monotonic() - self._message_created_ts`. monotonic()'s epoch is
arbitrary (on Linux, boot), so setting `_message_created_ts = 0.0` does not
mean "long ago" — it means "monotonic() seconds ago". On a freshly-booted
runner that is a handful of seconds, so the age falls under the 60s threshold,
fresh-final never fires, and `adapter.send.call_count` is 1 instead of 2.

That is why it is intermittent: it passed on #26/#27/#28/#29 and failed on
#25 and #30, purely as a function of runner uptime.

Fixed by anchoring to the same clock the production code reads. No assertion
weakened, no production code changed.

Verified: 10/10 in the file; and with time.monotonic patched to 12.0 to
simulate a host booted 12 seconds ago, the test passes where the old form
fails at line 79 — the exact CI failure.

Touches only tests/, so it does not trip the ci-reviewed workflow gate.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
bbasketballer75 added a commit that referenced this pull request Aug 4, 2026
In this repo the `# vX` comment beside a SHA pin is the human audit trail --
it is the only way a reader knows what version a 40-char hash represents.
Three of them were wrong or imprecise. Resolved every pinned SHA against the
GitHub tags API and rewrote the comments to match.

  actions/setup-python@5fda3b95a4ea...     # v5      -> # v7.0.0   (WRONG)
  actions/upload-artifact@043fb46d1a93...  # v7      -> # v7.0.1   (imprecise)
  actions/download-artifact@d3f86a106a...  # v4      -> # v4.3.0   (imprecise)

The setup-python comment was the actual defect: it read `# v5` while pinning
v7.0.0 -- two majors off. It was already stale before the dependabot bump in
#29; dependabot rewrites the SHA but never the comment, so the error survived.
The other two are the same SHA carrying different labels in different files
(`# v7` in ci.yml, `# v7.0.1` in tests.yml), which makes the pins look like
they diverge when they do not.

Comment-only. Every SHA is byte-identical before and after -- verified by
diffing the changed lines and confirming all three hashes appear unchanged on
both sides. All 7 workflow files still parse as YAML. No behavior change.

Not included, deliberately: the upload/download-artifact *version* drift
(tests.yml pairs upload v7.0.1 with download v8.0.1; docker.yml and
js-autofix.yml pair v7.0.1 with v4.3.0). Those combinations work today --
upload-artifact v7 only breaks a v4 download when `archive: false` is set,
which no workflow here does, and the v3->v4 backend split is the only true
incompatibility. Normalizing download-artifact to v8 is a real behavior change
(v8 errors on hash mismatch and no longer auto-unzips non-zipped files), so it
belongs in its own reviewed PR rather than riding along with a comment fix.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-reviewed CI-sensitive changes reviewed dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant