lunny/helm-chart
1
0
Fork 1
Code Issues 36 Pull Requests 14 Actions Packages Projects Releases 93 Wiki Activity

Update app version to 1.17.0 #340

New Issue
Closed
opened 2022-08-01 20:24:11 +00:00 by northcode · 5 comments
northcode commented 2022-08-01 20:24:11 +00:00 (Migrated from gitea.com)
Copy Link

Gitea 1.17.0 just released on docker hub.
Chart should update, to match latest version.

Gitea 1.17.0 just released on docker hub. Chart should update, to match latest version.
👍 3
TheAnachronism commented 2022-08-12 13:48:13 +00:00 (Migrated from gitea.com)
Copy Link

Is there any news on this?
Why is it taking so long to update to the new version?

Is there any news on this? Why is it taking so long to update to the new version?
petergardfjall commented 2022-08-15 11:02:25 +00:00 (Migrated from gitea.com)
Copy Link

As explained here it should be possible to just bump the version to v1.17.0 in the values.yaml file.

As explained [here](https://discord.com/channels/322538954119184384/730458347928813581/1004570012796854272) it should be possible to just bump the version to `v1.17.0` in the `values.yaml` file.
👍 1
justusbunsi commented 2022-08-15 11:24:41 +00:00 (Migrated from gitea.com)
Copy Link

We are currently working on #107 and #255 before bumping the Helm Chart image officially. Both features are related to breaking changes introduced in 1.17 regarding git config location and GPG signing functionality. Our goal is to eliminate these two breaking changes for the Helm Chart users.

As mentioned by @petergardfjall and discussed on Discord, switching to 1.17 via values.yaml is possible individually without bumping the version for everyone.

We are currently working on #107 and #255 before bumping the Helm Chart image officially. Both features are related to breaking changes introduced in 1.17 regarding git config location and GPG signing functionality. Our goal is to eliminate these two breaking changes for the Helm Chart users. As mentioned by @petergardfjall and discussed on Discord, switching to `1.17` via `values.yaml` is possible individually without bumping the version for everyone.
👍 1
justusbunsi commented 2022-08-21 12:47:38 +00:00 (Migrated from gitea.com)
Copy Link

I've added milestone 3176 to track progress for version bump.

I've added milestone [3176](https://gitea.com/gitea/helm-chart/milestone/3176) to track progress for version bump.
👍 1
justusbunsi commented 2022-08-22 15:39:44 +00:00 (Migrated from gitea.com)
Copy Link

@luhahn and I discussed the current situation and decided to release a new Helm Chart version bumping the Gitea version without these two features.

@luhahn and I discussed the current situation and decided to release a new Helm Chart version bumping the Gitea version without these two features.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
has/backport
in progress
invalid
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
need/backport
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/other
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lunny/helm-chart#340
No description provided.
Delete Branch "%!s()"

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?