open-webui/helm-charts
1
0
Fork 0
mirror of https://github.com/open-webui/helm-charts.git synced 2026-07-22 18:05:24 -04:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

[PR #15] [MERGED] fixing chart-releaser workflow #125

New Issue
Closed
opened 2026-02-15 19:16:31 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 19:16:31 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/open-webui/helm-charts/pull/15
Author: @robrakaric
Created: 5/9/2024
Status: ✅ Merged
Merged: 5/9/2024
Merged by: @tjbck

Base: main ← Head: main

📝 Commits (2)

  • 5fd1892 did a helm dependency update to fix chart-releaser workflow
  • dad9b4d increment to 2.0.1 so chart will release

📊 Changes

4 files changed (+4 additions, -4 deletions)

View changed files

📝 charts/open-webui/Chart.lock (+3 -3)
📝 charts/open-webui/Chart.yaml (+1 -1)
➖ charts/open-webui/charts/ollama-0.24.1.tgz (+0 -0)
➕ charts/open-webui/charts/ollama-0.25.0.tgz (+0 -0)

📄 Description

The merge of 2.0.0 in #11 did not run chart-releaser correctly due to an out-of-date Chart.lock file in the repo. I've addressed this in this PR, updating the helm ollama dependency, and incrementing version to 2.0.1 to trigger the chart build.

Error: the lock file (Chart.lock) is out of sync with the dependencies file (Chart.yaml). Please update the dependencies

I enabled gh-pages and Actions on my forked repo to make sure chart-releaser works: https://github.com/robrakaric/open-webui-helm-charts/releases/tag/open-webui-2.0.1

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/helm-charts/pull/15 **Author:** [@robrakaric](https://github.com/robrakaric) **Created:** 5/9/2024 **Status:** ✅ Merged **Merged:** 5/9/2024 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (2) - [`5fd1892`](https://github.com/open-webui/helm-charts/commit/5fd1892357460c614cd814a466ef6611f810396f) did a helm dependency update to fix chart-releaser workflow - [`dad9b4d`](https://github.com/open-webui/helm-charts/commit/dad9b4d4ab286847982b9044fd78e0d202e2e65e) increment to 2.0.1 so chart will release ### 📊 Changes **4 files changed** (+4 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `charts/open-webui/Chart.lock` (+3 -3) 📝 `charts/open-webui/Chart.yaml` (+1 -1) ➖ `charts/open-webui/charts/ollama-0.24.1.tgz` (+0 -0) ➕ `charts/open-webui/charts/ollama-0.25.0.tgz` (+0 -0) </details> ### 📄 Description The merge of 2.0.0 in #11 [did not run chart-releaser correctly due to an out-of-date `Chart.lock` file in the repo](https://github.com/open-webui/helm-charts/actions/runs/9014588304/job/24767546082). I've addressed this in this PR, updating the helm ollama dependency, and incrementing version to 2.0.1 to trigger the chart build. ```shell Error: the lock file (Chart.lock) is out of sync with the dependencies file (Chart.yaml). Please update the dependencies ``` I enabled gh-pages and Actions on my forked repo to make sure chart-releaser works: https://github.com/robrakaric/open-webui-helm-charts/releases/tag/open-webui-2.0.1 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 19:16:31 -05:00
yindo closed this issue 2026-02-15 19:16:31 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
awaiting-user-feedback
awaiting-user-feedback
bug
bug
documentation
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
upstream
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: open-webui/helm-charts#125
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?