ci: add Renovate and tag-driven releases #6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/renovate-and-release-automation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Changes
renovate.json+.gitea/workflows/renovate.yml: weekly pinned Renovate (44.165.1) covering NuGet, the SDK image, actions and the smoke-test images. Jellyfin packages and server stay on 10.11.x (together), the SDK on 9.0.x, no automerge.SHELLCHECK_VERSIONis deliberately unmanaged (its checksum cannot be recomputed).scripts/release.sh+.gitea/workflows/release.yml: on a bare-version tag, refuse mismatched or non-main tags, build the zip, create the release with assets, open the manifest PR.Verification
--strict) passes; an offline dry run extracts every intended dependency. Control run without the version rules proposes Jellyfin 12.2.0 and SDK 10.0.402; with the real config neither is proposed. An empty GitHub token variable does not break a run.release.shend to end against a throwaway local Gitea 1.22.6: created a public release with zip and SHA256SUMS, opened a mergeable manifest PR whose checksum equals the MD5 of the attached zip, and refused a second run. Rejects v-prefixed tags, version mismatch, missing tag, HEAD not on the tag, and a tag not on main.Not verified here
BOT_TOKENrepo secret (a dedicated account token); neither has run on this forge yet.