github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-22 06:02:06 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

[PR #2487] [MERGED] chore: upgrade github actions and python dependencies #7811

New Issue
Closed
opened 2025-11-11 17:36:38 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 17:36:38 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/2487
Author: @cheahjs
Created: 5/22/2024
Status: ✅ Merged
Merged: 5/22/2024
Merged by: @tjbck

Base: dev ← Head: chore/upgrade-deps

📝 Commits (2)

  • dcae813 chore: update github actions
  • 1aebf88 chore: update python dependencies

📊 Changes

8 files changed (+127 additions, -105 deletions)

View changed files

📝 .github/workflows/build-release.yml (+3 -3)
📝 .github/workflows/format-backend.yaml (+1 -1)
📝 .github/workflows/format-build-frontend.yaml (+1 -1)
📝 .github/workflows/integration-test.yml (+1 -1)
📝 backend/requirements.txt (+19 -19)
📝 pyproject.toml (+18 -18)
📝 requirements-dev.lock (+42 -31)
📝 requirements.lock (+42 -31)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

  • Target branch: Please verify that the pull request targets the dev branch.
  • Description: Provide a concise description of the changes made in this pull request.
  • Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
  • Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
  • Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
  • Testing: Have you written and run sufficient tests for validating the changes?
  • Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
  • Label: To cleary categorize this pull request, assign a relevant label to the pull request title, using one of the following:
    • BREAKING CHANGE: Significant changes that may affect compatibility
    • build: Changes that affect the build system or external dependencies
    • ci: Changes to our continuous integration processes or workflows
    • chore: Refactor, cleanup, or other non-functional code changes
    • docs: Documentation update or addition
    • feat: Introduces a new feature or enhancement to the codebase
    • fix: Bug fix or error correction
    • i18n: Internationalization or localization changes
    • perf: Performance improvement
    • refactor: Code restructuring for better maintainability, readability, or scalability
    • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
    • test: Adding missing tests or correcting existing tests
    • WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

Update GitHub Actions to stop the workflows from complaining about legacy Node versions.

Update Python deps. Was primarily updating litellm to pull in fixes, but went ahead and updated everything else that wasn't conflicting.

🔄 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/open-webui/pull/2487 **Author:** [@cheahjs](https://github.com/cheahjs) **Created:** 5/22/2024 **Status:** ✅ Merged **Merged:** 5/22/2024 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `chore/upgrade-deps` --- ### 📝 Commits (2) - [`dcae813`](https://github.com/open-webui/open-webui/commit/dcae813d05dec3d96a565ad1793728cbbb730e4e) chore: update github actions - [`1aebf88`](https://github.com/open-webui/open-webui/commit/1aebf880696b87a7178ca66ce05c9fe0e3a4928d) chore: update python dependencies ### 📊 Changes **8 files changed** (+127 additions, -105 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/build-release.yml` (+3 -3) 📝 `.github/workflows/format-backend.yaml` (+1 -1) 📝 `.github/workflows/format-build-frontend.yaml` (+1 -1) 📝 `.github/workflows/integration-test.yml` (+1 -1) 📝 `backend/requirements.txt` (+19 -19) 📝 `pyproject.toml` (+18 -18) 📝 `requirements-dev.lock` (+42 -31) 📝 `requirements.lock` (+42 -31) </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Please verify that the pull request targets the `dev` branch. - [x] **Description:** Provide a concise description of the changes made in this pull request. - [ ] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [x] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Have you written and run sufficient tests for validating the changes? - [ ] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Label:** To cleary categorize this pull request, assign a relevant label to the pull request title, using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description Update GitHub Actions to stop the workflows from complaining about legacy Node versions. Update Python deps. Was primarily updating litellm to pull in fixes, but went ahead and updated everything else that wasn't conflicting. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-11 17:36:38 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#7811
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?