Skip to content

fix: Update Trilium repository URL and image to v0.100.0#12

Open
kalbasit wants to merge 1 commit into
TriliumNext:mainfrom
kalbasit:use-correct-trilium-image
Open

fix: Update Trilium repository URL and image to v0.100.0#12
kalbasit wants to merge 1 commit into
TriliumNext:mainfrom
kalbasit:use-correct-trilium-image

Conversation

@kalbasit

Copy link
Copy Markdown

Updated Trilium repository references and upgraded to the latest version.

  • Updated the maintainer URL from https://github.com/TriliumNext/Notes to https://github.com/TriliumNext/Trilium
  • Changed the image repository from triliumnext/notes to triliumnext/trilium
  • Upgraded the image tag from v0.92.4 to v0.100.0
  • Removed duplicate image configuration from the release.yaml template

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @kalbasit, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on updating the Trilium Helm chart to align with recent changes in the upstream Trilium project. It ensures the chart references the correct repository and image names, while also bringing the application version up to the latest v0.100.0. This update is crucial for maintaining compatibility and providing users with the most current and stable version of Trilium.

Highlights

  • Repository URL Update: The maintainer URL for 'triliumnext' in the Chart.yaml has been updated to reflect the correct repository: https://github.com/TriliumNext/Trilium.
  • Image Repository and Tag Upgrade: The values.yaml file now points to the correct image repository triliumnext/trilium and has upgraded the image tag from v0.92.4 to v0.100.0.
  • Configuration Cleanup: Duplicate image configuration and extraneous blank lines have been removed from the release.yaml template, streamlining the chart definition.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly updates the Trilium repository URL and image version. The changes in values.yaml properly set the image to triliumnext/trilium:v0.100.0, and removing the hardcoded image from release.yaml is a good practice.

However, for the chart to be fully consistent with this update, a couple of important changes are missing in charts/trilium/Chart.yaml:

  • appVersion Mismatch: The appVersion is still 0.92.4. It should be updated to 0.100.0 to reflect the actual application version being deployed. This is crucial for correct chart metadata.
  • Incorrect sources URL: In the sources list, the URL hhttps://github.com/TriliumNext/Notes is both outdated and contains a typo (hhttps). It should be corrected to https://github.com/TriliumNext/Trilium.
  • (Optional) Update description: For consistency with the repository rename, you might also want to update the description which still refers to "Trilium Notes".

Applying these fixes will ensure the chart is accurate and provides a clear experience for users.

Updated Trilium repository references and upgraded to the latest version.

- Updated the maintainer URL from `https://github.com/TriliumNext/Notes` to `https://github.com/TriliumNext/Trilium`
- Changed the image repository from `triliumnext/notes` to `triliumnext/trilium`
- Upgraded the image tag from `v0.92.4` to `v0.100.0`
- Removed duplicate image configuration from the release.yaml template
@kalbasit kalbasit force-pushed the use-correct-trilium-image branch from acc1529 to 5890493 Compare December 24, 2025 07:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant