prime-simplereport icon indicating copy to clipboard operation
prime-simplereport copied to clipboard

Bump azure-functions-core-tools from 4.0.7317 to 4.3.0 in /ops/services/app_functions/report_stream_batched_publisher/functions

Open dependabot[bot] opened this issue 2 months ago • 1 comments

Bumps azure-functions-core-tools from 4.0.7317 to 4.3.0.

Release notes

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

4.3.0

Azure Functions CLI 4.3.0

Host Version

  • Host Version: 4.1042.100
  • In-Proc Host Version: 4.41.100 (4.841.100, 4.641.100)

Changes

  • Log the resolved worker runtime and local.settings.json location, if found. (#4628)
  • Add func pack basic functionality (#4600)
  • Clean up HelpAction and add func pack to help menu (#4639)
  • Add comprehensive pack validations for all Azure Functions runtimes (#4625)
    • Enhanced user experience with real-time validation status (PASSED/FAILED/WARNING)
    • Runtime-specific validations for .NET, Python, Node.js, PowerShell, and Custom Handlers
    • Actionable error messages to help developers resolve issues during packaging
    • Validates folder structure, required files, programming models, and runtime-specific configurations
  • Add support for linux-arm64 (#4655)

[!IMPORTANT] Please note that the APT release is still in-progress.

4.3.0-preview1

Azure Functions CLI 4.3.0-preview1

This release provides a preview build of Core Tools targeting the Linux-ARM64 architecture.

[!Note] Unless you're targeting Linux-ARM64, we recommend continuing to use the standard release for broader compatibility.

Key Information:

  • This build is intended to enable support for the Linux-ARM64 platform.
  • It does not include .NET applications using the in-process model
  • This release is only available on APT.

We appreciate your feedback as we continue to expand platform compatibility.

4.2.2

Azure Functions CLI 4.2.2

Host Version

  • Host Version: 4.1041.200
  • In-Proc Host Version: 4.41.100 (4.841.100, 4.641.100)

Changes

  • Fix .NET template install bug (#4612)

... (truncated)

Changelog

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

Azure Functions CLI 4.3.0

Host Version

  • Host Version: 4.1042.100
  • In-Proc Host Version: 4.41.100 (4.841.100, 4.641.100)

Changes

Commits
Maintainer changes

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


Dependabot compatibility score

You can trigger a rebase of this PR 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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

dependabot[bot] avatar Oct 05 '25 15:10 dependabot[bot]

Just realized that GitHub showed the dev5 deployment was active, but it looks like it actually ran into a failure so removing the approval and rerunning the deployment to test

mpbrown avatar Nov 04 '25 18:11 mpbrown