The pin was built 2026-08-20; the container on the machine runs the 2026-09-17 build of the same floating tag. Taking the module would have been a month-long downgrade of a service that has already migrated its own schema forward.
Third module in a row whose pin had aged this way — the forge, the package registry, now this one. The pattern is hq issue 099; this is the instance.
Dates read from each image's own config at the registry, not guessed from tag names.
The pin was built **2026-08-20**; the container on the machine runs the **2026-09-17** build of the same floating tag. Taking the module would have been a month-long downgrade of a service that has already migrated its own schema forward.
Third module in a row whose pin had aged this way — the forge, the package registry, now this one. The pattern is [hq issue 099](https://git.novox.be/novox/hq/src/branch/main/04-ISSUES/099-a-modules-image-pin-ages-into-a-downgrade/00-report.md); this is the instance.
Dates read from each image's own config at the registry, not guessed from tag names.
The pin was a month old — 2026-08-20 against the 2026-09-17 image the container runs.
Third module in a row whose pin had aged into a downgrade; the pattern is hq issue 099.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The pin was built 2026-08-20; the container on the machine runs the 2026-09-17 build of the same floating tag. Taking the module would have been a month-long downgrade of a service that has already migrated its own schema forward.
Third module in a row whose pin had aged this way — the forge, the package registry, now this one. The pattern is hq issue 099; this is the instance.
Dates read from each image's own config at the registry, not guessed from tag names.