ci(SDKE-1128): migrate Core Web SDK to trunk-based development#1212
Open
alexs-mparticle wants to merge 1 commit intodevelopmentfrom
Open
ci(SDKE-1128): migrate Core Web SDK to trunk-based development#1212alexs-mparticle wants to merge 1 commit intodevelopmentfrom
alexs-mparticle wants to merge 1 commit intodevelopmentfrom
Conversation
alexs-mparticle
force-pushed
the
feat/SDKE-1047-trunk-based
branch
from
ff173a6 to
5bfb105
Compare
alexs-mparticle
changed the title
alexs-mparticle
force-pushed
the
feat/SDKE-1047-trunk-based
branch
from
5bfb105 to
31ce4ae
Compare
Replace Gitflow branch model (development/master/staging-step-1/2/3) with trunk-based development using main as trunk and an auto-updated staging branch for E2E testing and releases. - Add release-step-1.yml: automatic staging pipeline on push to main - Add release-step-2.yml: manual release order push for CDN - Add release-step-3.yml: semantic-release from staging, publish to NPM/CDN - Remove staging-step-1/2/3.yml (replaced by new pipeline) - Update pull-request.yml to compare bundle size against main (not master) - Remove pr-branch-target-gitflow check from reusable-workflows.yml - Point dependabot and security checks at main - Point release.config.js branches at staging NOTE: After merging, the following branches should be deleted: - development - master (replaced by main) - release-order-a/b/c (managed via release-step-2 workflow) mPServer must be updated to reference main instead of master for the Core Web SDK GitHub repo (see linked Jira ticket).
alexs-mparticle
force-pushed
the
feat/SDKE-1047-trunk-based
branch
from
31ce4ae to
4ae6e8d
Compare
|
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
1 participant
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
development/master/staging-step-1/2/3) with trunk-based development usingmainas trunk and an auto-updatedstagingbranch for E2E testing and releasesrelease-step-1.yml(automatic staging on push to main),release-step-2.yml(manual release order for CDN),release-step-3.yml(semantic-release from staging, publish to NPM/CDN)staging-step-1/2/3.yml, update PR workflow to compare againstmain, remove gitflow checks, point dependabot/security atmaindependabot-automerge.yml,dependabot-branch-rebase.yml, andautomerge-dependabotjob — dependabot PRs now targetmaindirectly for manual review (GChat notification already fires for all PRs)Post-merge actions
development,master,release-order-a/b/c,chore/dependabotmaininstead ofmaster(SDKE-1127)mainstagingbranchTest plan
[skip ci]commits do NOT re-trigger staging pipelineJira: SDKE-1128