Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update helm release gitea to v10 #188

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 18, 2023

This PR contains the following updates:

Package Type Update Change
gitea HelmChart major 9.6.1 -> 10.6.0

Release Notes

gitea/helm-chart (gitea)

v10.6.0

Compare Source

Features
  • Add Gitea Actions act runner (#​666)
  • Support custom envs for Action DinD container (#​722)

v10.5.0

Compare Source

Features

  • Gitea 1.22.3 (#​718)
  • feat(serviceMonitor): custom configuration (#​710)
  • Add 'extraContainers' parameter (#​697)

Bug Fixes

  • Fix namespace templating inconsistencies (#​713)
  • Fix probe definition overrides (#​717)

Docs

  • Add comments about redis password policy (#​706)
  • Fix configuration in "external database" docs (#​716)

v10.4.1

Compare Source

Features

  • Gitea 1.22.2

Bug Fixes

  • Do not log errors in init-directories container during Gitea launch (#​708)
  • Fix persistence for postgresql-ha (#​704)

Dependencies

  • chore(deps): update subcharts (minor & patch) (#​695)
  • chore(deps): update subcharts (minor & patch) (#​693)
  • Improve Renovate behavior (#​689)

v10.4.0

Compare Source

Features

  • Gitea 1.22.1 (#​684)
  • feat: service.{http,ssh}.loadBalancerClass (#​640)

Dependencies

  • chore(deps): update subcharts (minor & patch) (#​688)
  • chore(deps): update alpine/helm docker tag to v3.15.3 (#​687)
  • chore(deps): update postgresql docker tag to v15.5.16 (#​683)

v10.3.0

Compare Source

With v10.2.0, Gitea was bumped to 1.22.0. This update introduced a bug where the admin password had to be reset every time the Pod was recreated. To mitigate this issue, we decided to implement a feature that allows customization of this behavior (#​677) and also restores the behavior prior to Gitea 1.22.0. Hence, the double classification of #​677.

Features

  • Add non-clustered redis as sub-chart (#​672)
  • Enable admin user password creation/update mode in values (#​677) (#​673)

Bug Fixes

  • Enable admin user password creation/update mode in values (#​677) (#​673)

Dependencies

  • chore(deps): update subcharts (minor & patch) (#​680)
  • chore(deps): update subcharts (minor & patch) (#​670)
  • chore(deps): update subcharts (minor & patch) (#​669)
  • chore(deps): update alpine/helm docker tag to v3.15.2 (#​668)
  • chore(deps): update subcharts (minor & patch) (#​667)
  • chore(deps): update subcharts (minor & patch) (#​665)

This tag has been re-tagged due to an expired gpg key for Helm signing. The original tagged commit is 1dbf171ad3566dc3cddd5aa74650708da0238d6e.

v10.2.0

Compare Source

  • Bump Gitea to 1.22.0
  • Add tpl support for PVC and ingress components (#​664)
  • Quote image tag (#​641)
  • Add deployment labels to deployment (#​649)

Subcharts

  • Update PG to 15.5.0
  • Update PG-HA to 14.1.3
  • Update redis-cluster to 10.2.0

v10.1.4

Compare Source

  • Bump Gitea to 1.21.11
  • chore(deps): update postgresql-ha docker tag to v14.0.3 (#​639)
  • chore(deps): update postgresql docker tag to v14 (#​622)
  • chore(deps): update redis-cluster docker tag to v9.7.0 (#​621)

v10.1.3

Compare Source

  • Bump Gitea to 1.21.7
  • chore(deps): update workflow dependencies (minor & patch) (#​616)
  • chore(deps): update redis-cluster docker tag to v9.6.2 (#​617)

v10.1.2

Compare Source

  • Bump to Gitea 1.21.6
  • Add tests for HA assertion and clean up (#​611)
  • chore(deps): update subcharts (minor & patch) (#​613)

v10.1.1

Compare Source

Bump Gitea to 1.21.5

v10.1.0

Compare Source

Features

  • Add labels to PVC manifest (#​581)
  • Allow using Custom Labels in SVC Templates (#​597)

Bug Fixes

Dependencies

  • chore(deps): update subcharts (minor & patch) (#​603)
  • Bump Gitea to 1.21.4

v10.0.2

Compare Source

Bump to Gitea 1.21.3

v10.0.1

Compare Source

Bug fixes

  • Properly sanitize gitea admin output (#​590): Fixes an issue for new installations which were failing during the creation of the internal admin user due to a change in Gitea 1.21.2

v10.0.0

Compare Source

Breaking

  • Update README with new dependency versioning approach (#​578): This allows the chart to move forward with the sub-chart dependencies as they get released without impacting users/forcing them to update. Please read the changelog and the linked section for the required actions.

Features

  • Add config fallbacks for session, cache and queue when disabling redis-cluster (#​585): this should help with config related problems when disabling the default redis-cluster sub-chart dependency

Dependencies

  • Bump Gitea to 1.21.2 (#​588)
  • chore(deps): update postgresql docker tag to v13 (#​579)
  • chore(deps): update postgresql-ha docker tag to v12.3.3 (#​587)

Misc

  • Properly distinguish predefined and custom env vars in environment-to-ini (#​586)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/gitea-10.x branch 2 times, most recently from cf7da2d to 3050b12 Compare December 23, 2023 15:58
@renovate renovate bot force-pushed the renovate/gitea-10.x branch from 3050b12 to a02862c Compare January 22, 2024 10:20
@renovate renovate bot force-pushed the renovate/gitea-10.x branch from a02862c to 838147d Compare February 1, 2024 14:17
@renovate renovate bot force-pushed the renovate/gitea-10.x branch 2 times, most recently from ac1da5c to c91fffa Compare February 26, 2024 13:27
@renovate renovate bot force-pushed the renovate/gitea-10.x branch from c91fffa to cf37384 Compare April 16, 2024 12:09
@renovate renovate bot force-pushed the renovate/gitea-10.x branch from cf37384 to 88b56f8 Compare June 6, 2024 21:42
@renovate renovate bot force-pushed the renovate/gitea-10.x branch from 88b56f8 to 74cfc35 Compare July 7, 2024 18:01
@renovate renovate bot force-pushed the renovate/gitea-10.x branch from 74cfc35 to 2d2ace1 Compare July 21, 2024 13:22
@renovate renovate bot force-pushed the renovate/gitea-10.x branch from 2d2ace1 to 62103c6 Compare September 11, 2024 13:53
@renovate renovate bot changed the title Update Helm release gitea to v10 chore(deps): update helm release gitea to v10 Sep 14, 2024
@renovate renovate bot force-pushed the renovate/gitea-10.x branch from 62103c6 to c193be1 Compare October 18, 2024 15:35
@renovate renovate bot force-pushed the renovate/gitea-10.x branch from c193be1 to 7b1b7e7 Compare November 10, 2024 16:13
@renovate renovate bot force-pushed the renovate/gitea-10.x branch from 7b1b7e7 to 741fbcd Compare November 12, 2024 09:51
@splattner
Copy link
Member

don't merge this, a lot has changed!

@splattner splattner closed this Nov 12, 2024
Copy link
Contributor Author

renovate bot commented Nov 12, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 10.x releases. But if you manually upgrade to 10.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/gitea-10.x branch November 12, 2024 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant