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

Bump the github-actions group across 1 directory with 2 updates #342

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

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

Bumps the github-actions group with 2 updates in the / directory: github/branch-deploy and cloudflare/wrangler-action.

Updates github/branch-deploy from 9.7.0 to 9.9.1

Release notes

Sourced from github/branch-deploy's releases.

v9.9.1

What's Changed

Full Changelog: github/branch-deploy@v9.9.0...v9.9.1

v9.9.0

What's Changed

New Contributors

Full Changelog: github/branch-deploy@v9.8.1...v9.9.0

v9.8.1

What's Changed

A follow-up to the v9.8.0 release to implement GraphQL pagination to make "latest deployment checks" more robust when using enforced deployment order.

Full Changelog: github/branch-deploy@v9.8.0...v9.8.1

v9.8.0

Enforced Deployment Order 🚀

Introducing a long requested feature, enforced deployment order...

Summary

This pull request does the following:

  • adds a new enforced_deployment_order input option that can be used to require deployments to take place "in order" and for each to pass before the next one can be triggered
  • adds a new needs_to_be_deployed output that maps to the environments that require successful deployments if a deployment attempt is rejected

Detailed

This feature is one that has been requested by folks internally and externally to GitHub for a long time (over a year). This pull request makes it so that users can now control the order in which deployments are made (if they choose to do so).

This feature is optional and can be enabled by setting, enforced_deployment_order: <env1>,<env2>,<env3>. The value for enforced_deployment_order is a string that is read from left->right with each value separated by commas. Each value in this comma separated list is an environment that you wish to use in an "enforced deployment order". Here is an example:

- uses: github/[email protected]
  id: branch-deploy
</tr></table> 

... (truncated)

Commits
  • e9ac229 Merge pull request #315 from github/commit-time-checks
  • 9bfda32 add unit tests
  • 1c17604 test coverage for main.js
  • fe201cd raise getCommit out of the helper method and into main in case it needs t...
  • 683275b implement extra commit safety checks
  • b2ee3bb vendor an example of ${JSON.stringify(context)}
  • 9e8e68f add context debug logs
  • 535e75d Merge pull request #314 from github/npm-updates
  • b980485 update all node deps with npm update
  • 3897071 Merge pull request #309 from github/dependabot/npm_and_yarn/npm-dependencies-...
  • Additional commits viewable in compare view

Updates cloudflare/wrangler-action from 3.7.0 to 3.11.0

Release notes

Sourced from cloudflare/wrangler-action's releases.

v3.11.0

Minor Changes

v3.10.0

Minor Changes

v3.9.0

Minor Changes

Patch Changes

v3.8.0

Minor Changes

Changelog

Sourced from cloudflare/wrangler-action's changelog.

Changelog

3.11.0

Minor Changes

3.10.0

Minor Changes

3.9.0

Minor Changes

Patch Changes

3.8.0

Minor Changes

3.7.0

Minor Changes

3.6.1

Patch Changes

3.6.0

Minor Changes

3.5.0

... (truncated)

Commits
  • b2a0191 Automatic compilation
  • b2be7ab Merge pull request #310 from cloudflare/changeset-release/main
  • b7158dc Version Packages
  • 43767e7 Merge pull request #309 from cloudflare/maximo/revert-add-parity-with-pages-a...
  • 10d5b9c Revert "Add parity with pages-action for pages deploy outputs"
  • c010357 Merge pull request #305 from cloudflare/changeset-release/main
  • fa96c39 Version Packages
  • 78dad1d Merge pull request #303 from cloudflare/courtney-sims-enable-outputs
  • 3ec7f89 Add parity with pages-action for pages deploy outputs
  • cd8a317 Merge pull request #299 from cloudflare/changeset-release/main
  • 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 <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 2 updates in the / directory: [github/branch-deploy](https://github.com/github/branch-deploy) and [cloudflare/wrangler-action](https://github.com/cloudflare/wrangler-action).


Updates `github/branch-deploy` from 9.7.0 to 9.9.1
- [Release notes](https://github.com/github/branch-deploy/releases)
- [Commits](github/branch-deploy@v9.7.0...v9.9.1)

Updates `cloudflare/wrangler-action` from 3.7.0 to 3.11.0
- [Release notes](https://github.com/cloudflare/wrangler-action/releases)
- [Changelog](https://github.com/cloudflare/wrangler-action/blob/main/CHANGELOG.md)
- [Commits](cloudflare/wrangler-action@f84a562...b2a0191)

---
updated-dependencies:
- dependency-name: github/branch-deploy
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: cloudflare/wrangler-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
...

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

github-actions bot commented Nov 1, 2024

👋 Thanks for opening a pull request!

If you are new, please check out the trimmed down summary of our deployment process below:

  1. 👀 Observe the CI jobs and tests to ensure they are passing

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

  3. 🚀 Deploy your pull request to the development environment with .deploy to development

  4. 🚀 Deploy your pull request to the production environment with .deploy

    If anything goes wrong, rollback with .deploy main

  5. 🎉 Merge!

Need help? Type .help as a comment or visit the usage guide for more details

Please note, if you have a more complex change, it is advised to claim a deployment lock with .lock <environment> --reason <reason> to prevent other deployments from happening while you are working on your change.

Once your PR has been merged, you can remove the lock with .unlock <environment>.

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.

0 participants