Dagger 0.19.9 access to container in private registry

[wet crescent]

Hello, I'm struggling to find the root cause of breaking pipelines that happened just after we upgraded to 0.19.19.

Seems like when accessing a container from a private registry, in a delayed step, the credentials are not being chained?
I've tried to reproduce it as simple as possible below:

func (m *Tests) PullWithCreds(ctx context.Context) (string, error) {
    ctr := dag.Container().
        WithRegistryAuth("private.registry.net", "nadir.lloret", dag.SetSecret("foobar", "xxxxxxxxxxxxxxxx")).
        From("private.registry.net/base-noble:latest")
    return ctr.File("/etc/hosts").Digest(ctx)
}

This works on 0.19.8, but breaks with 0.19.9 with:

failed to copy: httpReadSeeker: failed open: unexpected status from GET request to https://private.registry.net/base-noble/blobs/sha256:b3d818dbc26dc195a7ecc9ef9f2ddfe34c5062bd29b25c80aa6006594aea166e: 401 Unauthorized
  unauthorized: unauthorized to access repository: base-noble, action: pull: unauthorized to access repository: base-noble, action: pull

Has anything intentionally changed that I'm missing from release notes?

Thanks!

Dagger 0.19.9 access to container in private registry

[kindred fog]

hey @wet crescent ! it's a regression from v0.19.9 which we're fixing ASAP https://github.com/dagger/dagger/issues/11667

cc @acoustic gull

[wet crescent]

oh! I missed the bug report, sorry !

Thanks, i'll keep an eye on it 🙂

[acoustic gull]

PR has been approved and will be part of the next release 🙏

[bitter wyvern]

Ran into this today as well! Glad it's being fixed!

[slow crescent]

any sense when that next release might get cut?

[acoustic gull]

it should be today or tomorrow, we have another fix in (an edge case we missed for a user)

[stiff stirrup]

it went out yesterday, can upgrade anytime now