Skip to content

chore(release): 3.84.0

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

What does this MR do?

chore(release): 3.84.0

3.84.0 (2023-09-26)

✨ Features ✨

  • cache: use repository cache to complete blob upload (c678843)
  • handlers: expose database usage in v2 headers (121e440)
  • handlers: use accurate layer media types by default (1d7dc96)
  • use JSON format for sorting tags by name in descending order (eb20a87)

⚙️ Build ⚙️

  • deps: update module github.com/aws/aws-sdk-go to v1.45.11 (c2e742b)
  • deps: update module github.com/aws/aws-sdk-go to v1.45.6 (97ac190)
  • deps: update module github.com/getsentry/sentry-go to v0.24.0 (3f90827)
  • deps: update module github.com/getsentry/sentry-go to v0.24.1 (970f81a)
  • deps: update module github.com/miekg/dns to v1.1.56 (62c3c4e)
  • deps: update module golang.org/x/oauth2 to v0.12.0 (837e746)
  • deps: update module google.golang.org/api to v0.142.0 (2991e99)

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