customerio / customerio-reactnative

MIT License
23 stars 11 forks source link

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

Closed dependabot[bot] closed 11 months ago

dependabot[bot] commented 11 months ago

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

Updates actions/checkout from 2 to 4

Release notes

Sourced from actions/checkout's releases.

v4.0.0

What's Changed

New Contributors

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

v3.6.0

What's Changed

New Contributors

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

v3.5.3

What's Changed

New Contributors

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

v3.5.2

What's Changed

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

v3.5.1

What's Changed

New Contributors

... (truncated)

Changelog

Sourced from actions/checkout's changelog.

Changelog

v4.0.0

v3.6.0

v3.5.3

v3.5.2

v3.5.1

v3.5.0

v3.4.0

v3.3.0

v3.2.0

v3.1.0

v3.0.2

v3.0.1

... (truncated)

Commits


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

New Contributors

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

Slack Send V1.23.0

What's Changed

New Contributors

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

Slack Send V1.22.0

What's Changed

New Contributors

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

Slack Send V1.21.0

What's Changed

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

... (truncated)

Commits


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

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

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


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] commented 11 months ago

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.