[PR #8277] [MERGED] Refactor CI workflow to use Bun instead of Node.js. #7363

Closed
opened 2026-02-26 15:34:50 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/8277
Author: @BramSuurdje
Created: 10/11/2025
Status: Merged
Merged: 10/11/2025
Merged by: @michelroegl-brunner

Base: mainHead: switch-to-bun


📝 Commits (1)

  • 40ca1f9 Refactor CI workflow to use Bun instead of Node.js for dependency management and build process; add bun.lock file and remove package-lock.json.

📊 Changes

3 files changed (+1966 additions, -14468 deletions)

View changed files

📝 .github/workflows/frontend-cicd.yml (+6 -8)
frontend/bun.lock (+1960 -0)
frontend/package-lock.json (+0 -14460)

📄 Description

✍️ Description

This pull request updates the frontend CI/CD workflow to use Bun instead of Node.js and npm. This change streamlines dependency management and build steps for the frontend, aligning with modern JavaScript tooling.

Frontend build pipeline modernization:

  • Replaced Node.js setup (actions/setup-node@v4) with Bun setup (oven-sh/setup-bun@v2) in .github/workflows/frontend-cicd.yml, specifying the latest Bun version.
  • Changed dependency installation from npm ci to bun install --frozen-lockfile for improved speed and reliability.
  • Updated the build command from npm run build to bun run build to leverage Bun's faster build execution.

Link: #

Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔄 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/community-scripts/ProxmoxVE/pull/8277 **Author:** [@BramSuurdje](https://github.com/BramSuurdje) **Created:** 10/11/2025 **Status:** ✅ Merged **Merged:** 10/11/2025 **Merged by:** [@michelroegl-brunner](https://github.com/michelroegl-brunner) **Base:** `main` ← **Head:** `switch-to-bun` --- ### 📝 Commits (1) - [`40ca1f9`](https://github.com/community-scripts/ProxmoxVE/commit/40ca1f95f2d674bf8c3ac828006e23b81cb789bf) Refactor CI workflow to use Bun instead of Node.js for dependency management and build process; add bun.lock file and remove package-lock.json. ### 📊 Changes **3 files changed** (+1966 additions, -14468 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/frontend-cicd.yml` (+6 -8) ➕ `frontend/bun.lock` (+1960 -0) ➖ `frontend/package-lock.json` (+0 -14460) </details> ### 📄 Description <!--🛑 New scripts must be submitted to [ProxmoxVED](https://github.com/community-scripts/ProxmoxVED) for testing. PRs without prior testing will be closed. --> ## ✍️ Description This pull request updates the frontend CI/CD workflow to use Bun instead of Node.js and npm. This change streamlines dependency management and build steps for the frontend, aligning with modern JavaScript tooling. **Frontend build pipeline modernization:** * Replaced Node.js setup (`actions/setup-node@v4`) with Bun setup (`oven-sh/setup-bun@v2`) in `.github/workflows/frontend-cicd.yml`, specifying the latest Bun version. * Changed dependency installation from `npm ci` to `bun install --frozen-lockfile` for improved speed and reliability. * Updated the build command from `npm run build` to `bun run build` to leverage Bun's faster build execution. ## 🔗 Related PR / Issue Link: # ## ✅ Prerequisites (**X** in brackets) - [x] **Self-review completed** – Code follows project standards. - [x] **Tested thoroughly** – Changes work as expected. - [x] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. --- ## 🛠️ Type of Change (**X** in brackets) - [ ] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [ ] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [ ] 🆕 **New script** – A fully functional and tested script or script set. - [ ] 🌍 **Website update** – Changes to website-related JSON files or metadata. - [x] 🔧 **Refactoring / Code Cleanup** – Improves readability or maintainability without changing functionality. - [ ] 📝 **Documentation update** – Changes to `README`, `AppName.md`, `CONTRIBUTING.md`, or other docs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 15:34:50 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#7363
No description provided.