The module pinned a digest for 6.10.1. The machine whose service it takes over runs 6.10.3. Taking it would have been a downgrade, which is what the forge's first cutover cost an
outage to learn — so the runbook now checks version parity before anything else, and this is that
check applied to the next module in line.
Pinned to sha256:7b067a47…, which is exactly verdaccio/verdaccio:6.10.3 and exactly the image
digest the running container resolves to.
6.10.4 is published. Moving to it is an upgrade, deliberate and separate from a cutover; a cutover
changes who owns a service, not which version of it runs.
Note for whoever schedules that cutover: this module is not ready to take. Its declared config.yaml drops a rule the machine's has — one private scope kept local and never proxied —
and there is no mechanism to carry it across. Written up as hq issue 098.
The module pinned a digest for **6.10.1**. The machine whose service it takes over runs
**6.10.3**. Taking it would have been a downgrade, which is what the forge's first cutover cost an
outage to learn — so the runbook now checks version parity before anything else, and this is that
check applied to the next module in line.
Pinned to `sha256:7b067a47…`, which is exactly `verdaccio/verdaccio:6.10.3` and exactly the image
digest the running container resolves to.
6.10.4 is published. Moving to it is an upgrade, deliberate and separate from a cutover; a cutover
changes who owns a service, not which version of it runs.
Note for whoever schedules that cutover: this module is **not** ready to take. Its declared
`config.yaml` drops a rule the machine's has — one private scope kept local and never proxied —
and there is no mechanism to carry it across. Written up as
[hq issue 098](https://git.novox.be/novox/hq/src/branch/main/04-ISSUES/098-taking-a-module-replaces-a-configuration-nobody-compared/00-report.md).
The rule the forge's cutover taught: a module that takes over a running service must not
carry an older image than the one running, or the cutover is a downgrade nobody asked for.
6.10.4 exists; moving to it is an upgrade and its own act.
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 module pinned a digest for 6.10.1. The machine whose service it takes over runs
6.10.3. Taking it would have been a downgrade, which is what the forge's first cutover cost an
outage to learn — so the runbook now checks version parity before anything else, and this is that
check applied to the next module in line.
Pinned to
sha256:7b067a47…, which is exactlyverdaccio/verdaccio:6.10.3and exactly the imagedigest the running container resolves to.
6.10.4 is published. Moving to it is an upgrade, deliberate and separate from a cutover; a cutover
changes who owns a service, not which version of it runs.
Note for whoever schedules that cutover: this module is not ready to take. Its declared
config.yamldrops a rule the machine's has — one private scope kept local and never proxied —and there is no mechanism to carry it across. Written up as
hq issue 098.