From 077c6521d523e4b2852f5c186c6c1a65335515ed Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Krzysztof=20Ko=C5=82odzi=C5=84ski?= Date: Mon, 29 Jun 2026 14:40:08 +0200 Subject: [PATCH] fix: stopped uploading frontend to gh release --- .github/workflows/release.yml | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 7d696813..d969859d 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -83,15 +83,11 @@ jobs: - name: Build package run: make build - # TODO: also publish the frontend bundle to a CDN as part of the release, - # so deployments can opt out of serving it from Flask via - # GOODMAP_FRONTEND_LIB_URL. Until then it ships bundled in the wheel and is - # only attached to the GitHub Release below. - - name: Attach frontend bundle to GitHub Release - env: - GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} - run: gh release upload "${{ needs.release-please.outputs.tag_name }}" goodmap/static/frontend/index.min.js --clobber - + # TODO: publish the frontend bundle to a CDN as part of the release, so + # deployments can opt out of serving it from Flask via + # GOODMAP_FRONTEND_LIB_URL. The bundle ships inside the wheel (pyproject + # include); it is intentionally NOT attached to the GitHub Release because + # published releases are immutable and reject post-publish asset uploads. - name: Publish package distributions to PyPI uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b with: