No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

This is intentional. The old way was really frustrating for a lot of use cases.

You will either need to pin you version to the old one, or update your code and the way you expect the build to work.

So how can I get the image hash with the new version? Should I parse the output of repoDigest?

Do you need the hash? The Image now behaves like a normal Pulumi resource, maybe you can use that functionality instead? For example, opt dependsOn can now have the image passed to it, since it is updated only when the image is really changed (before, the image resource always changed, even if there was no actual change involved).

If you do need the hash, then: I don't know! I'll have a quick look.

This is what I have:

```const appImage = new docker.Image("app-image", {
  imageName: `<http://gcr.io/${project}/${imageName}|gcr.io/${project}/${imageName}>`
}

const appService = new gcp.cloudrunv2.Service("app-service", {
  location: location,
  template: {
    containers: [
      {
        image: appImage.imageName,
      },
    ],
  },
  traffics: [
    {
      type: "TRAFFIC_TARGET_ALLOCATION_TYPE_LATEST",
      percent: 100,
    },
  ],
}, {
  dependsOn: [appImage],
});```

I want the `appService` resource to be updated when `appImage` is updated

I expect that to work. Does it update the service and the service doesn't change? Or does it not update the service at all?

So `appImage` gets updated, but `appService` doesn’t get updated at all

I've looked through the docs and it looks all good to me. You could maybe try changing the dependsOn from appImage to appImage.repoDigest, but if that works, then I'm at a loss to explain why.
I'd raise an issue, either way.

`appImage.repoDigest` won’t work with dependsOn because it’s not a resource

The `repoDigest` is a valid fully qualified image name - so you should be able to pass that directly instead of `imageName` to get the behavior you are looking for here.  The name is slightly unusual, but derived from the term the Docker API uses to refer to this. 