Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: minio/minio-go
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v7.0.92
Choose a base ref
...
head repository: minio/minio-go
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v7.0.93
Choose a head ref
  • 9 commits
  • 32 files changed
  • 8 contributors

Commits on May 19, 2025

  1. Configuration menu
    Copy the full SHA
    6564f61 View commit details
    Browse the repository at this point in the history

Commits on May 21, 2025

  1. replication: add in progress metric and target status (#2109)

    as seen by each node.
    poornas authored May 21, 2025
    Configuration menu
    Copy the full SHA
    48ee2d3 View commit details
    Browse the repository at this point in the history

Commits on May 28, 2025

  1. Add Checksums to versioned list results (#2116)

    With metadata option, allow server to return version checksums as well.
    
    To be used by data integrity checker tool.
    klauspost authored May 28, 2025
    Configuration menu
    Copy the full SHA
    07f51b1 View commit details
    Browse the repository at this point in the history

Commits on May 29, 2025

  1. Configuration menu
    Copy the full SHA
    ebcbfeb View commit details
    Browse the repository at this point in the history

Commits on Jun 3, 2025

  1. Configuration menu
    Copy the full SHA
    258935a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    14d7d61 View commit details
    Browse the repository at this point in the history

Commits on Jun 4, 2025

  1. Configuration menu
    Copy the full SHA
    496595d View commit details
    Browse the repository at this point in the history

Commits on Jun 9, 2025

  1. Add support of error responses in 200 OK body (#2115)

    An S3 server can respond with 200 OK with an S3 Error response for long
    standing calls, such as S3 listing when a prefix contains a lot of
    entries.
    
    This commit will support this use case. This can only be enabled with
    specific calls that return XML as a successful response, so this will not
    be confused with GetObject returning a valid document that contains an
    S3 error response.
    
    Supported calls: CompleteMultipartUpload and DeleteMultiObjects.
    vadmeste authored Jun 9, 2025
    Configuration menu
    Copy the full SHA
    7a9dff0 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    dc94dff View commit details
    Browse the repository at this point in the history
Loading