Matt Thalman

Another example where this would have been useful: https://github.com/dotnet/dotnet-docker/issues/2417. The `krb5` package had been updated with a security fix but the parent Alpine image never changed. This meant we never...

As stated in https://github.com/dotnet/docker-tools/pull/824#issuecomment-900506374, the plan is stored the package graph as metadata in the image info file. In addition to actually storing this metadata, we should also provide notifications...

Now that the infrastructure supports the generation of SBOMs, it seems more appropriate to consume the SBOM's description of the packages that are installed in an image rather than duplicating...

With [CBL-Mariner 2.0](https://github.com/dotnet/dotnet-docker/pull/3739), there are no longer the necessary commands to execute the [scripts to get the set of installed packages](https://github.com/dotnet/docker-tools/pull/824) in a Mariner 2.0 container because the `sed` and...

This will need to account for the newly added [Chiseled Ubuntu Dockerfiles](https://github.com/dotnet/dotnet-docker/pull/3996). Those are unique in that they are based on `scratch` and use the [chisel](https://github.com/canonical/chisel) tool to install the...

Related to https://github.com/dotnet/dotnet-docker/issues/4771

[Triage] An important scenario to consider here is the dev workflow. For feature development, where does a PR get checked into? How does it flow to other branches? It's also...

Could `nightly` be subscribed to multiple channels? Leading up to .NET 8, we've got three active installer branches: `release/8.0.1xx.rc2`, `release/8.0.1xx`, and `main`. Obviously, we can have only one 8.0 represented...

> I was intending to show the dev workflow/code flow only, not dependency updates. Ok, I misinterpreted what `automatic dependency flows` meant. I assumed it meant the flow from `installer`...

[Triage] This would add another section that builds upon the output of the existing [ASP.NET](https://github.com/dotnet/dotnet-docker/blob/main/documentation/image-artifact-details.md#aspnet-core-image) section and includes the necessary paths for targeting .NET Monitor's installation.