[PR #2562] [MERGED] feat: add git hash of build everywhere #21029

New Issue

GiteaMirror · 2026-04-20T03:18:34-05:00

GiteaMirror commented

2026-04-20 03:18:34 -05:00

📋 Pull Request Information

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

Base: dev ← Head: feat/include-git-hash-everywhere

📝 Commits (3)

a579f5f feat: add git hash of build everywhere
4fdb26f refac: rename build hash vars
aba6308 Merge remote-tracking branch 'upstream/dev' into feat/include-git-hash-everywhere

📊 Changes

9 files changed (+27 additions, -9 deletions)

View changed files

📝 .github/workflows/docker-build.yaml (+8 -2)
📝 Dockerfile (+6 -0)
📝 backend/apps/webui/main.py (+1 -1)
📝 backend/config.py (+2 -2)
📝 backend/main.py (+3 -1)
📝 hatch_build.py (+2 -0)
📝 src/lib/components/chat/Settings/About.svelte (+2 -2)
📝 src/lib/constants.ts (+1 -0)
📝 vite.config.ts (+2 -1)

📄 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

Add the git hash of the build into the output of backend and the frontend in the about page to help disambiguate builds when multiple releases of the same tag are produced.

Screenshots or Videos

_{🔄 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/2562 **Author:** [@cheahjs](https://github.com/cheahjs) **Created:** 5/25/2024 **Status:** ✅ Merged **Merged:** 5/26/2024 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `feat/include-git-hash-everywhere` --- ### 📝 Commits (3) - [`a579f5f`](https://github.com/open-webui/open-webui/commit/a579f5f8cfb5d0f3794c0c0b05d4237b41fb3088) feat: add git hash of build everywhere - [`4fdb26f`](https://github.com/open-webui/open-webui/commit/4fdb26fdc4e9360f28cdba9d44b4b8deaab79e1c) refac: rename build hash vars - [`aba6308`](https://github.com/open-webui/open-webui/commit/aba6308825a351dc1e7657f3e800b901196b8ad9) Merge remote-tracking branch 'upstream/dev' into feat/include-git-hash-everywhere ### 📊 Changes **9 files changed** (+27 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/docker-build.yaml` (+8 -2) 📝 `Dockerfile` (+6 -0) 📝 `backend/apps/webui/main.py` (+1 -1) 📝 `backend/config.py` (+2 -2) 📝 `backend/main.py` (+3 -1) 📝 `hatch_build.py` (+2 -0) 📝 `src/lib/components/chat/Settings/About.svelte` (+2 -2) 📝 `src/lib/constants.ts` (+1 -0) 📝 `vite.config.ts` (+2 -1) </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? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [x] **Testing:** Have you written and run sufficient tests for validating the changes? - [x] **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 Add the git hash of the build into the output of backend and the frontend in the about page to help disambiguate builds when multiple releases of the same tag are produced. --- ### Screenshots or Videos <img width="745" alt="image" src="https://github.com/open-webui/open-webui/assets/818368/af6b10f2-3ffa-42b1-aa4d-2a1833126d6c"> <img width="643" alt="image" src="https://github.com/open-webui/open-webui/assets/818368/864f7fd1-b531-4f8b-b18c-bf4ec7653491"> --- <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 2026-04-20 03:18:34 -05:00

GiteaMirror closed this issue

2026-04-20 03:18:35 -05:00

GiteaMirror referenced this issue

2026-04-20 06:11:23 -05:00

[PR #21029] [CLOSED] chore(tests): add Playwright API tests + CI #25896

GiteaMirror referenced this issue

2026-04-25 09:04:28 -05:00

[GH-ISSUE #21030] CI: Please run Playwright API tests for PR #21029 (fork) #34889

GiteaMirror referenced this issue

2026-04-25 09:17:55 -05:00

[GH-ISSUE #21783] feat: Backend has no test coverage in CI — pytest is commented out and integration tests are disabled #35098