chore: v3.6.0-alpha.9 changelog bump (PROJQUAY-1486) (quay#763)

Signed-off-by: GitHub <[email protected]>

Co-authored-by: thomasmckay <[email protected]>

chore: v3.5.1 changelog (PROJQUAY-1891) (quay#752)

chore: v3.6.0-alpha.8 changelog bump (PROJQUAY-1486) (quay#732)

Signed-off-by: GitHub <[email protected]>

Co-authored-by: thomasmckay <[email protected]>

chore: v3.6.0-alpha.7 changelog bump (PROJQUAY-1486) (quay#730)

Signed-off-by: GitHub <[email protected]>

Co-authored-by: thomasmckay <[email protected]>

chore: correct git-chglog config (PROJQUAY-1468) (quay#728)

release: fixing Release action (PROJQUAY-1486) (quay#723)

wip

chore: v3.6.0-alpha.2 changelog bump (PROJQUAY-1486) (quay#721)

chore: v3.6.0-alpha.2 changelog bump (PROJQUAY-1486) (quay#721)

gc: fix GlobalLock ttl unit and increase gc workers lock timeout (qua…

…y#712)

Correctly converts the given ttl from seconds to milliseconds when
passed to Redis (redlock uses 'px', not 'ex'). Also increase the lock
timeout of gc workers to 1 day.

Some iteration, for repos with large numbers of tags (1000s), will
take more than 15 minutes to complete. This change will prevent multiple
workers GCing the same repo, and one possibly preempting
another. GlobalLock's ttl will make the lock available again when
expired, but will not actually stop execution of the current GC
iteration until the GlobalLock context is done. Having a 1 day timeout
should be enough.

NOTE: The correct solution would have GlobalLock should either renew
the lock until the caller is done, or signal that it is no longer
valid to the caller.