chore(deps): bump azure-functions-core-tools from 4.12.0 to 4.13.0 in /test/instrumentation/azure-functions/fixtures/azfunc4

[dependabot]

Bumps azure-functions-core-tools from 4.12.0 to 4.13.0.

Release notes

Sourced from azure-functions-core-tools's releases.

4.13.0

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.

4.12.1

Azure Functions CLI 4.12.1

Host Version

• Host Runtime Version: 4.1048.200
• In-Proc CLI:
  • CLI Version: 4.6.0
  • Host Runtime Version: 4.49.100 (includes 4.849.100, 4.649.100)

Changes

• No changes to core CLI, in-proc CLI updated to 4.6.0 with host version 4.49.100

Changelog

Sourced from azure-functions-core-tools's changelog.

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)

Commits

• dd0daba Fix test where incompatible dependency version pulled from cpm (#5475)
• 43d6899 Update Release Notes| InProc 4.51.100 (#5468)
• 87fe3e8 Update Release Notes (#5466)
• 3197518 Use default host name for flex health check (#5462)
• 3ae1408 Skip worker version validation when Packages.props unchanged (#5464)
• aabf154 Bump safe NuGet deps and ignore host-pinned packages in dependabot (#5456)
• d38e6d2 Update host and worker versions, dependencies, and migrate to .NET 10 (#4850)
• 86e5229 Bump dotnet-sdk from 10.0.300 to 10.0.301 (#5334)
• d2d529b Bump https-proxy-agent (#5335)
• 3c6807e fix: replace deprecated url.parse in npm installer (#5371)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for azure-functions-core-tools since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)