Skip to content

Commit ef3257a

Browse files
committed
fix(gittensor-impact): switch to branch-mode publishing
GitHub now creates gh-release-created releases as immutable, so the action's default release publish-mode fails every run with HTTP 422 (Cannot upload assets to an immutable release) right after creating it. Branch mode force-pushes the SVGs to a dedicated orphan branch instead, which isn't subject to release immutability.
1 parent 9d966b8 commit ef3257a

1 file changed

Lines changed: 7 additions & 2 deletions

File tree

.github/workflows/gittensor-impact.yml

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,8 @@ jobs:
1717
runs-on: ubuntu-latest
1818
timeout-minutes: 10
1919
# Scoped here rather than at workflow level (defense-in-depth): this is the
20-
# only job that needs write access, to publish SVG assets to the pinned
21-
# `gittensor-impact` release via matthewevans/gittensor-impact-action.
20+
# only job that needs write access, to push SVG assets to the dedicated
21+
# gittensor-impact-assets branch via matthewevans/gittensor-impact-action.
2222
permissions:
2323
contents: write
2424
# matthewevans/gittensor-impact-action is a ~1.5-day-old repo; require a
@@ -29,3 +29,8 @@ jobs:
2929
uses: matthewevans/gittensor-impact-action@397fd470899cba47367458289a374eea9cb0d76a # main, 2026-07-06 (#1 per-repo API endpoint)
3030
with:
3131
title: Gittensory
32+
# GitHub's release-asset uploads now reject re-uploads to an
33+
# immutable release (HTTP 422), which the action's default
34+
# release publish-mode hits every run. Branch mode force-pushes
35+
# the SVGs to a dedicated orphan branch instead, sidestepping it.
36+
publish-mode: branch

0 commit comments

Comments
 (0)