ci: development as integration branch, CI gate, pre-release channel - #22
Merged
Conversation
Adds CI (build+lint on PRs/pushes) and an automated main->development sync so hotfixes/direct pushes to main don't leave development stale. Renovate now targets development instead of main so dependency bumps batch into a single release instead of triggering one each.
…ly promotion, and syncing development
Keeps dependency-update PRs from landing mid-week or over the weekend; they'll be waiting, green-or-red, when the week starts.
Security patches shouldn't wait up to 6 days for the weekly window.
dependencyDashboardApproval already gates PR creation on manual checkbox approval, which is the actual behavior wanted — approve and test when there's time, not wait for a cron window. The schedule was redundant and would have delayed PR creation past approval.
development is now the beta channel: every push publishes a pre-release build (odd-minor versioning per VS Code's convention) that users can opt into via 'Switch to Pre-Release Version', while main stays the verified/stable track.
release-please.yml was accidentally removed in 83841ab alongside the obsolete nightly workflows -- it's what cuts stable releases and publishes to the Marketplace/Open VSX, so it needs to stay on main. sync-main-to-development.yml duplicated propagate-main-to-development.yml (same trigger, same job); keeping the latter since it reuses an existing open PR instead of force-pushing a branch, and labels it.
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
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
developmentas the integration branch: feature/dep-update work lands here first, batches, then promotes tomainwhen ready — instead of every merge triggering its own release.ci.yml: build + lint required on PRs intomain/development(previously nothing gated merges at all).mainanddevelopment: PR + passing CI required, owner can still bypass for hotfixes.development(baseBranchPatterns) and keepsdependencyDashboardApproval: true— dependency PRs only open when explicitly approved via the Dependency Dashboard, no schedule involved.prerelease.yml: every push todevelopmentpublishes a pre-release build to the VS Code Marketplace and Open VSX (odd-minor versioning per Marketplace convention, e.g.1.5.xwhile stable is1.4.x) — already live,1.5.2is the current pre-release.mainstays the verified/stable channel viarelease-please.codeql.yml,pr-title-lint.yml,propagate-main-to-development.yml(auto-opens a draft PR syncingmain→developmentafter any hotfix/direct push), and the corrected repository URLs inpackage.json.Test plan
ci.ymlbuild+lint passing ondevelopment(run 31545807980)prerelease.ymlpublished1.5.1and1.5.2successfully to both registriesrelease-please.ymlis unchanged frommain(an earlier commit on this branch had accidentally deleted it; restored before opening this PR)