ci-package-builder: Hardcode the releases to freeze MRs for

The pipeline really tries to ensure that updates to v2019 and v2020 go through the -updates/-security branches given that they are stable releases.

Unfortunately, for the pipeline the apertis/v2021 branch looks like it is stable already even if we haven't released it yet, as it only looks at the name.

I guess we really have to hardcode the list of stable branches since there's not way for it to figure automatically the to-be-stable-but-not-released-yet case.

added 1 commit

• c183c11a - ci-package-builder: Hardcode the releases to freeze MRs for

Compare with previous version

mentioned in merge request pkg/golang-github-go-debos-fakemachine!5 (merged)

added 1 commit

• 62b51bff - ci-package-builder: Hardcode the releases to freeze MRs for

Compare with previous version

added 1 commit

• 7a699b07 - ci-package-builder: Hardcode the releases to freeze MRs for

Compare with previous version

resolved all threads

merged