Fri, 16 Dec 2022 09:10:36 +0100

Two `monitor-components` fixes (#4168)

The `monitor-components` workflow's purpose is to notify the Git for
Windows maintainers when new package versions are published and may need
to be integrated into Git for Windows.

This PR brings two improvements to this workflow:

- We now explicitly disable the workflow everywhere but the Git for
Windows fork of Git, instead of relying on scheduled workflows being
disabled in forks (of the fork) by default.
- The label and the URL of the Git Credential Manager part was fixed. I
noticed that the label was wrong when
https://github.com/git-for-windows/build-extra/pull/451 was opened but
failed to mention that it would close the issue
(https://github.com/git-for-windows/git/issues/4166)

Mon, 12 Dec 2022 15:25:31 +0100

Merge 'readme' into HEAD

Add a README.md for GitHub goodness.

Signed-off-by: Johannes Schindelin <[email protected]>

Tue, 6 Dec 2022 08:10:14 +0100

Merge 'readme' into HEAD

Add a README.md for GitHub goodness.

Signed-off-by: Johannes Schindelin <[email protected]>

Wed, 30 Nov 2022 08:33:14 +0100

Merge 'readme' into HEAD

Add a README.md for GitHub goodness.

Signed-off-by: Johannes Schindelin <[email protected]>

Wed, 23 Nov 2022 11:00:07 +0100

Merge 'readme' into HEAD

Add a README.md for GitHub goodness.

Signed-off-by: Johannes Schindelin <[email protected]>

Tue, 8 Nov 2022 11:38:47 +0100

monitor-updates: add libfido2 and libcbor (#4073)

We also need to monitor libfido2 (and its dependency libcbor) because
that library is responsible for support of security keys in OpenSSH,
e.g. making it work with Windows Hello.

Thu, 3 Nov 2022 20:20:55 +0100

mimalloc: allow running in Windows Nano Server containers (#4074)

The `GetNumaProcessorNode()` symbol is not defined in Nano Server's DLLs 
(because that function is long deprecated). This caused Git no longer to
work on Nano Server.

Instead of importing it statically, try to import it dynamically, and
fall back gracefully if it cannot be loaded.

This fixes https://github.com/git-for-windows/git/issues/4052

Thu, 3 Nov 2022 13:48:51 +0100

Fix Windows version resources (#4092)

Add `FileVersion`, which is a required string ([Microsoft
documentation](https://learn.microsoft.com/en-us/windows/win32/menurc/versioninfo-resource))
in the `StringFileInfo` block.
As not all required strings were present in the block, none were being
included.
Fixes #4090

After including the `FileVersion` string, all other defined strings are
now being included on executables.

File version information for `git.exe` has changed from:
```
PS C:\Program Files\Git\bin> [System.Diagnostics.FileVersionInfo]::GetVersionInfo("C:\Data\git-sdk-64\usr\src\git\git.exe") | Select-Object *

FileVersionRaw     : 2.38.1.1
ProductVersionRaw  : 2.38.1.1
Comments           :
CompanyName        :
FileBuildPart      : 1
FileDescription    :
FileMajorPart      : 2
FileMinorPart      : 38
FileName           : C:\Data\git-sdk-64\usr\src\git\git.exe
FilePrivatePart    : 1
FileVersion        :
InternalName       :
IsDebug            : False
IsPatched          : False
IsPrivateBuild     : False
IsPreRelease       : False
IsSpecialBuild     : False
Language           : English (United States)
LegalCopyright     :
LegalTrademarks    :
OriginalFilename   :
PrivateBuild       :
ProductBuildPart   : 1
ProductMajorPart   : 2
ProductMinorPart   : 38
ProductName        :
ProductPrivatePart : 1
ProductVersion     :
SpecialBuild       :
```

To the following:
```
PS C:\Program Files\Git\bin> [System.Diagnostics.FileVersionInfo]::GetVersionInfo("C:\Data\git-sdk-64\usr\src\git\git.exe") | Select-Object *

FileVersionRaw     : 2.38.1.1
ProductVersionRaw  : 2.38.1.1
Comments           :
CompanyName        : The Git Development Community
FileBuildPart      : 1
FileDescription    : Git for Windows
FileMajorPart      : 2
FileMinorPart      : 38
FileName           : C:\Data\git-sdk-64\usr\src\git\git.exe
FilePrivatePart    : 1
FileVersion        : 2.38.1.windows.1.10.g6ed65a6fab
InternalName       : git
IsDebug            : False
IsPatched          : False
IsPrivateBuild     : False
IsPreRelease       : False
IsSpecialBuild     : False
Language           : English (United States)
LegalCopyright     :
LegalTrademarks    :
OriginalFilename   : git.exe
PrivateBuild       :
ProductBuildPart   : 1
ProductMajorPart   : 2
ProductMinorPart   : 38
ProductName        : Git
ProductPrivatePart : 1
ProductVersion     : 2.38.1.windows.1.10.g6ed65a6fab
SpecialBuild       :
```

I wasn't really expecting `GIT_VERSION` to contain the Git commit, I was
hoping for just `2.38.1` or `2.38.1.1`, at least for the `FileVersion`
string.

Anybody know if it's possible to concatenate the `MAJOR`, `MINOR`,
`MICRO`, and `PATCHLEVEL` fields with dots, or if there's another
variable that can be used (with or without `PATCHLEVEL`)?
Alternatively, use the complete `GIT_VERSION` for both `FileVersion` and
`ProductVersion`.

Wed, 2 Nov 2022 14:53:10 +0100

Fix CTest failures (#3977)

When building Git via Visual Studio and then running the tests via CTest
(which is made very easy by Visual Studio), there are test failures.
This PR intends to address those.

This closes #3966

Mon, 31 Oct 2022 13:00:14 +0100

prerelease-2.38.1.windows.1-9-gbeeaffbd90-20221031120339

minor monitor-components improvements (#3983)