Remove GitHub Release asset upload step from CI workflow#330
Merged
ritikarawlani merged 1 commit intomainfrom Apr 1, 2026
Merged
Remove GitHub Release asset upload step from CI workflow#330ritikarawlani merged 1 commit intomainfrom
ritikarawlani merged 1 commit intomainfrom
Conversation
The `create_package_release.py` step was creating a new GitHub Release on every successful CI build (every push, every PR), which conflates CI (build + deploy to gh-pages) with release management. Package release creation will live in the release workflow instead. The >100MB cleanup step remains to prevent gh-pages bloat. https://claude.ai/code/session_014xeaCmB7K2aXe9T8GV9m2f
Contributor
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
Contributor
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
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
2 participants
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
Removed the "Upload FHIR package assets as GitHub Release" step from the GitHub Actions workflow. This step was responsible for uploading large package files (package.db, package.tgz, package.r4.tgz, package.r4b.tgz, and ai.zip) as binary assets to GitHub Releases instead of deploying them to gh-pages.
Changes
Upload FHIR package assets as GitHub Releasejob step from.github/workflows/ghbuild.ymlcreate_package_release.pyImpact
Large package files will no longer be automatically uploaded as GitHub Release assets during the CI/CD pipeline. The subsequent "Delete files >100MB before deployment" step remains in place for the gh-pages deployment process.
https://claude.ai/code/session_014xeaCmB7K2aXe9T8GV9m2f