[PR #413] [MERGED] Add versioning, only update boot files for rolling #847

New issue

Closed

opened 2026-02-27 14:53:28 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 14:53:28 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/netbootxyz/netboot.xyz/pull/413
Author: @thelamer
Created: 12/12/2019
Status: ✅ Merged
Merged: 12/12/2019
Merged by: @antonym

Base: development ← Head: versioning

📝 Commits (1)

78eac80 only run the update logic on the rolling .x series, tag the versioned builds to display in menu

📊 Changes

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

View changed files

📝 roles/netbootxyz/defaults/main.yml (+1 -1)
📝 roles/netbootxyz/templates/menu/menu.ipxe.j2 (+4 -2)
📝 script/build_release (+16 -5)
📝 user_overrides.yml (+1 -1)

📄 Description

So the basics of this is if the user is using a specific versioned boot medium ( self hosted users and people specifically looking for versioned endpoint ) we do not include the upgrade logic it is redundant as they are already pointed to a static endpoint but there is also no need for it. They will see this specific version in their menu when booting.

If the user downloads the standard rolling release looking at the latest endpoints they will be pinged for an upgrade if we do a major version change ( 2.x to 3.x ) signifying we have made a significant change to the boot medium files and need it's functionality for the new menu files.

Let me know if you have any questions.

_{🔄 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/netbootxyz/netboot.xyz/pull/413 **Author:** [@thelamer](https://github.com/thelamer) **Created:** 12/12/2019 **Status:** ✅ Merged **Merged:** 12/12/2019 **Merged by:** [@antonym](https://github.com/antonym) **Base:** `development` ← **Head:** `versioning` --- ### 📝 Commits (1) - [`78eac80`](https://github.com/netbootxyz/netboot.xyz/commit/78eac8044835603169f93e1d6a81d709212e95ed) only run the update logic on the rolling .x series, tag the versioned builds to display in menu ### 📊 Changes **4 files changed** (+22 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `roles/netbootxyz/defaults/main.yml` (+1 -1) 📝 `roles/netbootxyz/templates/menu/menu.ipxe.j2` (+4 -2) 📝 `script/build_release` (+16 -5) 📝 `user_overrides.yml` (+1 -1) </details> ### 📄 Description So the basics of this is if the user is using a specific versioned boot medium ( self hosted users and people specifically looking for versioned endpoint ) we do not include the upgrade logic it is redundant as they are already pointed to a static endpoint but there is also no need for it. They will see this specific version in their menu when booting. If the user downloads the standard rolling release looking at the latest endpoints they will be pinged for an upgrade if we do a major version change ( 2.x to 3.x ) signifying we have made a significant change to the boot medium files and need it's functionality for the new menu files. Let me know if you have any questions. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>