chore(deps): bump the github-action-dependencies group with 3 updates

[dependabot[bot]]

Bumps the github-action-dependencies group with 3 updates: actions/checkout, cycjimmy/semantic-release-action and slackapi/slack-github-action.

Updates actions/checkout from 3 to 4

Release notes

Sourced from actions/checkout's releases.

v4.0.0

What's Changed

• Update default runtime to node20 by @​takost in actions/checkout#1436
• Support fetching without the --progress option by @​simonbaird in actions/checkout#1067
• Release 4.0.0 by @​takost in actions/checkout#1447

New Contributors

• @​takost made their first contribution in actions/checkout#1436
• @​simonbaird made their first contribution in actions/checkout#1067

Full Changelog: https://github.com/actions/checkout/compare/v3...v4.0.0

v3.6.0

What's Changed

• Mark test scripts with Bash'isms to be run via Bash by @​dscho in actions/checkout#1377
• Add option to fetch tags even if fetch-depth > 0 by @​RobertWieczoreck in actions/checkout#579
• Release 3.6.0 by @​luketomlinson in actions/checkout#1437

New Contributors

• @​RobertWieczoreck made their first contribution in actions/checkout#579
• @​luketomlinson made their first contribution in actions/checkout#1437

Full Changelog: https://github.com/actions/checkout/compare/v3.5.3...v3.6.0

v3.5.3

What's Changed

• Fix: Checkout Issue in self hosted runner due to faulty submodule check-ins by @​megamanics in actions/checkout#1196
• Fix typos found by codespell by @​DimitriPapadopoulos in actions/checkout#1287
• Add support for sparse checkouts by @​dscho and @​dfdez in actions/checkout#1369
• Release v3.5.3 by @​TingluoHuang in actions/checkout#1376

New Contributors

• @​megamanics made their first contribution in actions/checkout#1196
• @​DimitriPapadopoulos made their first contribution in actions/checkout#1287
• @​dfdez made their first contribution in actions/checkout#1369

Full Changelog: https://github.com/actions/checkout/compare/v3...v3.5.3

v3.5.2

What's Changed

• Fix: Use correct API url / endpoint in GHES by @​fhammerl in actions/checkout#1289 based on #1286 by @​1newsr

Full Changelog: https://github.com/actions/checkout/compare/v3.5.1...v3.5.2

v3.5.1

What's Changed

• Improve checkout performance on Windows runners by upgrading @​actions/github dependency by @​BrettDong in actions/checkout#1246

New Contributors

• @​BrettDong made their first contribution in actions/checkout#1246

... (truncated)

Changelog

Sourced from actions/checkout's changelog.

Changelog

v4.0.0

• Support fetching without the --progress option
• Update to node20

v3.6.0

• Fix: Mark test scripts with Bash'isms to be run via Bash
• Add option to fetch tags even if fetch-depth > 0

v3.5.3

• Fix: Checkout fail in self-hosted runners when faulty submodule are checked-in
• Fix typos found by codespell
• Add support for sparse checkouts

v3.5.2

• Fix api endpoint for GHES

v3.5.1

• Fix slow checkout on Windows

v3.5.0

• Add new public key for known_hosts

v3.4.0

• Upgrade codeql actions to v2
• Upgrade dependencies
• Upgrade @​actions/io

v3.3.0

