Skip to content

Follow up on #638 - fix pypi publish action version handling#640

Merged
raboof merged 1 commit intomainfrom
follow-up-with-pypi-publish
Apr 1, 2026
Merged

Follow up on #638 - fix pypi publish action version handling#640
raboof merged 1 commit intomainfrom
follow-up-with-pypi-publish

Conversation

@potiuk
Copy link
Copy Markdown
Member

@potiuk potiuk commented Mar 30, 2026

Summary

Follow-up to #638 which was mistakenly merged too fast.

  • Remove keep: true from the older pypa/gh-action-pypi-publish v1.12.4 — only the newest version (v1.13.0) should have keep: true
  • Update README to better document the process of adding older vs newer versions of already approved actions

Test plan

  • Verify actions.yml correctly marks only v1.13.0 with keep: true
  • Verify README documentation is clear about the two cases (newest vs older version)

🤖 Generated with Claude Code

The previous version (v1.12.4) should not have `keep: true` as it's not the
newest version. Also updates README to better document the process of adding
older vs newer versions of already approved actions.

Generated-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@potiuk potiuk requested review from dave2wave, dfoulks1 and raboof March 30, 2026 22:41
Copy link
Copy Markdown
Member

@dave2wave dave2wave left a comment

Choose a reason for hiding this comment

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

LGTM - but maybe add a note that keep and expires_at are mutually exclusive. Does one take precedence over the other?

Copy link
Copy Markdown
Member

@raboof raboof left a comment

Choose a reason for hiding this comment

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

good improvement, though the docs are getting hard to digest and in need of a good wider review at this point.

@raboof raboof merged commit 97e7ecd into main Apr 1, 2026
6 checks passed
@raboof raboof deleted the follow-up-with-pypi-publish branch April 1, 2026 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants