Repository navigation
Promotion partielle : mise à jour du front fiabilisée (#463), avec #461 et #462 - #470
Merged
Merged
Conversation
Bumps the angular group in /src/front/InSeconds.Client with 3 updates: [@angular/cdk](https://github.com/angular/components), [@angular/build](https://github.com/angular/angular-cli) and [@angular/cli](https://github.com/angular/angular-cli). Updates `@angular/cdk` from 22.2.3 to 22.2.4 - [Release notes](https://github.com/angular/components/releases) - [Changelog](https://github.com/angular/components/blob/main/CHANGELOG.md) - [Commits](angular/components@v22.2.3...v22.2.4) Updates `@angular/build` from 22.2.3 to 22.2.4 - [Release notes](https://github.com/angular/angular-cli/releases) - [Changelog](https://github.com/angular/angular-cli/blob/v22.2.4/CHANGELOG.md) - [Commits](angular/angular-cli@v22.2.3...v22.2.4) Updates `@angular/cli` from 22.2.3 to 22.2.4 - [Release notes](https://github.com/angular/angular-cli/releases) - [Changelog](https://github.com/angular/angular-cli/blob/v22.2.4/CHANGELOG.md) - [Commits](angular/angular-cli@v22.2.3...v22.2.4) --- updated-dependencies: - dependency-name: "@angular/cdk" dependency-version: 22.2.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: angular - dependency-name: "@angular/build" dependency-version: 22.2.4 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: angular - dependency-name: "@angular/cli" dependency-version: 22.2.4 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: angular ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps WolverineFx.EntityFrameworkCore from 6.54.0 to 6.57.0 Bumps WolverineFx.Http from 6.54.0 to 6.57.0 Bumps WolverineFx.Http.FluentValidation from 6.54.0 to 6.57.0 Bumps WolverineFx.Postgresql from 6.54.0 to 6.57.0 Bumps WolverineFx.RuntimeCompilation from 6.54.0 to 6.57.0 --- updated-dependencies: - dependency-name: WolverineFx.EntityFrameworkCore dependency-version: 6.57.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: WolverineFx.Http dependency-version: 6.57.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: WolverineFx.Http.FluentValidation dependency-version: 6.57.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: WolverineFx.Postgresql dependency-version: 6.57.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: WolverineFx.RuntimeCompilation dependency-version: 6.57.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…aging/nuget-minor-patch-409bfce58e Bump the nuget-minor-patch group with 5 updates
…t/InSeconds.Client/env/staging/angular-c7d7794ce7 Bump the angular group in /src/front/InSeconds.Client with 3 updates
… un module introuvable Le rechargement automatique n'activait jamais la version prête : le service worker gardait la page sur l'ancienne, la nouvelle était annoncée de nouveau et le garde-fou affichait le bandeau (UpdatePrompt: reload-loop). Un module chargé à la demande introuvable après un déploiement recharge la page une fois au lieu d'être remonté. Claude-Session: https://claude.ai/code/session_018kRWbfhvkeuSEaC7dfahTR
…arning en prod et au staging
Le paramètre {Level} du journal d'indice était pris par Grafana pour le niveau du journal (indices classés « 1 » et « 2 »).
Les logs System.Net.Http.HttpClient (Information) écrivaient l'URL de ping healthchecks.io en clair.
…vables dans le tableau Exploitation
Front : activer la nouvelle version avant de recharger, recharger sur un module introuvable
Repère les onglets restés bloqués sur une ancienne version du front, d'après la version remontée avec chaque erreur.
|
Oasis35
marked this pull request as ready for review
November 1, 2026 07:32
Oasis35
added a commit
that referenced
this pull request
Nov 1, 2026
Remerge de main dans env/staging après #470
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Clément · project thread
Promotion de
env/stagingarrêtée au merge de #463 (1336e38), sans le lecteur #464 (qui reste dans #465, en brouillon).Pourquoi
Le 01/11, un téléphone est resté sur le front du 28/10 au staging, même après une reconnexion : il a fallu effacer les données du site. La version de ce téléphone date d'avant #463, qui active la nouvelle version (
activateUpdate()) avant de recharger. Sans ça, le service worker resservait l'ancienne version, et le garde-fou affichait le bandeau (UpdatePrompt: reload-loop, déjà vu 8 fois en prod sur 7 jours). La prod a encore ce défaut.Contenu (tout est déjà testé au staging depuis le 29/10)
HintLeveldans les journaux, logs HttpClient en Warning ; doc des sous-agents et hooks ; tableau Grafana Exploitation (bandeau de nouvelle version, modules introuvables).Merge commit (jamais squash) :
1336e38est un commit deenv/staging, donc la promotion suivante (#465) reste sans conflit.Generated by Claude Code