chore(deps): update ghcr.io/thomiceli/opengist docker tag to v1.10.0

[renovate]

This PR contains the following updates:

Package	Update	Change
ghcr.io/thomiceli/opengist	minor	1.9.1 -> 1.10.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

thomiceli/opengist (ghcr.io/thomiceli/opengist)

v1.10.0

Compare Source

See here how to update Opengist.

🔴 Deprecations

Removed in the next SemVer MAJOR version of Opengist.

• Use the configuration option index/OG_INDEX instead of index.enabled/OG_INDEX_ENABLED. The default value is bleve.
• The configuration index.dirname/OG_INDEX_DIRNAME will be removed. If you're using Bleve, the path of the index will be opengist.index.

Added

• Helm Chart (#​454)
• Meilisearch indexer (#​444)
• Prometheus metrics (#​439)
• Config to name the OIDC provider (#​435)
• Read admin group from OIDC token claim (#​445)
• More translation strings (#​438)

Fixed

• Garbled text display issues for non-English Unicode characters in browsers (#​441)
• Test database when running go test (#​442)
• Allow lag between admin invitation creation and test assertion (#​452)
• gist.html using relative URL (#​451)
• Do not hide file delete button on gist edit page (#​447)

Other

• Update deps Golang & JS deps (#​455)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[f2c-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[f2c-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[wanghe-fit2cloud]

The provided code snippet shows an update to the image field for a service called opengist. The change from version 1.9.1 to 1.10.0 suggests that there might be new features, improvements, or bug fixes in version 1.10. However, without more information about what changes are present between these versions, it's difficult to determine if it's worth updating to this newer version. Here are some general points to consider when reviewing such changes:

1. Version Details: Always refer to the official documentation of the service or package to understand any known issues with each version.

2. Testing: Before deploying the changes, thoroughly test the application on a staging environment to ensure compatibility and stability.

3. Backup: Make sure you have backups of your current setup in case something goes wrong during the upgrade process.

4. Performance: Check performance metrics to see if there is any decrease in speed, memory usage, or other resource consumption after upgrading.

5. Documentation Review: Ensure that any changes made do not affect existing configurations or APIs required by users or applications interacting with the service.

If there is no specific reason to use version 1.10.0 over 1.9.1 based on testing, maintaining the current version could still provide adequate functionality while keeping costs low. It's also important to monitor ongoing development to keep up with future updates.

[wanghe-fit2cloud]

The provided code difference shows an update of the image version from "1.9.1" to "1.10.0". This is generally a good approach to incorporate newer updates with bug fixes and improvements, but it should also consider checking if there are any specific changes in the configuration or requirements related to this new version.

• Review Changes: Ensure that any custom configurations specified after "container_name:" have not been altered unintentionally.
• Network Check: Since there might be dependencies on other services (specified under "networks:"), verify that they can still communicate seamlessly with the updated service.
• Logs / Output Monitor: Test running the service with "ghcr.io/thomiceli/opengist:1.10.0" in development stages and monitor for any unexpected behavior that could arise from these differences.

Overall, updating to version 1.10.0 seems correct based on the initial intent. The next steps should involve careful testing and verification before deploying the change to production environments.

[wanghe-fit2cloud]

The code difference you provided is for a Docker Compose file where service opengist's image has been updated from version 1.9.1 to version 1.10.0. The changes include:

• Updated the image tag from ghcr.io/thomiceli/opengist:1.9.1 to ghcr.io/thomiceli/opengist:1.10.0.
• Ensured that container name ${CONTAINER_NAME} remains referenced correctly.

These changes can be considered appropriate if you intend to upgrade the version to capture bug fixes, security patches, or new features introduced in version 1.10.0 of the container.

Optimization Suggestion: If you have multiple instances of this service and want to minimize configuration redundancy, consider using environment variables or parameters in your Docker Compose file instead of directly embedding them within the service definition. This approach keeps your compose files cleaner and easier to manage. For example:

services:
  opengist:
    image: ghcr.io/thomiceli/opengist:${OPEN_GIST_VER}
    container_name: ${CONTAINER_NAME:-default_container_name} # Default value if not specified
    restart: unless-stopped
    networks: []

In this revised version:

• All occurrences of $CONTAINER_NAME and $OPEN_GIST_VER are replaced with placeholders (${...}).
• A default value ("default_container_name") is set for container_name, avoiding errors when it hasn't been defined elsewhere (such as through command-line arguments or Docker environment variables).