• Implement branch list using callbacks from exec function
• Add in explicit reference to private checkout options
• [Fix comment typos (that got added in #770)](actions/checkout#1057)

v3.2.0

• Add GitHub Action to perform release
• Fix status badge
• Replace datadog/squid with ubuntu/squid Docker image
• Wrap pipeline commands for submoduleForeach in quotes
• Update @​actions/io to 1.1.2
• Upgrading version to 3.2.0

v3.1.0

• Use @​actions/core saveState and getState
• Add github-server-url input

v3.0.2

• Add input set-safe-directory

v3.0.1

... (truncated)

Commits

• 3df4ab1 Release 4.0.0 (#1447)
• 8b5e8b7 Support fetching without the --progress option (#1067)
• 97a652b Update default runtime to node20 (#1436)
• See full diff in compare view

Updates cycjimmy/semantic-release-action from 3 to 4

Release notes

Sourced from cycjimmy/semantic-release-action's releases.

v4.0.0

4.0.0 (2023-08-31)

Features

• update node version on runner to 20 (0c20554)

BREAKING CHANGES

• set the default node version to 20

v3.4.2

3.4.2 (2023-03-30)

Bug Fixes

• fix installation error for npm-audit (86a0e59), closes #159

v3.4.1

3.4.1 (2023-03-30)

Bug Fixes

• windUpJob: set last_release outputs before returning (91e3dc6)

v3.4.0

3.4.0 (2023-03-15)

Features

• add ci input parameter (b356b18)

v3.3.0

... (truncated)

Changelog

Sourced from cycjimmy/semantic-release-action's changelog.

4.0.0 (2023-08-31)

Features

• update node version on runner to 20 (0c20554)

BREAKING CHANGES

• set the default node version to 20

3.4.2 (2023-03-30)

Bug Fixes

• fix installation error for npm-audit (86a0e59), closes #159

3.4.1 (2023-03-30)

Bug Fixes

• windUpJob: set last_release outputs before returning (91e3dc6)

3.4.0 (2023-03-15)

Features

• add ci input parameter (b356b18)

3.3.0 (2023-03-07)

Features

• support for option tagFormat (ed38eb0)

3.2.0 (2022-11-04)

Features

• added gitHead and gitTag outputs (385af4f)

3.1.2 (2022-10-19)

... (truncated)

Commits

• 61680d0 chore(release): 4.0.0 [skip ci]
• 31a37a4 Merge pull request #171 from enell/node20
• 81a6335 docs: modify docs for v4
• 3b12aa9 chore: upgrade deps
• 0c20554 feat: update node version on runner to 20
• 7f0c0e4 Merge pull request #165 from elebiodaslingshot/patch-1
• 4dd16d6 docs: fix example tag format with proper lodash
• See full diff in compare view

Updates slackapi/slack-github-action from 1.18.0 to 1.24.0

Release notes

Sourced from slackapi/slack-github-action's releases.

Slack Send V1.24.0

What's Changed

• Add in testing instructions for maintainer's guide and standardize bullet point punctuation by @​hello-ashleyintech in slackapi/slack-github-action#140
• Added checks for bot token and webhook url length by @​koki-develop in slackapi/slack-github-action#124
• Add channel_id output parameter by @​maso7 in slackapi/slack-github-action#149
• #171 Update Technique 2 to use Actions context instead of values property by @​mwbrooks in slackapi/slack-github-action#172
• Fix interpolation of variables in file-based payloads by @​filmaj in slackapi/slack-github-action#200
• Update README.md with variable usage and links to example workflows by @​filmaj in slackapi/slack-github-action#201

New Contributors

• @​koki-develop made their first contribution in slackapi/slack-github-action#124
• @​maso7 made their first contribution in slackapi/slack-github-action#149
• @​mwbrooks made their first contribution in slackapi/slack-github-action#172
• @​hnarimiya made their first contribution in slackapi/slack-github-action#200

Full Changelog: https://github.com/slackapi/slack-github-action/compare/v1.23.0...v1.24.0

Slack Send V1.23.0

What's Changed

• Bump node from 12 to 16 by @​quinnjn in slackapi/slack-github-action#128
• Bump eslint from 8.23.0 to 8.24.0 by @​dependabot in slackapi/slack-github-action#135
• Bump @​actions/core from 1.9.1 to 1.10.0 by @​dependabot in slackapi/slack-github-action#134
• Bump @​actions/github from 5.0.3 to 5.1.1 by @​dependabot in slackapi/slack-github-action#133
• Use https proxy agent by @​EHitchcockIAG in slackapi/slack-github-action#132
• Release v1.23.0 by @​hello-ashleyintech in slackapi/slack-github-action#139

New Contributors

• @​quinnjn made their first contribution in slackapi/slack-github-action#128
• @​EHitchcockIAG made their first contribution in slackapi/slack-github-action#132
• @​hello-ashleyintech made their first contribution in slackapi/slack-github-action#139

Full Changelog: https://github.com/slackapi/slack-github-action/compare/v1.22.0...v1.23.0

Slack Send V1.22.0

What's Changed

• feat(message): support multiple channel IDs by @​treemmett in slackapi/slack-github-action#126 (fixes #118)

New Contributors

• @​treemmett made their first contribution in slackapi/slack-github-action#126

Full Changelog: https://github.com/slackapi/slack-github-action/compare/v1.21.0...v1.22.0

Slack Send V1.21.0

What's Changed

• updated to 1.21.0, fixed update-ts by @​stevengill in slackapi/slack-github-action#110

Full Changelog: https://github.com/slackapi/slack-github-action/compare/v1.20.0...v1.21.0

... (truncated)

Commits

• e28cf16 Automatic compilation
• f07b4a2 bump package version to v1.24.0
• 2c8b741 Update README.md with variable usage and links to example workflows. (#201)
• 81a1dc0 Fixed to be able to use env of Step (#200)
• 4eb7313 Bump sinon from 15.0.3 to 15.0.4 (#194)
• 17394c7 Bump eslint-plugin-jsdoc from 40.1.1 to 43.1.1 (#195)
• 2746ea8 Bump axios from 1.3.4 to 1.4.0 (#196)
• 1b89efc Bump eslint from 8.37.0 to 8.39.0 (#197)
• 0e608ca Bump eslint-plugin-jsdoc from 40.0.0 to 40.1.1 (#188)
• 02b50ad Bump eslint from 8.35.0 to 8.37.0 (#189)
• Additional commits viewable in compare view

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 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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions

[github-actions[bot]]

Pull request title looks good 👍!

If this pull request gets merged, it will not cause a new release of the software. Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.0.0. This pull request is not a breaking change.

All merged pull requests will eventually get deployed. But some types of pull requests will trigger a deployment (such as features and bug fixes) while some pull requests will wait to get deployed until a later time.

This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...

This project uses a special format for pull requests titles. Don't worry, it's easy! This pull request title should be in this format: ``` : short description of change being made ``` **If your pull request [introduces breaking changes](https://web.archive.org/web/20220725195319/https://nordicapis.com/what-are-breaking-changes-and-how-do-you-avoid-them/)** to the code, use this format: ``` !: short description of breaking change ``` where `` is one of the following: - `feat:` - A feature is being added or modified by this pull request. Use this if you made any changes to any of the features of the project. - `fix:` - A bug is being fixed by this pull request. Use this if you made any fixes to bugs in the project. - `docs:` - This pull request is making documentation changes, only. - `refactor:` - A change was made that doesn't fix a bug or add a feature. - `test:` - Adds missing tests or fixes broken tests. - `style:` - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc) - `perf:` - Changes improve performance of the code. - `build:` - Changes to the build system (maven, npm, gulp, etc) - `ci:` - Changes to the CI build system (Travis, GitHub Actions, Circle, etc) - `chore:` - Other changes to project that don't modify source code or test files. - `revert:` - Reverts a previous commit that was made. ### Examples: ``` feat: edit profile photo refactor!: remove deprecated v1 endpoints build: update npm dependencies style: run formatter ``` Need more examples? Want to learn more about this format? [Check out the official docs](https://www.conventionalcommits.org/). **Note:** If your pull request does multiple things such as adding a feature _and_ makes changes to the CI server _and_ fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.

[github-actions[bot]]

Hey, there @dependabot[bot] 👋🤖. I'm a bot here to help you.

⚠️ Pull requests into the branch beta typically only allows changes with the types: fix. From the pull request title, the type of change this pull request is trying to complete is: chore. ⚠️

This pull request might still be allowed to be merged. However, you might want to consider make this pull request merge into a different branch other then beta.

This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...

This project uses a special format for pull requests titles. Don't worry, it's easy! This pull request title should be in this format: ``` : short description of change being made ``` **If your pull request [introduces breaking changes](https://web.archive.org/web/20220725195319/https://nordicapis.com/what-are-breaking-changes-and-how-do-you-avoid-them/)** to the code, use this format: ``` !: short description of breaking change ``` where `` is one of the following: - `feat:` - A feature is being added or modified by this pull request. Use this if you made any changes to any of the features of the project. - `fix:` - A bug is being fixed by this pull request. Use this if you made any fixes to bugs in the project. - `docs:` - This pull request is making documentation changes, only. - `refactor:` - A change was made that doesn't fix a bug or add a feature. - `test:` - Adds missing tests or fixes broken tests. - `style:` - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc) - `perf:` - Changes improve performance of the code. - `build:` - Changes to the build system (maven, npm, gulp, etc) - `ci:` - Changes to the CI build system (Travis, GitHub Actions, Circle, etc) - `chore:` - Other changes to project that don't modify source code or test files. - `revert:` - Reverts a previous commit that was made. ### Examples: ``` feat: edit profile photo refactor!: remove deprecated v1 endpoints build: update npm dependencies style: run formatter ``` Need more examples? Want to learn more about this format? [Check out the official docs](https://www.conventionalcommits.org/). **Note:** If your pull request does multiple things such as adding a feature _and_ makes changes to the CI server _and_ fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.