Skip to content

feat(release-pypi): spa-build-in-publish input (release without artifact storage) - #76

Merged
ghostkernel-core merged 1 commit into
masterfrom
spa-build-in-publish
Nov 11, 2026
Merged

ghostkernel-core merged 1 commit into
masterfrom
spa-build-in-publish

Conversation

@ghostkernel-core

Copy link
Copy Markdown
Contributor

Summary

  • New generic input spa-build-in-publish (boolean, default false) on release-pypi.yml: when true, the frontend job is skipped and the publish job runs npm ci && npm run build in frontend/ from the release tag checkout, so no upload-artifact/download-artifact hand-off is needed.
  • Why: the org hit its Actions artifact storage quota for November; CognitiveSystems v1.1.1 is tagged but its release (run 43002531440) failed at upload-artifact, so nothing was published.
  • The default is unchanged for all consumers. README input list updated.

Rollout

Merging ships nothing until v1 is advanced (manual). After that, the CognitiveSystems release.yml wrapper sets spa-build-in-publish: true, then a workflow_dispatch with tag_name: v1.1.1.

Test plan

  • YAML parses; pytest tests 25 passed; git diff --check
  • self-ci on this PR

🤖 Generated with Claude Code

…off)

The frontend job hands the built SPA to the publish job through an Actions
artifact. Once the org's artifact storage quota is hit (Free plan, GB-hours per
month), every release with has-frontend fails before publishing
(CognitiveSystems v1.1.1, run 43002531440). With spa-build-in-publish: true the
publish job builds the SPA itself from the release tag's checkout, so no
artifact is needed. The default is false, so existing consumers are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ghostkernel-core
ghostkernel-core requested a review from a team as a code owner November 11, 2026 14:15
@ghostkernel-core
ghostkernel-core merged commit 4d409d9 into master Nov 11, 2026
17 checks passed
@ghostkernel-core
ghostkernel-core deleted the spa-build-in-publish branch November 11, 2026 15:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant