Compare commits

..

No commits in common. "main" and "v6.1.0" have entirely different histories.
main ... v6.1.0

8 changed files with 13 additions and 31 deletions

View file

@ -5,7 +5,7 @@ on:
push:
branches:
- main
- maint/**
- release/**
tags:
- v*
@ -83,7 +83,6 @@ jobs:
- v1.27.13 # renovate: kindest
- v1.28.9 # renovate: kindest
- v1.29.4 # renovate: kindest
- v1.30.0 # renovate: kindest
steps:
- run: cat /etc/os-release

View file

@ -1 +1 @@
20.14.0
20.13.1

View file

@ -1,12 +1,12 @@
dependencies:
- name: postgresql
repository: oci://registry-1.docker.io/bitnamicharts
version: 15.5.0
version: 15.4.1
- name: postgresql-ha
repository: oci://registry-1.docker.io/bitnamicharts
version: 14.1.3
version: 14.1.2
- name: redis-cluster
repository: oci://registry-1.docker.io/bitnamicharts
version: 10.2.0
digest: sha256:f7feb678e253951354014684cca973ce7656aa8fd812e627534257dad7765069
generated: "2024-05-29T18:01:33.490509906Z"
digest: sha256:c5f726f10dc8b6cb106248e936edb3e44babf9cd4b809b327cbcbe93871c6f63
generated: "2024-05-27T08:31:19.427853618Z"

View file

@ -2,7 +2,7 @@ apiVersion: v2
name: forgejo
description: Forgejo Helm chart for Kubernetes
type: application
version: 0.1.0
version: 0.0.0
appVersion: 7.0.3
icon: https://code.forgejo.org/forgejo/forgejo/raw/branch/forgejo/assets/logo.svg
home: https://forgejo.org/
@ -29,12 +29,12 @@ dependencies:
# https://github.com/bitnami/charts/blob/main/bitnami/postgresql/Chart.yaml
- name: postgresql
repository: oci://registry-1.docker.io/bitnamicharts
version: 15.5.0
version: 15.4.1
condition: postgresql.enabled
# https://github.com/bitnami/charts/blob/main/bitnami/postgresql-ha/Chart.yaml
- name: postgresql-ha
repository: oci://registry-1.docker.io/bitnamicharts
version: 14.1.3
version: 14.1.2
condition: postgresql-ha.enabled
# https://github.com/bitnami/charts/blob/main/bitnami/redis-cluster/Chart.yaml
- name: redis-cluster

View file

@ -68,7 +68,7 @@ Additionally, this chart allows to provide LDAP and admin user configuration wit
## Update and versioning policy
The Forgejo helm chart versioning does not follow Forgejo's versioning.
The latest chart version can be looked up in <https://codeberg.org/forgejo-contrib/-/packages/container/forgejo> or in the [repository releases](https://codeberg.org/forgejo-contrib/forgejo-helm/releases).
The latest chart version can be looked up in <https://codeberg.org/forgejo-contrib/-/packages/container/forgejo/0.8.0> or in the [repository releases](https://codeberg.org/forgejo-contrib/forgejo-helm/releases).
The chart aims to follow Forgejo's releases closely.
There might be times when the chart is behind the latest Forgejo release.
@ -1161,8 +1161,3 @@ Hop into [our Matrix room](https://matrix.to/#/#forgejo-helm-chart:matrix.org) i
This section lists major and breaking changes of each Helm Chart version.
Please read them carefully to upgrade successfully, especially the change of the **default database backend**!
If you miss this, blindly upgrading may delete your Postgres instance and you may lose your data!
### To v6.0.0
You need Forgejo v7+ to use this Helm Chart version.
Use the v5 Helm Chart for Forgejo v1.21.

Binary file not shown.

View file

@ -9,15 +9,7 @@
"custom.regex",
"github-actions"
],
"baseBranches": ["main", "/^maint\\/.+/"],
"packageRules": [
{
"description": "Disable major chart updates for maintenance branches",
"matchBaseBranches": ["/^maint\\/.+/"],
"matchUpdateTypes": ["major"],
"matchFileNames": ["Chart.yaml"],
"enabled": false
},
{
"matchManagers": ["helmv3"],
"matchUpdateTypes": ["minor", "patch"],
@ -94,11 +86,6 @@
"description": "Update only daily for forgejo ci tests",
"matchFileNames": ["ci/*.yml"],
"extends": ["schedule:daily"]
},
{
"description": "branch automerge not possible",
"matchPackagePatterns": [".+"],
"automergeType": "pr"
}
],
"customManagers": [

View file

@ -1,6 +1,6 @@
suite: Init template (rootless)
suite: Init template
release:
name: forgejo-unittests
name: gitea-unittests
namespace: testing
templates:
- templates/gitea/init.yaml
@ -67,6 +67,7 @@ tests:
chown 1000:1000 "${GNUPGHOME}"
fi
- it: it does not chown /data even when image.fullOverride is set
template: templates/gitea/init.yaml
set:
image.fullOverride: gitea/gitea:1.20.5
asserts: