starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

Readeck latest version is wrong (upstream change) #884

New Issue
Closed
opened 2026-02-04 22:03:39 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-04 22:03:39 +03:00
Owner
Copy Link

Originally created by @neurolit on GitHub (May 1, 2025).

Originally assigned to: @tremor021 on GitHub.

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Readeck

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/readeck.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Hi,

Readeck script doesn't find the latest version, but an older one.

See b5dc4bdf59/ct/readeck.sh (L31C14-L31C121)

curl -fsSL https://codeberg.org/readeck/readeck/releases/ | grep -oP '(?<=Version )\d+\.\d+\.\d+' | head -1 returns 0.17.1, but should return 0.18.1 (as of today), because on readeck releases page, the version number isn't prefixed by "Version " anymore.

🔄 Steps to reproduce the issue.

  • Step 1: run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/readeck.sh)" in order to update Readeck.
  • Step 2: go to https://YOUR_READECK_URL/docs/about
  • Step 3: see version 0.17.1 instead of 0.18.1

Or

  • Step 1: run curl -fsSL https://codeberg.org/readeck/readeck/releases/ | grep -oP '(?<=Version )\d+\.\d+\.\d+' | head -1
  • Step 2: see 0.17.1 instead of 0.18.1

❌ Paste the full error output (if available).

No error output, only the wrong version

🖼️ Additional context (optional).

No response

Originally created by @neurolit on GitHub (May 1, 2025). Originally assigned to: @tremor021 on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Readeck ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/readeck.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Hi, Readeck script doesn't find the latest version, but an older one. See https://github.com/community-scripts/ProxmoxVE/blob/b5dc4bdf59a5448c190b8f65b8689a8ecabe1a6c/ct/readeck.sh#L31C14-L31C121 `curl -fsSL https://codeberg.org/readeck/readeck/releases/ | grep -oP '(?<=Version )\d+\.\d+\.\d+' | head -1` returns 0.17.1, but should return 0.18.1 (as of today), because on [readeck releases page](https://codeberg.org/readeck/readeck/releases), the version number isn't prefixed by "Version " anymore. ### 🔄 Steps to reproduce the issue. - Step 1: run `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/readeck.sh)"` in order to update Readeck. - Step 2: go to https://YOUR_READECK_URL/docs/about - Step 3: see version 0.17.1 instead of 0.18.1 Or - Step 1: run `curl -fsSL https://codeberg.org/readeck/readeck/releases/ | grep -oP '(?<=Version )\d+\.\d+\.\d+' | head -1` - Step 2: see 0.17.1 instead of 0.18.1 ### ❌ Paste the full error output (if available). No error output, only the wrong version ### 🖼️ Additional context (optional). _No response_
OVERLORD added the investigation label 2026-02-04 22:03:39 +03:00
OVERLORD commented 2026-02-04 22:03:47 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (May 1, 2025):

The grep is failing because they changed release version naming. They removed "Version" from version number. Its just numbering now. @MickLesk

@tremor021 commented on GitHub (May 1, 2025): The grep is failing because they changed release version naming. They removed "Version" from version number. Its just numbering now. @MickLesk
OVERLORD commented 2026-02-04 22:03:50 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (May 1, 2025):

Yeah, its an task not an bug, the script itself still works, but not with the current upstream. Therefore, action is not required immediately => task

@MickLesk commented on GitHub (May 1, 2025): Yeah, its an task not an bug, the script itself still works, but not with the current upstream. Therefore, action is not required immediately => task
OVERLORD commented 2026-02-04 22:03:52 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (May 1, 2025):

curl -fsSL https://codeberg.org/readeck/readeck/releases/ | grep -oP '/releases/tag/\K\d+\.\d+\.\d+' | head -1

@tremor021 commented on GitHub (May 1, 2025): `curl -fsSL https://codeberg.org/readeck/readeck/releases/ | grep -oP '/releases/tag/\K\d+\.\d+\.\d+' | head -1`
OVERLORD commented 2026-02-04 22:03:56 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (May 1, 2025):

@neurolit should be fixed after #4172 merges

@tremor021 commented on GitHub (May 1, 2025): @neurolit should be fixed after #4172 merges
OVERLORD commented 2026-02-04 22:04:03 +03:00
Author
Owner
Copy Link

@neurolit commented on GitHub (May 2, 2025):

Thank you very much!

@neurolit commented on GitHub (May 2, 2025): Thank you very much!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label investigation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#884
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?