SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

TriliumNext was renamed Trilium and its repository moved #1413

New Issue
Closed
opened 2025-11-20 05:09:49 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:09:49 -05:00
Owner
Copy Link

Originally created by @jshprentz on GitHub (Jul 2, 2025).

✅ Have you read and understood the above guidelines?

yes

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

TriliumNext

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

update

⚙️ 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.

The TriliumNext LXC script does not upgrade from version 0.95.0 to 0.96.0.

This is caused by the TriliumNext project migrating to a different GitHub repository and renaming the application.

The TriliumNext LXC script should be updated to accommodate the new repository and application name.

🔄 Steps to reproduce the issue.

Step 1: update

❌ Paste the full error output (if available).

  ______     _ ___               
 /_  __/____(_) (_)_  ______ ___ 
  / / / ___/ / / / / / / __ `__ \
 / / / /  / / / / /_/ / / / / / /
/_/ /_/  /_/_/_/\__,_/_/ /_/ /_/ 
                                 

  ✔️   No update required. Trilium is already at 0.95.0

🖼️ Additional context (optional).

According to TriliumNext discussion 5867, Trilium's original developer, @zadam, agreed that the TriliumNext project is mature enough to regain the original name, Trilium. He transferred control of the original repository.

Last week, TriliumNext discussion 5845 announced that "Zadam's trilium repository is now under the TriliumNext organisation's umbrella."

Yesterday's Trilium Release v0.96.0 is the first from the TriliumNext/Trilium repository. Previous releases came from the TriliumNext/Notes repository, which now is archived.

Originally created by @jshprentz on GitHub (Jul 2, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? TriliumNext ### 📂 What was the exact command used to execute the script? update ### ⚙️ 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. The TriliumNext LXC script does not upgrade from version 0.95.0 to 0.96.0. This is caused by the TriliumNext project migrating to a different GitHub repository and renaming the application. The TriliumNext LXC script should be updated to accommodate the new repository and application name. ### 🔄 Steps to reproduce the issue. Step 1: `update` ### ❌ Paste the full error output (if available). ``` ______ _ ___ /_ __/____(_) (_)_ ______ ___ / / / ___/ / / / / / / __ `__ \ / / / / / / / / /_/ / / / / / / /_/ /_/ /_/_/_/\__,_/_/ /_/ /_/ ✔️ No update required. Trilium is already at 0.95.0 ``` ### 🖼️ Additional context (optional). According to [TriliumNext discussion 5867](https://github.com/orgs/TriliumNext/discussions/5867), Trilium's original developer, @zadam, agreed that the TriliumNext project is mature enough to regain the original name, Trilium. He transferred control of the original repository. Last week, [TriliumNext discussion 5845](https://github.com/orgs/TriliumNext/discussions/5845) announced that "Zadam's trilium repository is now under the TriliumNext organisation's umbrella." Yesterday's [Trilium Release v0.96.0](https://github.com/TriliumNext/Trilium/releases/tag/v0.96.0) is the first from the [TriliumNext/Trilium repository](https://github.com/TriliumNext/Trilium). Previous releases came from the [TriliumNext/Notes repository](https://github.com/TriliumNext/Notes), which now is archived.
saavagebueno added the bug label 2025-11-20 05:09:49 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1413
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?