Skip to content

Release script fixes - #64

Open
trasher wants to merge 1 commit into
developfrom
feature/release-script-fixes
Open

Release script fixes#64
trasher wants to merge 1 commit into
developfrom
feature/release-script-fixes

Conversation

@trasher

@trasher trasher commented Sep 5, 2026

Copy link
Copy Markdown
Member

This script is a copy of Galette core's and had been left on the pre-migration generation, so it carries both the bugs found in the core and the alignment the other plugins already got.

Subprocess exit codes were never looked at, so a failed composer install produced an archive without vendor/ while the script exited 0 announcing a release. They now go through one helper that stops the build.

msg is None on that branch, so msg += raised a TypeError instead of saying what it had found, when a detached signature exists without its archive.

The "does this release already exist?" check asked an HTTPS repository on port 80, where the server answers a 301. status == 200 was therefore false for every version, published or not, and the guard never fired.

Also brought in line with the migrated plugins: /usr/bin/python no longer exists on a runner, the urlgrabber import is dead and is not installed by the shared action, --no-sign is what the release workflow passes, dist/ has to be created on a fresh checkout, and a lightweight tag carries no tag object to read. assume_yes moves above the -f prompt, which it is supposed to answer.

This script is a copy of Galette core's and had been left on the
pre-migration generation, so it carries both the bugs found in the core
and the alignment the other plugins already got.

Subprocess exit codes were never looked at, so a failed composer install
produced an archive without vendor/ while the script exited 0 announcing
a release. They now go through one helper that stops the build.

`msg` is None on that branch, so `msg +=` raised a TypeError instead of
saying what it had found, when a detached signature exists without its
archive.

The "does this release already exist?" check asked an HTTPS repository on
port 80, where the server answers a 301. `status == 200` was therefore
false for every version, published or not, and the guard never fired.

Also brought in line with the migrated plugins: `/usr/bin/python` no
longer exists on a runner, the `urlgrabber` import is dead and is not
installed by the shared action, `--no-sign` is what the release workflow
passes, `dist/` has to be created on a fresh checkout, and a lightweight
tag carries no tag object to read. `assume_yes` moves above the `-f`
prompt, which it is supposed to answer.
@trasher
trasher requested a review from gagnieray September 5, 2026 11:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant