Sourced fromfluxcd/flux2's releases.

v2.4.0

Highlights

Flux v2.4.0 is a feature release. Users are encouraged to upgrade for the best experience.

For a comprehensive overview of new features and API changes included in this release, please refer to theAnnouncing Flux 2.4 GA blog post.

This release marks the General Availability (GA) of Flux Bucket API. TheBucket v1 API comes with new features including: proxy support, mTLS and custom STS configuration for AWS S3 and MinIO LDAP authentication.

TheGitRepository v1 API gains support for OIDC authentication. Starting with this version, you can authenticate against Azure DevOps repositories using AKS Workload Identity.

TheOCIRepository v1beta2 API gains support for proxy configuration thus allowing dedicated HTTP/S Proxy authentication on multi-tenant Kubernetes clusters.

TheHelmRelease v2 API gains support for disabling JSON schema validation of the Helm release values during installation and upgrade. And allows adopting existing Kubernetes resources during Helm release installation.

The Flux controllers are now built with Go 1.23 and their dependencies have been updated to Kubernetes 1.31, Helm 3.16, SOPS 3.9 Cosign 2.4 and Notation 1.2.

❤️ Big thanks to all the Flux contributors that helped us with this release!

Kubernetes compatibility

This release is compatible with the following Kubernetes versions:

Kubernetes version	Minimum required
v1.29	>= 1.29.0
v1.30	>= 1.30.0
v1.31	>= 1.31.0

[!NOTE]Note that the Flux project offers support only for the latest three minor versions of Kubernetes.Backwards compatibility with older versions of Kubernetes and OpenShift is offered by vendors such asControlPlane that provide enterprise support for Flux.

OpenShift compatibility

Flux can be installed on Red Hat OpenShift cluster directly from OperatorHub usingFlux Operator.The operator allows the configuration of Flux multi-tenancy lockdown, network policies, persistent storage, sharding, vertical scaling and the synchronization of the cluster state from Git repositories, OCI artifacts and S3-compatible storage.

API changes

Bucket v1

TheBucket kind was promoted from v1beta2 to v1 (GA).

The v1 API is backwards compatible with v1beta2.

New fields:

• .spec.proxySecretRef allows configuring HTTP/S Proxy authentication for the S3-compatible storage service.

... (truncated)

• 5350425 Merge pull request#5014 from fluxcd/k8s-v0.31.1
• 6611a4f Update Kubernetes dependencies to v1.31.1
• 297b15b Merge pull request#5005 from fluxcd/update-components
• 56a3d08 Update toolkit components
• cf26cf2 Merge pull request#5011 from fluxcd/remove-deprecated-tls-flags
• a3dbf31 Remove TLS deprecated flags fromflux create secret
• 3e4524b Merge pull request#5010 from fluxcd/create-secret-proxy
• 8470f23 Addflux create secret proxy command
• e17f3f0 Merge pull request#5009 from fluxcd/proxy-secret-ref
• e0b8464 Add--proxy-secret-ref toflux create source commands
• Additional commits viewable incompare view

Sourced fromgithub/codeql-action's changelog.

CodeQL Action Changelog

See thereleases page for the relevant changes to the CodeQL CLI and language packs.

Note that the only difference betweenv2 andv3 of the CodeQL Action is the node version they support, withv3 running on node 20 while we continue to releasev2 to support running on node 16. For example3.22.11 was the firstv3 release and is functionally identical to2.22.11. This approach ensures an easy way to track exactly which features are included in different versions, indicated by the minor and patch version numbers.

[UNRELEASED]

• Bump the minimum CodeQL bundle version to 2.14.6.#2549

3.26.13 - 14 Oct 2024

No user facing changes.

3.26.12 - 07 Oct 2024

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.14.5 and earlier. These versions of CodeQL were discontinued on 24 September 2024 alongside GitHub Enterprise Server 3.10, and will be unsupported by CodeQL Action versions 3.27.0 and later and versions 2.27.0 and later.#2520

  • If you are using one of these versions, please update to CodeQL CLI version 2.14.6 or later. For instance, if you have specified a custom version of the CLI using the 'tools' input to the 'init' Action, you can remove this input to use the default version.

  • Alternatively, if you want to continue using a version of the CodeQL CLI between 2.13.5 and 2.14.5, you can replacegithub/codeql-action/*@v3 bygithub/codeql-action/*@v3.26.11 andgithub/codeql-action/*@v2 bygithub/codeql-action/*@v2.26.11 in your code scanning workflow to ensure you continue using this version of the CodeQL Action.

3.26.11 - 03 Oct 2024

• Upcoming breaking change: Add support for usingactions/download-artifact@v4 to programmatically consume CodeQL Action debug artifacts.

  Starting November 30, 2024, GitHub.com customers willno longer be able to useactions/download-artifact@v3. Therefore, to avoid breakage, customers who programmatically download the CodeQL Action debug artifacts should set theCODEQL_ACTION_ARTIFACT_V4_UPGRADE environment variable totrue and bumpactions/download-artifact@v3 toactions/download-artifact@v4 in their workflows. The CodeQL Action will enable this behavior by default in early November and workflows that have not yet bumped toactions/download-artifact@v3 toactions/download-artifact@v4 will begin failing then.

  This change is currently unavailable for GitHub Enterprise Server customers, asactions/upload-artifact@v4 andactions/download-artifact@v4 are not yet compatible with GHES.

• Update default CodeQL bundle version to 2.19.1.#2519

3.26.10 - 30 Sep 2024

• We are rolling out a feature in September/October 2024 that sets up CodeQL using a bundle compressed withZstandard. Our aim is to improve the performance of setting up CodeQL.#2502

3.26.9 - 24 Sep 2024

No user facing changes.

3.26.8 - 19 Sep 2024

• Update default CodeQL bundle version to 2.19.0.#2483

3.26.7 - 13 Sep 2024

• Update default CodeQL bundle version to 2.18.4.#2471

3.26.6 - 29 Aug 2024

• Update default CodeQL bundle version to 2.18.3.#2449

... (truncated)

• f779452 Merge pull request#2539 from github/update-v3.26.13-0c3e00641
• 5329324 Update CHANGELOG.md
• 007ba25 Update changelog for v3.26.13
• 0c3e006 Merge pull request#2536 from yoff/python/ff-std-lib-extraction
• 38469af Merge pull request#2537 from github/henrymercer/no-zstd-windows
• 5b6984e Assert that Windows downloads gzip
• eefb943 Don't use Zstandard bundles on Windows
• 201e02e rebuild the action
• ce5f900 formatting
• 65dd816 remove unused import
• Additional commits viewable incompare view

Sourced fromaquasecurity/trivy-action's releases.

v0.28.0

What's Changed

• chore(deps): bump setup-trivy to v0.2.1 by@​DmitriyLewen inaquasecurity/trivy-action#411

Full Changelog:aquasecurity/trivy-action@0.27.0...0.28.0

• 915b19b chore(deps): bump setup-trivy to v0.2.1 (#411)
• See full diff incompare view

Sourced fromPaloAltoNetworks/prisma-cloud-scan's releases.

v1.6.7

What's Changed

• Added publish flag to avoid publishing the results to the Prisma Console by@​raoganeshr inPaloAltoNetworks/prisma-cloud-scan#60

New Contributors

• @​raoganeshr made their first contribution inPaloAltoNetworks/prisma-cloud-scan#60

Full Changelog:PaloAltoNetworks/prisma-cloud-scan@v1.6.6...v1.6.7

v1.6.6

Changes

• No changes

Contributors

No contributors

What's Changed

• Support 'unassigned' severity level by@​mikocot inPaloAltoNetworks/prisma-cloud-scan#56
• Feat/add twistcli debug flag by@​mgappa inPaloAltoNetworks/prisma-cloud-scan#58

New Contributors

• @​mgappa made their first contribution inPaloAltoNetworks/prisma-cloud-scan#58

Full Changelog:PaloAltoNetworks/prisma-cloud-scan@v1.6.5...v1.6.6

v1.6.5

What's Changed

• add support for unreviewed sev by@​sgordon46 inPaloAltoNetworks/prisma-cloud-scan#53
• Node20 support by@​mikocot inPaloAltoNetworks/prisma-cloud-scan#50

Full Changelog:PaloAltoNetworks/prisma-cloud-scan@v1.6.4...v1.6.5

v1.6.4

What's Changed

• Port changes from npm install and add the negligible severity by@​sgordon46 inPaloAltoNetworks/prisma-cloud-scan#48

Full Changelog:PaloAltoNetworks/prisma-cloud-scan@v1.6.3...v1.6.4

v1.6.3

What's Changed

• Fix vulnerability duplicate filtering by@​ferozsalam inPaloAltoNetworks/prisma-cloud-scan#46

New Contributors

• @​ferozsalam made their first contribution inPaloAltoNetworks/prisma-cloud-scan#46

Full Changelog:PaloAltoNetworks/prisma-cloud-scan@v1.6.2...v1.6.3

v1.6.2

... (truncated)

• 124b48d Merge pull request#60 from raoganeshr/main
• 9ae6a30 Delete .github/workflows/run-scan.yaml
• 340c9c2 Update run-scan.yaml
• da09cbd Update run-scan.yaml
• bc8f89e Fixed publish step
• fd5fbdc Compile
• af9de12 Removed unwanted console message
• 7ca86b1 Added dist
• d72c5f9 Removed unwanted logs
• 1ac8e1d Added logging
• Additional commits viewable incompare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions