chore(release): promote staging to production - #2844
Merged
Merged
Conversation
Dual-target deploy during the CloudFront migration: staging builds now also publish to qovery-console-staging (the OAC origin behind CloudFront) and invalidate the cached index.html. The legacy bucket keeps serving console-staging.qovery.com until the DNS cutover. Production is intentionally unchanged; it opts in later by passing s3-bucket-name-with-cloudfront and cloudfront-distribution-id. Requires the frontend-code-push IAM policy update (s3:PutObject on the new bucket + cloudfront:CreateInvalidation) before merge.
Production releases now also publish to qovery-console-prod (the OAC origin behind CloudFront) and invalidate the cached index.html, using the dual-target support already merged for staging. The legacy bucket keeps serving console.qovery.com until the DNS cutover. IAM (frontend-code-push) already grants both buckets and distributions.
* feat(variables): separate secret creation flow * fix(variables): mask secret values on edit * fix(variables): prefill file path on focus * chore(variables): inline creation flow actions * chore(variables): rely on button spacing * chore(variables): simplify variable modal state * fix(variables): remove path placeholder * fix(variables): use file title wording * chore(variables): simplify variable creation actions
* fix(services): isolate agentic workflows from service list * chore(services): remove unrelated api changes * fix(services): preserve editable service fallback
Member
Author
|
🎉 This PR is included in version 1.331.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #2844 +/- ##
==========================================
- Coverage 47.90% 47.64% -0.26%
==========================================
Files 1213 1197 -16
Lines 26262 25952 -310
Branches 7804 7774 -30
==========================================
- Hits 12581 12366 -215
+ Misses 11554 11468 -86
+ Partials 2127 2118 -9
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
3 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.
Opens the production promotion path from staging to main. Merging this PR triggers semantic-release, then the existing production deployment workflow.
Do not squash this PR. Use a merge commit to preserve the original conventional commits for semantic-release.