Skip to content

chore(release): 3.87.0

Nigel Kukard requested to merge nkukard/container-registry:nkupdates into main

What does this MR do?

chore(release): 3.87.0

3.87.0 (2023-12-05)

✨ Features ✨

  • db: add primary database config and use for migrations (4d1bf37)
  • enable registry to store artifactType with OCI manifests (5e3b76f)
  • registry: import-command: add debug-server option (59064d9)

🐛 Bug Fixes 🐛

  • api/gitlab/v1: order tag pagination correctly by publish_at (3c29839)
  • don't skip check on post-deployment migrations prior to import (6d76c0e)
  • silence ominous maxprocs log message (aaf8577)

⚙️ Build ⚙️

  • deps: update module github.com/gorilla/mux to v1.8.1 (a58bf89)
  • deps: update module github.com/spf13/cobra to v1.8.0 (d85ac07)
  • deps: update module github.com/vmihailenco/msgpack/v5 to v5.4.1 (4035764)
  • deps: update module github.com/xanzy/go-gitlab to v0.94.0 (4d4b344)
  • deps: update module gitlab.com/gitlab-org/labkit to v1.21.0 (51cc6a9)
  • deps: update module golang.org/x/crypto to v0.16.0 (8eaf5e4)
  • deps: update module golang.org/x/oauth2 to v0.14.0 (3089ffc)
  • deps: update module golang.org/x/oauth2 to v0.15.0 (6f898f7)
  • deps: update module golang.org/x/time to v0.4.0 (1b23c8d)
  • deps: update module google.golang.org/api to v0.151.0 (5a37085)
  • deps: update module google.golang.org/api to v0.152.0 (a5ad8c7)

Related to

Author checklist

  • Feature flags
    • Added feature flag:
    • This feature does not require a feature flag
  • I added unit tests or they are not required
  • I added documentation (or it's not required)
  • I followed code review guidelines
  • I followed Go Style guidelines
  • For ~database changes including schema migrations:
    • Manually run up and down migrations in a postgres.ai production database clone and post a screenshot of the result here.
    • If adding new queries, extract a query plan from postgres.ai and post the link here. If changing existing queries, also extract a query plan for the current version for comparison.
    • Do not include code that depends on the schema migrations in the same commit. Split the MR into two or more.
  • Ensured this change is safe to deploy to individual stages in the same environment (cny -> prod). State-related changes can be troublesome due to having parts of the fleet processing (possibly related) requests in different ways.

Reviewer checklist

  • Ensure the commit and MR tittle are still accurate.
  • If the change contains a breaking change, apply the ~"breaking change" label.
  • If the change is considered high risk, apply the label ~high-risk-change
  • Identify if the change can be rolled back safely. (note: all other reasons for not being able to rollback will be sufficiently captured by major version changes).

If the MR introduces ~database schema migrations:

  • Ensure the commit and MR tittle start with fix:, feat:, or perf: so that the change appears on the Changelog
If the changes cannot be rolled back follow these steps:
  • If not, apply the label ~"cannot-rollback".
  • Add a section to the MR description that includes the following details:
    • The reasoning behind why a release containing the presented MR can not be rolled back (e.g. schema migrations or changes to the FS structure)
    • Detailed steps to revert/disable a feature introduced by the same change where a migration cannot be rolled back. (note: ideally MRs containing schema migrations should not contain feature changes.)
    • Ensure this MR does not add code that depends on these changes that cannot be rolled back.

Merge request reports