chore(ci): adopt shared workflows and central Renovate preset - #198
Merged
Conversation
|
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. |
Contributor
Test results249 files 249 suites 1m 56s ⏱️ Results for commit 5a5d0af. ♻️ This comment has been updated with latest results. |
- renovate.json -> central preset (cygnus-maintainers) - security.yml (Trivy + CycloneDX SBOM)
- pr-lint.yml - commitlint.config.mjs - SBOM job appended to release-please.yml
…build.gradle.kts - renovate flavor restored: minestom - extra-files now points at build.gradle.kts
TheMeinerLP
force-pushed
the
chore/standardize-pipelines-and-renovate
branch
from
August 25, 2026 21:19
76979b3 to
5a5d0af
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
3 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.
What
Brings this repository onto the OneLiteFeather standard CI, release and dependency setup.
CI, security and dependencies
Release automation and PR hygiene
Version anchoring and Renovate presets
Why
One shared setup per concern instead of a hand-maintained copy per repository:
OneLiteFeatherNET/workflows) are pinned to a full SemVer tag, so a fixin the shared catalogue reaches this repository through a Renovate PR.
the maintainer team as reviewer, instead of a per-repository config that drifts.
scanning, plus a CycloneDX SBOM on every run. Report-only, so adopting it does not turn CI red on
day one.
the version and cuts the release. Simple mode deliberately does not rewrite language version
files, which keeps this change limited to release plumbing.
dependency inventory.
:minestom/:paper) is what teaches Renovate thedate-based Minestom scheme and Paper's
X.Y.Z-<mc-version>scheme; without it those two getparsed as plain SemVer and updated wrongly.
build.gradle.ktsbehind// x-release-please-version, so a releasechanges exactly one line in one file instead of a properties file the build has to parse.
release-please silently fails to bump the version or drops the commit from the changelog.
Everything a release needs is chained into the release-please workflow run on purpose: release-please
tags with
GITHUB_TOKEN, and a tag pushed that way does not start a separateon: push: tagsworkflow.