Bump azure-functions-core-tools from 4.12.1 to 4.14.0 in /api

[dependabot]

Bumps azure-functions-core-tools from 4.12.1 to 4.14.0.

Release notes

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

4.14.0

Azure Functions CLI 4.14.0

Host Version

• Host Runtime Version: 4.1052.200
• In-Proc CLI:
  • CLI Version: 4.7.0
  • Host Runtime Version: 4.51.100 (includes 4.851.100, 4.651.100)

Changes

• 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.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.

Changelog

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

Azure Functions CLI 4.14.0

Host Version

• Host Runtime Version: 4.1052.200
• In-Proc CLI:
  • CLI Version: 4.7.0
  • Host Runtime Version: 4.51.100 (includes 4.851.100, 4.651.100)

Changes

Commits

• 4a17060 Updating host version to 4.1052.200 (#5565)
• df2ab4b Fix CFS violations: route npm and NuGet through authenticated feeds in consol...
• 80dea00 Fix emulator steps hanging on Linux and macOS E2E pipelines (#5560)
• 26a9cbe Fix CFS pypi.org violations by moving PipAuthenticate before UsePythonVersion...
• 2276e8b Fix flaky TimerTrigger auth level test by using FuncInitWithRetryAsync (#5551)
• b523b02 Move NPM_CONFIG_USERCONFIG to job-level variables for E2E test coverage (#5548)
• 177216c Remove unused pipeline-utilities.psm1 (#5546)
• 6f316c7 Bump chalk from 4.1.2 to 6.0.0 in /eng/tools/publish-tools/npm (#5499)
• 6e27126 Switch to prepack (#5541)
• b3a5fd1 Reset release notes after 4.13.0 release (#5542)
• 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)

[dependabot]

Labels

The following labels could not be found: api, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[github-actions]

⚠️ Deprecation Warning: The deny-licenses option is deprecated for possible removal in the next major release. For more information, see issue 997.

Dependency Review

The following issues were found:

• ✅ 0 vulnerable package(s)
• ✅ 0 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ✅ 0 package(s) with unknown licenses.
• ⚠️ 2 packages with OpenSSF Scorecard issues.

See the Details below.

OpenSSF Scorecard

Package	Version	Score	Details
npm/@types/node	25.9.2	🟢 6.6	Details Check Score Reason Code-Review 🟢 9 Found 29/30 approved changesets -- score normalized to 9 Packaging ⚠️ -1 packaging workflow not detected CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Maintained 🟢 10 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Security-Policy 🟢 10 security policy file detected License 🟢 9 license file detected Signed-Releases ⚠️ -1 no releases found Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Pinned-Dependencies 🟢 8 dependency not pinned by hash detected -- score normalized to 8 Binary-Artifacts 🟢 10 no binaries found in the repo Fuzzing ⚠️ 0 project is not fuzzed
npm/azure-functions-core-tools	4.14.0	🟢 6.8	Details Check Score Reason Code-Review 🟢 10 all changesets reviewed Maintained 🟢 10 30 commit(s) and 26 issue activity found in the last 90 days -- score normalized to 10 Security-Policy 🟢 10 security policy file detected Packaging ⚠️ -1 packaging workflow not detected CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege Binary-Artifacts 🟢 9 binaries present in source code License 🟢 10 license file detected Fuzzing ⚠️ 0 project is not fuzzed Signed-Releases ⚠️ 0 Project has not signed or included provenance with any releases. Branch-Protection 🟢 5 branch protection is not maximal on development and all release branches SAST 🟢 8 SAST tool is not run on all commits -- score normalized to 8 Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0
npm/brace-expansion	5.0.9	🟢 7.2	Details Check Score Reason Binary-Artifacts 🟢 10 no binaries found in the repo Packaging ⚠️ -1 packaging workflow not detected Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Maintained 🟢 10 23 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10 Code-Review 🟢 3 Found 6/16 approved changesets -- score normalized to 3 Token-Permissions 🟢 10 GitHub workflow tokens follow principle of least privilege Security-Policy 🟢 10 security policy file detected Pinned-Dependencies 🟢 10 all dependencies are pinned CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected License 🟢 9 license file detected Fuzzing ⚠️ 0 project is not fuzzed Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md Signed-Releases ⚠️ -1 no releases found SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0
npm/chalk	6.0.0	🟢 4.6	Details Check Score Reason Packaging ⚠️ -1 packaging workflow not detected Security-Policy 🟢 10 security policy file detected Binary-Artifacts 🟢 10 no binaries found in the repo Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Code-Review 🟢 3 Found 10/30 approved changesets -- score normalized to 3 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Maintained 🟢 8 8 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 8 Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Fuzzing ⚠️ 0 project is not fuzzed License 🟢 10 license file detected Signed-Releases ⚠️ -1 no releases found Branch-Protection ⚠️ 0 branch protection not enabled on development/release branches SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0
npm/https-proxy-agent	9.1.0	⚠️ 2.8	Details Check Score Reason Maintained ⚠️ 1 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1 Code-Review ⚠️ 0 Found 0/6 approved changesets -- score normalized to 0 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Packaging ⚠️ -1 packaging workflow not detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Binary-Artifacts 🟢 10 no binaries found in the repo Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Security-Policy ⚠️ 0 security policy file not detected License ⚠️ 0 license file not detected Fuzzing ⚠️ 0 project is not fuzzed Signed-Releases ⚠️ -1 no releases found Branch-Protection 🟢 3 branch protection is not maximal on development and all release branches SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0
npm/lru-cache	11.5.1	🟢 4.4	Details Check Score Reason Code-Review ⚠️ 0 Found 1/29 approved changesets -- score normalized to 0 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Maintained 🟢 5 4 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 5 Packaging ⚠️ -1 packaging workflow not detected Binary-Artifacts 🟢 10 no binaries found in the repo Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected License 🟢 10 license file detected Fuzzing ⚠️ 0 project is not fuzzed Signed-Releases ⚠️ -1 no releases found Security-Policy 🟢 10 security policy file detected SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0 Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
npm/proxy-agent-negotiate	1.1.0	⚠️ 2.8	Details Check Score Reason Maintained ⚠️ 1 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1 Code-Review ⚠️ 0 Found 0/6 approved changesets -- score normalized to 0 Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Packaging ⚠️ -1 packaging workflow not detected Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions Binary-Artifacts 🟢 10 no binaries found in the repo Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Security-Policy ⚠️ 0 security policy file not detected License ⚠️ 0 license file not detected Fuzzing ⚠️ 0 project is not fuzzed Signed-Releases ⚠️ -1 no releases found Branch-Protection 🟢 3 branch protection is not maximal on development and all release branches SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0

Scanned Files

• api/package-lock.json

[Copilot]

Pull request overview

This PR updates the API’s local Azure Functions tooling by bumping azure-functions-core-tools from 4.12.1 to 4.14.0 in the /api workspace.

Changes:

• Bump azure-functions-core-tools devDependency to ^4.14.0.
• Regenerate api/package-lock.json to reflect the new version and its transitive dependency updates.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 2 comments.

File	Description
api/package.json	Updates the Azure Functions Core Tools devDependency version used for local function host runs.
api/package-lock.json	Updates resolved versions/metadata for azure-functions-core-tools@4.14.0 and related transitive dependencies.

Files not reviewed (1)

• api/package-lock.json: Generated file

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.