Closed EliahKagan closed 1 year ago
Disabling stale
was actually intentional. It was marking things stale that weren't actually wrong, due to either a lack of time on my part or significant complexity.
That makes sense. Would it be reasonable to remove the stale
workflow?
I've opened #256 to propose removal of the stale
workflow.
(If you would prefer not to do that, then #256 can of course simply be closed without merging.)
This updates versions of GitHub Actions, except in the
stale.yml
workflow. The upgraded actions in other workflows arecheckout
,setup-python
, andgh-action-pypi-publish
.The checkout and setup-python actions were upgraded across major versions. Although it is possible for major version updates to introduce incompatibilities, I believe the advantages decisively outweigh the disadvantages, because:
For
gh-action-pypi-publish
, the minor version upgrade includes security updates to internal dependencies. This happened in 1.8.9.I have not touched
stale.yml
here, even though the action it uses is specified to use a very old version, because that workflow is currently disabled (which appears to have been done automatically at some point during a lull in activity when no repository activity was detected for 60 days). Modifying it might re-enable it, which might not be desired.