winget is still showing 4.13.0 while 4.14.0 is the latest

I have seen this multiple times, so thought of raising an issue.

Version: [4.13.0](https://github.com/Azure/azure-functions-core-tools/releases/tag/4.13.0) was released 2 weeks ago, but winget only displayed that yesterday.

Have no idea when [4.14.0](https://github.com/Azure/azure-functions-core-tools/releases/tag/4.14.0) will be available.

```bash
> winget show Microsoft.Azure.FunctionsCoreTools
Found Azure Functions Core Tools [Microsoft.Azure.FunctionsCoreTools]
Version: 4.13.0
Publisher: Microsoft
Publisher Url: https://www.microsoft.com/
Publisher Support Url: https://github.com/Azure/azure-functions-core-tools/issues
Author: Microsoft Corporation
Moniker: functionscoretools
Description: The Azure Functions Core Tools provide a local development experience for creating, developing, testing, running, and debugging Azure Functions.
Homepage: https://github.com/Azure/azure-functions-core-tools
License: MIT
License Url: https://github.com/Azure/azure-functions-core-tools/blob/HEAD/LICENSE
Privacy Url: https://privacy.microsoft.com/privacystatement
Copyright: Copyright (c) .NET Foundation. All rights reserved.
Copyright Url: https://www.microsoft.com/legal/intellectualproperty/trademarks
Release Notes:
Azure Functions CLI 4.13.0
Host Version
- Host Runtime Version: 4.1051.300
- In-Proc CLI:
- CLI Version: 4.7.0
- Host Runtime Version: 4.51.100 (includes 4.851.100, 4.651.100)
Changes
- Removed warning log for remote build with Python 3.14 Flex apps, as remote build is now supported (#5375)
- Fixed npm postinstall silently swallowing extraction errors (#5281)
- Added lazy first-use install for npm RFC #868 compatibility (#5291)
- Added warning when key vault references fail to resolve (#5373)
- Replaced deprecated url.parse in npm installer (#5371)
- Enhanced func CLI static gitignore and streamlined Azurite entries (#5084)
- Bumped dotnet templates version to 4.0.5590 (#5271)
- Bumped https-proxy-agent dependency (#5335)
- Updated target framework to .NET 10 (#4850)
- Fix Flex Health Check to use defaultHostName instead of enabledHostNames (#5462)
- Added durable-functions dependency to package.json when creating Node.js durable function templates (#5495)
- Changed func start to bind to the IPv4 loopback address (127.0.0.1) by default instead of 0.0.0.0, and added an opt-in --address flag (and Host.LocalHttpAddress setting in local.settings.json) to override the bind address (#5484)
- Potential breaking change: the host now binds to 127.0.0.1 by default, so it is only reachable from the local machine. Setups that relied on binding to 0.0.0.0 — for example reaching the host from outside a Docker container via a published port — will no longer connect. Workaround: start the host with func start --address 0.0.0.0 (or set "LocalHttpAddress": "0.0.0.0" under Host in local.settings.json) to restore the previous behavior.
Release Notes Url: https://github.com/Azure/azure-functions-core-tools/releases/tag/4.13.0
Documentation:
Wiki: https://github.com/Azure/azure-functions-core-tools/wiki
Tags:
app-service
azure
azure-functions
functions
Installer:
Installer Type: wix
Installer Url: https://github.com/Azure/azure-functions-core-tools/releases/download/4.13.0/func-cli-4.13.0-x64.msi
Installer SHA256: 60c4fe33df379d6099967e1af38be5d3db84b06cf381579e6149fbff6e4f4295
Release Date: 2026-08-10
Offline Distribution Supported: true
```

Not sure whether the issue is on `winget` side or `azure-functions-core-tools` deployment side.

Start by comparing the 4.14.0 GitHub release with the winget listing shown in the issue, then determine whether the package metadata is maintained in this repository or deployed through winget. Done means identifying the source of the delay and confirming that winget exposes the latest Azure Functions Core Tools release.

Written by the indexing model from the issue text.