Repository navigation
feat(release-pypi): spa-build-in-publish input (release without artifact storage) - #76
Merged
Merged
Conversation
…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>
1 of 2 tasks
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.
Summary
spa-build-in-publish(boolean, defaultfalse) onrelease-pypi.yml: when true, thefrontendjob is skipped and the publish job runsnpm ci && npm run buildinfrontend/from the release tag checkout, so noupload-artifact/download-artifacthand-off is needed.upload-artifact, so nothing was published.Rollout
Merging ships nothing until
v1is advanced (manual). After that, the CognitiveSystemsrelease.ymlwrapper setsspa-build-in-publish: true, then aworkflow_dispatchwithtag_name: v1.1.1.Test plan
pytest tests25 passed;git diff --check🤖 Generated with Claude Code