Repository navigation
ci(release): adopt GitFlow and deploy published tags - #5
Merged
Merged
Conversation
samankassou
changed the title
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.
Adopt GitFlow: feature PRs target develop; release and hotfix branches stabilize before merge commits into main and back-merges into develop. Release Please generates version/changelog PRs against release/* and hotfix/* only. CI covers all long-lived and stabilization branches.
Production deployment follows successful tag verification and GitHub publication. Render uses a commit-specific deploy hook, with auto-deploy disabled in the Blueprint. Its response confirms deployment acceptance, not completion. Old-tag retries cannot deploy over newer main. Pending release labels are cleared using preserved GitFlow ancestry.
Required activation: turn Render Auto-Deploy Off, retain branch main, and configure RENDER_DEPLOY_HOOK_URL. Setup confirmation is pending. After this one-time infrastructure PR merges, merge main into develop preserving history.
Validation: workflow YAML, pinned actions, Bash syntax and hosting configuration checks passed. Local Git fixtures verified current published tags are accepted and old or unpublished tags rejected. Live deployment needs hosting credentials and must be verified on the next release.