From 5577e846e774031c03211aecb3138d159341a542 Mon Sep 17 00:00:00 2001 From: Dani Date: Fri, 31 Jul 2026 20:58:51 -0400 Subject: [PATCH] chore(ci): drop the 0.4.x Trusted Publisher migration note MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) Claude-Session: https://claude.ai/code/session_01LdqRBYsdEoyC45w9525Zjx --- .github/workflows/publish.yml | 5 ----- 1 file changed, 5 deletions(-) diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index 9813278..5fe3457 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -3,11 +3,6 @@ # The SDK factory pushes generated source + an annotated `vX.Y.Z` tag to this repo; # that tag triggers this workflow. PyPI must have a Trusted Publisher configured for # project `everos-cloud` pointing at this repo + workflow (`publish.yml`). -# -# NOTE: `everos-cloud` predates this factory — it was published from -# github.com/evermemos/everos-cloud-python up to 0.4.1. Publishing from here needs a -# Trusted Publisher for THIS repo added to that existing PyPI project; the 0.4.x -# publisher does not carry over. name: publish on: