Repository navigation
release: notes for v2.3.0 and fix the Docker-trigger secret name - #2733
Merged
Merged
Conversation
Prep for the v2.3.0-pre1 probe release. - docs/release-notes.md: v2.3.0 entry covering the 22 commits since v2.1.11. The file still stopped at v2.1.0 (Jan 2025), and the 2.2.0 pre-releases were cut from a line that never landed on master (v2.2.0-pre5 is not an ancestor of master), so 2.3.0 is the next coherent version. - release.yml: read `secrets.AARON_TOKEN` instead of `secrets.AARON_TRIGGER`. The repo only has a secret named AARON_TOKEN, so the lncm Docker dispatch step has been silently skipping. - docs/AGENTS: follow the rename.
✅ Deploy Preview for specter-desktop-docs canceled.
|
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
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.
Zweck
Vorbereitung für den Proberelease-Tag
v2.3.0-pre1(→ PyPI2.3.0rc1).Warum
v2.3.0und nichtv2.2.0-pre6v2.2.0-pre5ist kein Vorfahre vonmaster(git merge-base --is-ancestor v2.2.0-pre5 upstream/master→ exit 1).git describe --tagsliefertv2.1.11-22-g<sha>, undgit describe --match 'v2.2.0*'findet gar nichts. Die 2.2.0-pre-Releases wurden also auf einer Linie gebaut, die nie inmastergelandet ist.masterist faktischv2.1.11+ 22 Commits. Damit istv2.3.0die nächste kohärente Version;2.2.0rc1/rc5bleiben auf PyPI liegen, aber als rc ohnehin vonpip installignoriert.Änderungen
docs/release-notes.md— neuerv2.3.0-Eintrag über die 22 Commits seitv2.1.11(BIP-329-Import Add backwards-compatible BIP-329 label import and export #2712, Taproot-Flag BitBox02 Add Taproot support flag for BitBox02 #2705, Specter-DIY-xpub-Import Specter-DIY: import xpubs without the 3s timeout, one confirmation per key set, wrong-network handling #2702, Coldcard-Fix Fix Coldcard USB warning flow #2698, Intel-macOS Restore Intel macOS release compatibility #2692, Dependabot-Bumps u.a.). Die Datei stand noch aufv2.1.0(Jan 2025)..github/workflows/release.yml—secrets.AARON_TOKENstattsecrets.AARON_TRIGGER. Im Repo existiert nur ein SecretAARON_TOKEN, weshalb dertrigger-docker-Job bisher immer stummskipping Docker triggergeloggt hat. Log-Meldung angepasst.docs/release-guide.md,docs/continuous-integration.md,AGENTS.md— Secret-Name nachgezogen.Test
YAML geparst (9 Jobs), keine
AARON_TRIGGER-Referenzen mehr. Der eigentliche Beweis kommt vom Tag:release.ymlläuft erst beiv2.3.0-pre1.