Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump the github-actions group with 4 updates #278

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 1, 2024

Bumps the github-actions group with 4 updates: github/branch-deploy, actions/setup-node, GrantBirki/json-yaml-validate and GrantBirki/comment.

Updates github/branch-deploy from 8.2.1 to 9.1.0

Release notes

Sourced from github/branch-deploy's releases.

v9.1.0

Overview

This release introduces a new input option called checks (thanks to @​Ugzuzg! 🎉). The checks feature has been a long sought after feature of this Action to give teams better control over what CI checks have to be passing in order for a deployment to proceed. This feature was originally requested way back in 2022 and it has finally landed!

The detailed documentation around the checks input can be found here.

TL;DR: A new input option called checks allows for teams to choose whether they want all CI checks to pass before a deployment can proceed or if only the explicitly required CI checks need to be passing.

What's Changed

New Contributors

Full Changelog: github/branch-deploy@v9...v9.1.0

v9.0.0

What's Changed


⚠️ potentially breaking change! ⚠️

The vast majority of teams should be able to upgrade to v9.0.0 without any issues

It should be noted that this change is only "breaking" in the sense that unexpected behavior may take place for teams using more unique git flows for development. If you want to maintain the current state of this Action on v9.0.0 and beyond, all you need to do is to simply set outdated_mode: "pr_base" in the Action configuration. Most teams using this Action will not notice any issues upgrading to v9.x.x.


This release introduces a new input option (outdated_mode) for fine grain control over deployments when a branch is deemed "out-of-date" 🎉. These changes were introduced in github/branch-deploy#237 and the aforementioned pull request contains a lot of information around these changes. You can also view the detailed documentation around this new input option to learn more and how you and your team can use it. Enjoy!

Full Changelog: github/branch-deploy@v8...v9.0.0


Huge thank you to @​jessew-albert for helping out with the features in this release! 🙇

Commits
  • ad494b2 Merge pull request #244 from github/checks-input-docs
  • 243c05c bundle
  • 6954700 update help message
  • 6e34ae2 add checks documentation
  • 8d27c4e Merge branch 'main' into checks-input-docs
  • 903ca23 add a link to the docs
  • c540455 update checks input description to be more detailed
  • 677cced Merge pull request #243 from github/node-updates
  • f427ac4 node-updates
  • 8facfd3 Merge pull request #242 from github/dependabot/npm_and_yarn/undici-5.28.3
  • Additional commits viewable in compare view

Updates actions/setup-node from 4.0.1 to 4.0.2

Release notes

Sourced from actions/setup-node's releases.

v4.0.2

What's Changed

New Contributors

Full Changelog: actions/setup-node@v4.0.1...v4.0.2

Commits

Updates GrantBirki/json-yaml-validate from 2.6.0 to 2.6.1

Release notes

Sourced from GrantBirki/json-yaml-validate's releases.

v2.6.1

What's Changed

Internal node dependency updates and CI updates

Full Changelog: GrantBirki/json-yaml-validate@v2.6.0...v2.6.1

Commits

Updates GrantBirki/comment from 2.0.8 to 2.0.9

Release notes

Sourced from GrantBirki/comment's releases.

v2.0.9

What's Changed

Only internal node dependency updates in this release!

Full Changelog: GrantBirki/comment@v2.0.8...v2.0.9

Commits
  • d5cdf02 Merge pull request #21 from GrantBirki/general-updates
  • 5689d4b move workflow dir
  • 85af987 add .github/workflows/update-latest-release-tag.yml workflow
  • 2dbc76a update lint job
  • 25e5203 update all node packages with npm update
  • 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 <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

Bumps the github-actions group with 4 updates: [github/branch-deploy](https://github.com/github/branch-deploy), [actions/setup-node](https://github.com/actions/setup-node), [GrantBirki/json-yaml-validate](https://github.com/grantbirki/json-yaml-validate) and [GrantBirki/comment](https://github.com/grantbirki/comment).


Updates `github/branch-deploy` from 8.2.1 to 9.1.0
- [Release notes](https://github.com/github/branch-deploy/releases)
- [Commits](github/branch-deploy@v8.2.1...v9.1.0)

Updates `actions/setup-node` from 4.0.1 to 4.0.2
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v4.0.1...v4.0.2)

Updates `GrantBirki/json-yaml-validate` from 2.6.0 to 2.6.1
- [Release notes](https://github.com/grantbirki/json-yaml-validate/releases)
- [Commits](GrantBirki/json-yaml-validate@v2.6.0...v2.6.1)

Updates `GrantBirki/comment` from 2.0.8 to 2.0.9
- [Release notes](https://github.com/grantbirki/comment/releases)
- [Commits](GrantBirki/comment@7016e89...d5cdf02)

---
updated-dependencies:
- dependency-name: github/branch-deploy
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions
- dependency-name: actions/setup-node
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: GrantBirki/json-yaml-validate
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: GrantBirki/comment
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from a team as a code owner March 1, 2024 02:11
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Mar 1, 2024
Copy link
Contributor

github-actions bot commented Mar 1, 2024

👋 Thanks for opening a pull request!

If you are new, please check out the deployment process below to understand how to deploy this pull request:

  1. 👀 Observe the CI output on this pull request to ensure it is passing and doing what it is supposed to do

  2. ✔️ Obtain an approval/review on this pull request

  3. 🚀 Branch deploy your pull request to production with .deploy

    Comment .deploy on this pull request to trigger a deploy. If anything goes wrong, rollback with .deploy main

  4. 🎉 Merge!

If you need additional help with branch deployments, checkout the usage guide

@Razzmatazzz
Copy link
Member

.deploy

Copy link
Contributor

github-actions bot commented Mar 1, 2024

Deployment Triggered 🚀

Razzmatazzz, started a branch deployment to production

You can watch the progress here 🔗

Branch: dependabot/github_actions/github-actions-1a0b66f0d6

Copy link
Contributor

github-actions bot commented Mar 1, 2024

Deployment Results ✅

Razzmatazzz successfully deployed branch dependabot/github_actions/github-actions-1a0b66f0d6 to production

@Razzmatazzz Razzmatazzz merged commit 7273a82 into main Mar 1, 2024
2 checks passed
@Razzmatazzz Razzmatazzz deleted the dependabot/github_actions/github-actions-1a0b66f0d6 branch March 1, 2024 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant