Update still pulls old version #4456

New issue

Closed

opened 2026-02-28 04:03:19 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 04:03:19 -05:00

Owner

Originally created by @techny210 on GitHub (Nov 18, 2025).

Not found

🛡️ Security Policy

I have read and agree to Uptime Kuma's Security Policy.

📝 Description

Update pulling old version of distro

👟 Reproduction steps

git branch

(HEAD detached at 2.0.2)

npm install --omit dev --no-audit
up to date in 3s

npm run download-dist

uptime-kuma@2.0.1 download-dist

👀 Expected behavior

git branch

(HEAD detached at 2.0.2)

npm install --omit dev --no-audit
up to date in 3s

npm run download-dist

uptime-kuma@2.0.2 download-dist

😓 Actual Behavior

git branch

(HEAD detached at 2.0.2)

npm install --omit dev --no-audit
up to date in 3s

npm run download-dist

uptime-kuma@2.0.1 download-dist <----- ??? we are on 2.0.2 branch pulling 2.0.1 distro

🐻 Uptime-Kuma Version

2.0.2

💻 Operating System and Arch

Ubuntu 24.04

🌐 Browser

Brave

🖥️ Deployment Environment

Runtime Environment:
- Docker: Version X.X.X (Build Y.Y.Y)
- Docker Compose: Version X.X.X
- Portainer (BE/CE): Version X.X.X (LTS: Yes/No)
- MariaDB: Version X.X.X (LTS: Yes/No)
- Node.js: Version X.X.X (LTS: Yes/No)
- Kubernetes (K3S/K8S): Version X.X.X (LTS: Yes/No, via [method/tool])
Database:
- SQLite: Embedded
- MariaDB: Embedded/External
Database Storage:
- Filesystem:
  - Linux: ext4/XFS/Btrfs/ZFS/F2FS
  - macOS: APFS/ HFS+
  - Windows: NTFS/ReFS
- Storage Medium: HDD/eMMC/SSD/NVMe
Uptime Kuma Setup:
- Number of monitors: X

📝 Relevant log output

Originally created by @techny210 on GitHub (Nov 18, 2025). ### 📑 I have found these related issues/pull requests Not found ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Description Update pulling old version of distro ### 👟 Reproduction steps git branch * (HEAD detached at 2.0.2) npm install --omit dev --no-audit up to date in 3s npm run download-dist > uptime-kuma@2.0.1 download-dist ### 👀 Expected behavior git branch * (HEAD detached at 2.0.2) npm install --omit dev --no-audit up to date in 3s npm run download-dist > uptime-kuma@2.0.2 download-dist ### 😓 Actual Behavior git branch * (HEAD detached at 2.0.2) npm install --omit dev --no-audit up to date in 3s npm run download-dist > uptime-kuma@2.0.1 download-dist <----- ??? we are on 2.0.2 branch pulling 2.0.1 distro ### 🐻 Uptime-Kuma Version 2.0.2 ### 💻 Operating System and Arch Ubuntu 24.04 ### 🌐 Browser Brave ### 🖥️ Deployment Environment - **Runtime Environment**: - Docker: Version `X.X.X` (Build `Y.Y.Y`) - Docker Compose: Version `X.X.X` - Portainer (BE/CE): Version `X.X.X` (LTS: Yes/No) - MariaDB: Version `X.X.X` (LTS: Yes/No) - Node.js: Version `X.X.X` (LTS: Yes/No) - Kubernetes (K3S/K8S): Version `X.X.X` (LTS: Yes/No, via `[method/tool]`) - **Database**: - SQLite: Embedded - MariaDB: Embedded/External - **Database Storage**: - **Filesystem**: - Linux: ext4/XFS/Btrfs/ZFS/F2FS - macOS: APFS/ HFS+ - Windows: NTFS/ReFS - **Storage Medium**: HDD/eMMC/SSD/NVMe - **Uptime Kuma Setup**: - Number of monitors: `X` ### 📝 Relevant log output ```bash session ```