# Intégration externe - Accéder au changelog de la version actuelle ou future **URL:** \ **Category:** Demandes livrées\ **Tags:** in-progress\ **Created:** [Août 15, 2026, 2:45 UTC](https://community.gladysassistant.com/t/integration-externe-acceder-au-changelog-de-la-version-actuelle-ou-future/10575 "2026-08-15T14:45:22Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![cursor-bot](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cursor-bot/32/22252_2.png) [@cursor-bot](https://community.gladysassistant.com/u/cursor-bot)\ **Post date:** [Août 17, 2026, 12:05 UTC](https://community.gladysassistant.com/t/integration-externe-acceder-au-changelog-de-la-version-actuelle-ou-future/10575/2 "2026-08-17T12:05:55Z")
Salut tout le monde ! Ce sujet est désormais **en cours de développement**. Une PR a été ouverte pour lier le numéro de version d’une intégration externe à son changelog : > > > Implements feature request: https://community.gladysassistant.com/t/integration-…externe-acceder-au-changelog-de-la-version-actuelle-ou-future/10575 > > \### Description > > In the supervision block of an external integration, the version number is now a link to that version's changelog: > > \- the \*\*green banner\*\* after an update ("Integration updated to version 1.2.0.") > \- the \*\*blue banner\*\* when the integration was already up to date ("The integration is already up to date (version 1.2.0)…") > \- the \*\*"Version" row\*\* of the details list (the currently installed version) > > Users who do not follow the forum had no way to know what a new version changes; the release notes already exist on the integration's repository, they were just never linked from Gladys. > > \*\*Where the URL comes from.\*\* It is derived client-side from data the front already has — the integration's \`store\_slug\` (\`owner/repo\`) and its version — so nothing new is plumbed through the supervisor, the store index or the manifest. > > \*\*Why the releases page filtered on the version\*\* (\`https://github.com/\/\/releases?q=\&expanded=true\`) rather than \`.../releases/tag/\\`: the tag name is the integration author's choice, and \`1.2.0\` and \`v1.2.0\` are both common in the wild (Gladys itself tags with the \`v\` prefix). Guessing the wrong one is a plain 404, whereas the filtered releases list matches either form and shows the release notes expanded. When the version is unknown it degrades to the plain releases page, and a repository that publishes no release lands on a page that says so. > > A \*\*dev install\*\* (Docker image only, no \`store\_slug\` and therefore no repository) has no changelog to point at: its version stays plain text rather than becoming a link that leads nowhere. > > \*\*On the translations\*\*: the banner sentences are left untouched in the locale files. The version is split out of the already-interpolated string at render time, so where it sits in the sentence ("mise à jour en version 1.2.0", "auf Version 1.2.0 aktualisiert") stays the translator's business instead of being cut into fragments. A new \`changelogTitle\` key was added to \`en\`, \`fr\` and \`de\` for the link's tooltip. > > \`docs/specs/external-integrations.md\` is updated in the same diff (B.8 screen table and B.9), as required for any change to external-integration behavior. > > This pull request was produced by an automated run. > > \## Forum > > Forum: https://community.gladysassistant.com/t/integration-externe-acceder-au-changelog-de-la-version-actuelle-ou-future/10575 > > \### Checklist > > \- \[x\] Tests pass: \`cd server && npm run coverage\` (Codecov requires 100% coverage on changed lines) and Cypress (\`npm run cypress:run\`) if the UI changed — no server file is touched by this PR; the front has no unit-test script and is validated by eslint, \`compare-translations\` and the build > \- \[x\] Linter and prettier pass on both front and server (\`npm run eslint\`, \`npm run prettier\`) — \`prettier\`, \`prettier-check\`, \`eslint\`, \`compare-translations\` and \`build\` all pass in \`front/\` > \- \[x\] No undocumented breaking change > > > \--- > \_Generated by \[Claude Code\](https://claude.ai/code/session\_01REGRUvErzpwtSrsi9gKh4J)\_ > > > \## Summary by CodeRabbit > > \* \*\*New Features\*\* > \* Integration versions now link to the corresponding GitHub release changelog when available. > \* Update results include a localized link to view the changelog for the installed version. > \* Hardware grants can be managed from the integration configuration screen. > \* Versions remain plain text for developer installations without an associated repository. > > \* \*\*Localization\*\* > \* Added changelog link labels in English, French, and German. N’hésitez pas à suivre la PR, à tester dès que possible et à faire vos retours ici. --- _[View the full topic](https://community.gladysassistant.com/t/integration-externe-acceder-au-changelog-de-la-version-actuelle-ou-future/10575)._