This is the reason: https://github.com/dotnet/runtime/issues/80023 When the .NET runtime can't determine the file creation date on linux, it silently falls back to the last modified time, and there's no way for us to stop that. It would be better if it threw an error so that we could decide how to proceed, but it's just a silent switch that we can't control. So we will need them to resolve that, although it doesn't look like they want to change the behavior right now.