chore(ci): drop the 0.4.x Trusted Publisher migration note - #16
Merged
Conversation
The note tracked a one-time setup step: `everos-cloud` was published from github.com/evermemos/everos-cloud-python through 0.4.1, so releasing from this repo required adding a Trusted Publisher for it to the existing PyPI project. That's done — 1.0.0 shipped from this workflow — so the note is spent, and now that the repo is public it reads as a stale internal memo. The surrounding comment already states the standing requirement (a Trusted Publisher must point at this repo + workflow), which is the part worth keeping. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LdqRBYsdEoyC45w9525Zjx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes a 4-line comment block from
.github/workflows/publish.yml.The note recorded a one-time setup step —
everos-cloudwas published fromgithub.com/evermemos/everos-cloud-pythonthrough 0.4.1, so publishing fromthis repo needed a Trusted Publisher for it added to the existing PyPI project.
1.0.0 shipped from this workflow, so that's settled. With the repo now public
it just reads as a stale internal memo.
The preceding comment keeps the part that still matters: a Trusted Publisher
must be configured for
everos-cloudpointing at this repo +publish.yml.Comment-only — no change to triggers, permissions, or steps. Verified the YAML
still parses (
on.push.tags: ['v*.*.*'], 5 steps,id-token: writeintact).🤖 Generated with Claude Code
https://claude.ai/code/session_01LdqRBYsdEoyC45w9525Zjx