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 github/branch-deploy from 6.0.1 to 7.1.0 #368

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 31, 2023

Bumps github/branch-deploy from 6.0.1 to 7.1.0.

Release notes

Sourced from github/branch-deploy's releases.

v7.1.0

This release introduces a new input parameter for this Action:

  • deploy_message_path - The path to a markdown file which is used as a template for custom deployment messages

You can read more about this change under the dedicated documentation for custom deployment messages.

This release will give users of this Action even more flexibility to customize what their projects deployment messages look like! All this can now be done in our familiar friend, markdown and it also comes with nunjucks template rendering support 🚀.

What's Changed

Full Changelog: github/branch-deploy@v7.0.0...v7.1.0

v7.0.0

⚠️ Breaking Changes ⚠️

This new major release changes the way that "noop" style commands work. Starting with this release, the .deploy noop command will no longer work and it will be immediately replaced with .noop instead. The core reasoning for this, is so that .noop can become its own standalone command and no longer be a subset of the .deploy command. This will lead to less mistakes, user error, and higher flexibility when customizing this Action for future projects.

What do I need to do?

For most users, you don't need to do anything at all. Simply use .noop (the default) instead of .deploy noop. In fact, if you upgrade to v7.0.0 (this release) and run .deploy noop, you will be presented with a comment containing details about the command to use instead and a link to the deprecation docs

You can always customize the noop_trigger input option to be something else besides .noop (you could do .plan if you're doing Terraform things for example) but the "noop" trigger will never again be a subset of the primary deploy command.

Why was this change made?

Here are some suggested readings to learn more about why this change was made if you are curious to learn more:

What's Changed

Full Changelog: github/branch-deploy@v6.1.0...v7.0.0

v6.1.0

This release introduces a new input option from @​szymonpk's suggestion github/branch-deploy#163.

... (truncated)

Commits

Dependabot compatibility score

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 ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github/branch-deploy](https://github.com/github/branch-deploy) from 6.0.1 to 7.1.0.
- [Release notes](https://github.com/github/branch-deploy/releases)
- [Commits](github/branch-deploy@v6.0.1...v7.1.0)

---
updated-dependencies:
- dependency-name: github/branch-deploy
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot requested a review from a team as a code owner July 31, 2023 01:46
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jul 31, 2023
@github-actions
Copy link
Contributor

👋 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. 🚀 Branch deploy your pull request to production

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

  4. 🎉 Merge!

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Aug 7, 2023

Superseded by #372.

@dependabot dependabot bot closed this Aug 7, 2023
@dependabot dependabot bot deleted the dependabot/github_actions/github/branch-deploy-7.1.0 branch August 7, 2023 01:23
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.

None yet

0 participants