Repository navigation
ci: automerge ruff updates and release automatically - #176
Merged
Merged
Conversation
This was referenced Oct 21, 2026
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.
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.jsonextends theautomerge-serverpreset instead of:semanticCommitTypeAll(fix):fix(deps): ...commit messages, from the preset. Other updates, such as GitHub Actions, now getchore(deps): ..., which doesn't make a release. With:semanticCommitTypeAll(fix), every Renovate PR would have been released.The
smoke / Smoke test resultcheck is made required through sublimelsp/infra.Release on push
Adds the lsp_release_workflow caller, which releases the package on push to
mainbased on the conventional commits since the latest tag:feat→ minor releasefix,perf,revert→ patch release, including thefix(deps)ruff updateschore,ci,docs,refactor,test, and commits that aren't conventional → no releaseReleases can still be made by hand: add an entry to
messages.json, run the workflow from the Actions tab withbumpset, 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 inserver/, and the smoke test.