Skip to content

ci: run on the 0.x release branch and version branches after it - #86

Merged
Decipher merged 1 commit into
0.xfrom
feature/version-branches
Oct 31, 2026
Merged

Decipher merged 1 commit into
0.xfrom
feature/version-branches

Conversation

@Decipher

@Decipher Decipher commented Oct 31, 2026 •

Copy link
Copy Markdown
Member

The trunk is now 0.x, one release branch per major, as in druxt.js. main is renamed on GitHub and replaced on the mirror, and the open pull requests moved with it. This change updates the configuration that still named main.

What changes

File Before After
.github/workflows/ci.yml main only Pushes to '*.x', and every pull request whatever its base
.github/workflows/codeql-analysis.yml develop, which never existed here, so only the weekly schedule ran The same triggers as CI
renovate.json main Every <major>.x or <major>.<minor>.x branch
.changeset/config.json baseBranch: main baseBranch: 0.x
README.md CI and coverage badges for main For 0.x
CONTRIBUTING.md Says nothing about branches Says to branch from 0.x and target it

A repository made from the template starts on 0.x, since GitHub copies the default branch with its name.

Testing

  • The Renovate pattern matches 0.x, 1.x, 1.2.x and 10.x, and not main or feature/x.
  • yamllint, prettier, cspell and Vale pass on the changed files. The commit hooks passed.
  • This pull request targets 0.x, so its own CI run checks the new pull_request trigger.

#82 still names main in the release workflow. It moves to '*.x' when it is rebased onto this.

Summary by CodeRabbit

  • Documentation
    • Added guidance on release branches and where to target contributions.
  • Chores
    • Updated CI and security checks to run across release branches and pull requests targeting any branch.
    • Updated automated dependency updates and project badges to follow the current release branch.

The trunk is renamed from main to 0.x, one release branch per major, as in
druxt.js. CI and CodeQL run on pushes to any '*.x' branch, and on every pull
request whatever its base. CodeQL listed develop, a branch this repository
never had, so it ran on its schedule only. Renovate targets every version
branch, changesets reads 0.x as its base, and the README badges follow 0.x.
CONTRIBUTING says which branch to work from.
@coderabbitai

coderabbitai Bot commented Oct 31, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
Commits

Reviewing files that changed from the base of the PR and between b545c8a and 59e58b2.

Files selected for processing: 6
  • .changeset/config.json
  • .github/workflows/ci.yml
  • .github/workflows/codeql-analysis.yml
  • CONTRIBUTING.md
  • README.md
  • renovate.json

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Walkthrough

The repository now uses 0.x and other versioned release branches for contributor guidance, Changesets, Renovate, README badges, CI, and CodeQL. Pull request triggers no longer restrict target branches.

Changes: Release branch targeting

Layer / File(s) Summary
Document the release branch convention
CONTRIBUTING.md, .changeset/config.json
Contributor guidance describes major and older-minor release branches. Changesets now uses 0.x as its base branch.
Apply release branches to automation
.github/workflows/ci.yml, .github/workflows/codeql-analysis.yml, renovate.json, README.md
CI and CodeQL push triggers match *.x branches, and their pull request triggers accept any target branch. Renovate targets versioned .x branches, and README badges reference 0.x.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Possibly related PRs

  • druxt/module-template#82: Adds a release workflow triggered from main and *.x branches, which uses the release branch naming and behaviour described here.
Merge Risk: Minimal · up to 59e58

The branch-targeting changes present no concrete merge-blocking risk.

Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title says the change makes CI run on the 0.x release branch and on version branches after it. The raw summary and objectives show that ci.yml now runs on pushes to *.x branches and on pull reques…
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title says the change makes CI run on the 0.x release branch and on version branches after it. The raw summary and objectives show that ci.yml now runs on pushes to *.x branches and on pull requests regardless of base branch. The title covers the main CI change. It leaves out the wider branch migration, which touches CodeQL, Renovate, the Changesets baseBranch, the README badges, and CONTRIBUTING.md. That is expected for a short title, so the title is related to the main change.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (6 skipped: 6 unsupported.)

Finishing Touches
Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@Decipher
Decipher merged commit b45a116 into 0.x Oct 31, 2026
5 checks passed
@Decipher
Decipher deleted the feature/version-branches branch October 31, 2026 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant