chore(deps): update all non-major github action dependencies

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/cache	action	minor	v3.3.3 -> v3.4.0
actions/checkout	action	minor	v2 -> v2.7.0
actions/checkout	action	minor	v3 -> v3.6.0
actions/setup-node	action	minor	v2 -> v2.5.2

Review

• Updates have been tested and work
• If updates are AWS related, versions match the infrastructure (e.g. Lambda runtime, database, etc.)

---

Release Notes

actions/cache (actions/cache)

v3.4.0

Compare Source

⚠️ Important Changes

The cache backend service has been rewritten from the ground up for improved performance and reliability. actions/cache now integrates with the new cache service (v2) APIs.

The new service will gradually roll out as of February 1st, 2025. The legacy service will also be sunset on the same date. Changes in these release are fully backward compatible.

We are deprecating some versions of this action. We recommend upgrading to version v4 or v3 as soon as possible before February 1st, 2025. (Upgrade instructions below).

If you are using pinned SHAs, please use the SHAs of versions v4.2.0 or v3.4.0

If you do not upgrade, all workflow runs using any of the deprecated actions/cache will fail.

Upgrading to the recommended versions will not break your workflows.

Read more about the change & access the migration guide: reference to the announcement.

Minor changes

Minor and patch version updates for these dependencies:

• @​actions/core: 1.11.1
• @​actions/io: 1.1.3
• @​vercel/ncc: 0.38.3

Full Changelog: actions/cache@v3...v3.4.0

actions/checkout (actions/checkout)

v2.7.0

Compare Source

What's Changed

• Add new public key for known_hosts (#​1237) by @​TingluoHuang in https://github.com/actions/checkout/pull/1238

Full Changelog: actions/checkout@v2.6.0...v2.7.0

v2.6.0

Compare Source

What's Changed

• Add backports to v2 branch by @​cory-miller in https://github.com/actions/checkout/pull/1040
  • Includes backports from the following changes: https://github.com/actions/checkout/pull/964, https://github.com/actions/checkout/pull/1002, https://github.com/actions/checkout/pull/1029
  • Upgraded the licensed version to match what is used in v3.

Full Changelog: actions/checkout@v2.5.0...v2.6.0

v2.5.0

Compare Source

What's Changed

• Update @​actions/core to 1.10.0 by @​rentziass in https://github.com/actions/checkout/pull/962

Full Changelog: actions/checkout@v2...v2.5.0

v2.4.2

Compare Source

What's Changed

• Add set-safe-directory input to allow customers to take control. (#​770) by @​TingluoHuang in https://github.com/actions/checkout/pull/776
• Prepare changelog for v2.4.2. by @​TingluoHuang in https://github.com/actions/checkout/pull/778

Full Changelog: actions/checkout@v2...v2.4.2

v2.4.1

Compare Source

• Fixed an issue where checkout failed to run in container jobs due to the new git setting safe.directory

v2.4.0

Compare Source

• Convert SSH URLs like org-<ORG_ID>@&#8203;github.com: to https://github.com/ - pr

v2.3.5

Compare Source

Update dependencies

v2.3.4

Compare Source

• Add missing awaits
• Swap to Environment Files

v2.3.3

Compare Source

• Remove Unneeded commit information from build logs
• Add Licensed to verify third party dependencies

v2.3.2

Compare Source

Add Third Party License Information to Dist Files

v2.3.1

Compare Source

• Fix default branch resolution for .wiki and when using SSH

v2.3.0

Compare Source

• Fallback to the default branch

v2.2.0

Compare Source

• Fetch all history for all tags and branches when fetch-depth=0

v2.1.1

Compare Source

• Changes to support GHES (here and here)

v2.1.0

Compare Source

• Group output
• Changes to support GHES alpha release
• Persist core.sshCommand for submodules
• Add support ssh
• Convert submodule SSH URL to HTTPS, when not using SSH
• Add submodule support
• Follow proxy settings
• Fix ref for pr closed event when a pr is merged
• Fix issue checking detached when git less than 2.22

actions/setup-node (actions/setup-node)

v2.5.2: Update @​actions/core for v2

Compare Source

In scope of this release we updated actions/core to 1.10.0 and actions/tool-cache to 1.7.2 for v2: https://github.com/actions/setup-node/pull/713

v2.5.1: Fix logic of error handling for npm warning and uncaught exception

Compare Source

In scope of this release we fix logic of error handling related to caching (https://github.com/actions/setup-node/pull/358) and (https://github.com/actions/setup-node/pull/359).

In the previous behaviour we relied on stderr output to throw error. The warning messages from package managers can be written to the stderr's output. For now the action will throw an error only if exit code differs from zero. Besides, we add logic to сatch and log unhandled exceptions.

v2.5.0: Adding Node.js version file support

Compare Source

In scope of this release we add the node-version-file input and update actions/cache dependency to the latest version.

Adding Node.js version file support

The new input (node-version-file) provides functionality to specify the path to the file containing Node.js's version with such behaviour:

• If the file does not exist the action will throw an error.
• If you specify both node-version and node-version-file inputs, the action will use value from the node-version input and throw the following warning: Both node-version and node-version-file inputs are specified, only node-version will be used.
• For now the action does not support all of the variety of values for Node.js version files. The action can handle values according to the documentation and values with v prefix (v14)

steps:
  - uses: actions/checkout@v2
  - name: Setup node from node version file
    uses: actions/setup-node@v2
    with:
      node-version-file: '.nvmrc'
  - run: npm install
  - run: npm test

Update actions/cache dependency to 1.0.8 version.

We updated actions/cache dependency to the latest version (1.0.8). For more information please refer to the toolkit/cache.

v2.4.1: Add "cache-hit" output

Compare Source

This release introduces a new output: cache-hit (#​327).

The cache-hit output contains boolean value indicating that an exact match was found for the key. It shows that the action uses already existing cache or not. The output is available only if cache is enabled.

v2.4.0: Support caching for mono repos and repositories with complex structure

Compare Source

This release introduces dependency caching support for mono repos and repositories with complex structure (#​305).

By default, the action searches for the dependency file (package-lock.json or yarn.lock) in the repository root. Use the cache-dependency-path input for cases when multiple dependency files are used, or they are located in different subdirectories. This input supports wildcards or a list of file names for caching multiple dependencies.

Yaml example:

steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
  with:
    node-version: 14
    cache: npm
    cache-dependency-path: 'sub-project/package-lock.json'

For more examples of using cache-dependency-path input, see the Advanced usage guide.

v2.3.2: Revert temporary fix

Compare Source

We had to disable pre-cached Node.js usage in the previous version due to the broken image cache. Now cache is fixed, so we can safely enable its usage again.
Thank you for understanding.

v2.3.1: Temporary maintenance fix.

Compare Source

Temporarily disabled usage of pre-cached Node.js.

v2.3.0: Support caching pnpm dependencies

Compare Source

This release introduces dependency caching support for the pnpm package manager (#​278).

Caching pnpm dependencies:

### This workflow uses actions that are not certified by GitHub.
### They are provided by a third-party and are governed by

### separate terms of service, privacy policy, and support
### documentation.

steps:
- uses: actions/checkout@v2
- uses: pnpm/action-setup@646cdf48217256a3d0b80361c5a50727664284f2
  with:
    version: 6.10.0
- uses: actions/setup-node@v2
  with:
    node-version: '14'
    cache: 'pnpm'
- run: pnpm install
- run: pnpm test

NOTE: pnpm caching support requires pnpm version >= 6.10.0

v2.2.0: Support caching dependencies and LTS aliases

Compare Source

This release brings two major features:

• Support LTS aliases #​270
• Implementation of node's caching #​272

Supported version syntax

The node-version input supports the following syntax:

major versions: 12, 14, 16
more specific versions: 10.15, 14.2.0, 16.3.0
nvm LTS syntax: lts/erbium, lts/fermium, lts/*

Caching dependencies

The action has a built-in functionality for caching and restoring npm/yarn dependencies. Supported package managers are npm, yarn. The cache input is optional, and caching is turned off by default.

Caching npm dependencies:

steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
  with:
    node-version: '14'
    cache: 'npm'
- run: npm install
- run: npm test

Caching yarn dependencies:

steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
  with:
    node-version: '14'
    cache: 'yarn'
- run: yarn install
- run: yarn test

Yarn caching handles both yarn versions: 1 or 2.

At the moment, only lock files in the project root are supported.

v2.1.5: Release

Compare Source

Improve error and warning line number handling (problem matcher regex)

v2.1.4

Compare Source

The first stable release of actions/setup-node V2

v2.1.3: (beta)

Compare Source

• Add support for specifying architecture of Node.JS

v2.1.2: (beta)

Compare Source

• Updated communication with runner to use environment files rather then workflow commands

v2.1.1: (beta)

Compare Source

Switch to main branch of node-versions repository to consume latest added versions.

v2.1.0: (beta)

Compare Source

Added check-latest input option to query the versions manifest for latest version before checking for semver match in local VM cache first (the default). That's useful for ensuring you get latest as soon as it's released to the cache but at the cost of perf / reliability (much more likely to incur and download and extract).

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone America/Montreal, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

xray-daemon	xray     	9       	2024-12-13 17:06:10.773232864 +0000 UTC	deployed	aws-xray-4.0.8	3.3.12     

ingress	nginx    	10      	2024-12-13 17:06:11.234752912 +0000 UTC	deployed	nginx-ingress-1.1.2	3.4.2      

Comparing release=notify-documentation, chart=charts/notify-documentation
Comparing release=notify-api, chart=charts/notify-api
Comparing release=notify-admin, chart=charts/notify-admin
Comparing release=notify-document-download, chart=charts/notify-document-download
Comparing release=notify-celery, chart=charts/notify-celery
Comparing release=k8s-event-logger, chart=/tmp/helmfile3415108713/amazon-cloudwatch/staging/k8s-event-logger/k8s-event-logger/1.1.8/k8s-event-logger
Comparing release=karpenter-crd, chart=/tmp/helmfile3415108713/karpenter/staging/karpenter-crd/karpenter-crd/0.36.1/karpenter-crd
Comparing release=karpenter, chart=/tmp/helmfile3415108713/karpenter/staging/karpenter/karpenter/0.36.1/karpenter
Comparing release=karpenter-nodepool, chart=charts/karpenter-nodepool
Comparing release=priority-classes, chart=deliveryhero/priority-class
Comparing release=secrets-store-csi-driver, chart=secrets-store-csi-driver/secrets-store-csi-driver
Comparing release=aws-secrets-provider, chart=aws-secrets-manager/secrets-store-csi-driver-provider-aws
Comparing release=kube-state-metrics, chart=prometheus-community/kube-state-metrics
Comparing release=blazer, chart=stakater/application
Comparing release=ingress, chart=charts/nginx-ingress
Comparing release=xray-daemon, chart=okgolove/aws-xray