Skip to content

ci: automerge ruff updates and release automatically - #176

Merged
rchl merged 1 commit into
mainfrom
automerge-and-release
Oct 21, 2026
Merged

rchl merged 1 commit into
mainfrom
automerge-and-release

Conversation

@rchl

@rchl rchl commented Oct 21, 2026

Copy link
Copy Markdown
Member

Like sublimelsp/LSP-oxlint#10: lets ruff updates go from Renovate PR to release without manual steps. Merge #175 first: the preset only recognises ruff updates once ruff is pinned in server/.

Automerge ruff updates

renovate.json extends the automerge-server preset instead of :semanticCommitTypeAll(fix):

  • Renovate waits 3 days after a ruff release before opening the PR, so a broken release that gets a quick fix is skipped.
  • ruff updates still get fix(deps): ... commit messages, from the preset. Other updates, such as GitHub Actions, now get chore(deps): ..., which doesn't make a release. With :semanticCommitTypeAll(fix), every Renovate PR would have been released.
  • Patch updates are merged once the smoke test passes. ruff is still 0.x, and the preset doesn't automerge minor updates of 0.x servers (0.17 → 0.18), so those still need a manual merge.

The smoke / Smoke test result check is made required through sublimelsp/infra.

Release on push

Adds the lsp_release_workflow caller, which releases the package on push to main based on the conventional commits since the latest tag:

  • feat → minor release
  • fix, perf, revert → patch release, including the fix(deps) ruff updates
  • chore, ci, docs, refactor, test, and commits that aren't conventional → no release

Releases can still be made by hand: add an entry to messages.json, run the workflow from the Actions tab with bump set, or put [skip release] in a commit message.

If #175 is merged first, merging this releases 3.2.15, since #175 is a fix: commit since 3.2.14. That release ships #174, the server in server/, and the smoke test.

@rchl
rchl merged commit 55a15e5 into main Oct 21, 2026
4 checks passed
@rchl
rchl deleted the automerge-and-release branch October 21, 2026 06:35
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