Skip to content

Bump Container Registry to v3.60.1-gitlab

What does this MR do?

3.60.1 (2022-10-28)

Bug Fixes

  • handlers: return 404 on v1 compliance check when metadata database is disabled (eb44acf)

3.60.0 (2022-10-25)

Bug Fixes

  • s3: treat s3 serialization error as retry-able (#753) (f91a995)

Features

  • configuration: add ability to log specific CF-ray header (106bb9e)
  • s3 driver support for ExistsPath (37b8f72)

Performance Improvements

  • temporary workaround for top-level namespace usage calculation (3b3a19a)

3.59.0 (2022-10-24)

Features

  • configuration: remove the ability to externally configure testslowimport (27f9752)

Related issues

Related to: gitlab-org/container-registry#821 (closed)

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • Merge Request Title and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Tests added
  • Integration tests added to GitLab QA
  • Equivalent MR/issue for omnibus-gitlab opened
  • Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.

Merge request reports