Hi, > On 6. Dec 2023, at 16:48, Emond Papegaaij <emond.papega...@gmail.com> wrote: > > We can switch from LastModifiedResourceVersion to something else in our > applications to work around this issue, but maybe we should consider > tracking down this issue and release a 9.16.1. I'd expect we are not the > only ones using LastModifiedResourceVersion.
I wonder how this is supposed to work at all... AFAIK git does not track the last modification date - so I guess that date would reflect whatever the modification date is on the machine of the developer that does the release...? -- Richard
