chore(ci): remove legacy S3 CDN deploy from release-web#744
Merged
Conversation
The release-web workflow no longer uploads build output to CDN and no longer depends on AWS secrets. Keep artifact upload only to match the current release process. Made-with: Cursor
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
originalix
approved these changes
Apr 9, 2026
originalix
requested changes
Apr 9, 2026
Keep PUBLIC_PATH injection in release-web workflow while removing legacy CDN upload and AWS secrets usage. Made-with: Cursor
originalix
reviewed
Apr 9, 2026
Keep PUBLIC_PATH at job level and also pass it explicitly to the build step for clarity after removing duplicate build/deploy flow. Made-with: Cursor
ByteZhang1024
approved these changes
Apr 9, 2026
originalix
approved these changes
Apr 9, 2026
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
release-webworkflowAWS_KEY_ID,AWS_SECRET_ACCESS_KEY,AWS_BUCKET) and CDN path envsTest plan
deploy-release-iframe-webworkflow manuallyMade with Cursor