jklein
cbddba6972
Validate Helm Charts / Detect changed charts (pull_request) Successful in 4s
Validate Helm Charts / Resource quantities (pull_request) Successful in 8s
Validate Helm Charts / Build ${{ fromJSON(needs.detect-changed-charts.outputs.charts) }} (pull_request) Successful in 32s
Validate Helm Charts / Trivy config ${{ fromJSON(needs.detect-changed-charts.outputs.scan-charts) }} (pull_request) Successful in 1m24s
Validate Helm Charts / Install-test ${{ fromJSON(needs.detect-changed-charts.outputs.install-charts) }} (pull_request) Failing after 16m52s
The doc comments on the resources and defaultedDict helpers justified the copy-per-chart with "charts in this repo deliberately have no dependencies". That rule fell with #214: a dependency is admissible now, just expensive, and it sits in the README as guideline 14, not 13. The justification still holds, but its reason is a different one - sharing the helper would mean a library chart, a second artefact to publish, version and pull for something that changes about once a year. searxng got that wording in PR #38; this carries it to the remaining 22 charts, 41 occurrences in all. Comments only: every touched chart renders byte-identical against its ci/<chart>/test-values.yaml. Each published chart takes a patch bump, appVersion and +up suffix untouched; template-chart is never published and takes none, but is corrected because every new chart inherits from it. Two repo files carried the same claim at no version cost: validate-charts.yml explained the all-charts quantity render test with it, and change-app-version.yml still counted nine images for freesailarr - MediathekArr made it ten.
31 lines
1.5 KiB
YAML
31 lines
1.5 KiB
YAML
apiVersion: v2
|
|
name: minecraft-server
|
|
description: A Helm chart for deploying a itzg/minecraft-server
|
|
icon: https://avatars.githubusercontent.com/u/988985
|
|
|
|
type: application
|
|
|
|
# ONLY THE NEWEST JAVA LINE IS MAINTAINED (chart 5.0.0, issue #158).
|
|
# appVersion is the image tag and therefore fixes the JVM. Up to chart 4.1.0 the
|
|
# chart was published once per line (java8 / java17 / java21 / java25) out of
|
|
# this single directory, which is what made the lines drift apart: whatever
|
|
# change landed while a line happened to lie in the directory reached that line
|
|
# only. That is over. This directory carries exactly one line - the newest -
|
|
# and it is the only one that gets chart changes.
|
|
# The older lines stay published as frozen artifacts and are still installable:
|
|
# java8 and java17 at 4.0.0, java21 at 4.1.0. They will not be updated again.
|
|
# To run an older JVM with the CURRENT chart, set image.tagOverride in values
|
|
# instead of installing a frozen chart version; the chart then checks that
|
|
# minecraft.version fits the line of that tag and fails the render if it does
|
|
# not.
|
|
# Since chart 2.0.0 the tag is a DATED upstream release ("<release>-java<N>")
|
|
# instead of the rolling line tag ("java<N>"): the rolling tags are rebuilt
|
|
# continuously, so a pod restart could pull a different image than the last one
|
|
# without anything being recorded anywhere. The dated tags are immutable, so the
|
|
# image is now pinned by the chart version like every other chart in this repo.
|
|
version: 6.0.1+up2026.8.2.java25
|
|
appVersion: "2026.8.2-java25"
|
|
|
|
maintainers:
|
|
- name: jklein
|