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.

Sign up for GitHub

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

Jump to bottom

Update github/branch-deploy action to v10 #1323

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

Update github/branch-deploy action to v10 #1323

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 18, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
github/branch-deploy action major v9.10.0 -> v10.4.1

Release Notes

github/branch-deploy (github/branch-deploy)

v10.4.1

Compare Source

What's Changed

Full Changelog: github/branch-deploy@v10...v10.4.1

v10.4.0

Compare Source

What's Changed

This release introduces a new feature/input called deployment_confirmation. This option is rooted in security/safety that gives deployers one last "safety check" to approve/deny a deployment before it starts. See the full documentation about this feature to learn more. Original issue: https://github.com/github/branch-deploy/issues/373

Full Changelog: github/branch-deploy@v10.3.1...v10.4.0

v10.3.1

Compare Source

What's Changed

Full Changelog: github/branch-deploy@v10.3.0...v10.3.1

v10.3.0

Compare Source

What's Changed

Full Changelog: github/branch-deploy@v10.2.0...v10.3.0

v10.2.0

Compare Source

What's Changed

Full Changelog: github/branch-deploy@v10.1.0...v10.2.0

v10.1.0

Compare Source

What's Changed

This release adds new attributes to the payload which gets sent to GitHub's deployment API. These attributes can be used by subsequent systems that might read, parse, or interact with the deployments that this Action creates.

For nearly all users (including users that interact with the payload attribute), this new version should be a seamless upgrade. Enjoy!

Full Changelog: github/branch-deploy@v10.0.2...v10.1.0

v10.0.2

Compare Source

What's Changed

No major changes with this release, just dependency updates 📦

Full Changelog: github/branch-deploy@v10.0.1...v10.0.2

v10.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: github/branch-deploy@v10...v10.0.1

v10.0.0

Compare Source

v10.0.0

v10 of the github/branch-deploy Action is focused around safety, security, and usability improvements 🚀

BREAKING

Please note that even though there are breaking changes listed, the vast majority of users should be able to simply upgrade to github/branch-deploy@v10 without any issues

  • The checks input option can now be used with a comma separated list of CI checks if you only want certain checks to be considered "blocking" in terms of deployments. Read more here.
  • Pull requests in the CHANGES_REQUESTED state are now treated the same as PRs in the REVIEW_REQUIRED state.
  • The structure and content of the pre/post deployment messages (that get written to PRs) has changed to contain more rich information. This isn't really a breaking change, but it could be if you are parsing these comments in some way.
  • The deployment payload that gets set to the GitHub API will now contain two new attributes: params and parsed_params
  • By default, you can no longer .deploy or .noop a pull request fork unless it has approvals - reference. These changes have been made as an extra safety check against potentially untrusted commits
  • You will no longer be able to deploy a pull request if the target branch is not the default branch - reference1 reference2

Key Changes

  • You should use ${{ steps.branch-deploy.outputs.sha }} everywhere instead of ${{ steps.branch-deploy.outputs.ref }} - documentation
  • The structure of the deployment payload that gets sent to the GitHub API has a few new attributes - documentation
  • You can now have fine grained control to include or ignore CI checks that can (or can't) block your deployments - documentation
  • The message rendering system for pre/post deployment messages has been greatly improved. It now has many more variables for custom deployment messages and the default structures have been updated a bit - PR reference
  • A new input option has been added commit_verification: true that enforces commits to be signed/verified before they can be deployed by this Action - PR reference
  • A lot of new outputs have been added so subsequent workflow steps have access to even more rich data related to deployments
  • Preventing the ability to deploy a pull request that is not targeting the default branch
  • Branch ruleset warning checks - If you have a potential security misconfiguration in your branch rulesets, this Action will loudly warn you about it in the deployment logs
  • The sha output is now available on "Merge commit strategy" deployments as well

What's Changed

Here is a full list of changes:

New Contributors

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/github-branch-deploy-10.x branch from 6a6246f to 8a29a4e Compare January 18, 2025 08:26
@renovate renovate bot force-pushed the renovate/github-branch-deploy-10.x branch from 8a29a4e to 6afc686 Compare January 22, 2025 01:36
@renovate renovate bot force-pushed the renovate/github-branch-deploy-10.x branch from 6afc686 to fa52faa Compare January 22, 2025 15:18
@renovate renovate bot force-pushed the renovate/github-branch-deploy-10.x branch from fa52faa to b12e93d Compare January 22, 2025 15:21
@renovate renovate bot force-pushed the renovate/github-branch-deploy-10.x branch from b12e93d to 42f5dc8 Compare January 22, 2025 17:47
@renovate renovate bot force-pushed the renovate/github-branch-deploy-10.x branch from 42f5dc8 to 5832d29 Compare January 22, 2025 17:49
@renovate renovate bot force-pushed the renovate/github-branch-deploy-10.x branch from 5832d29 to b1b036d Compare January 22, 2025 20:23
@renovate renovate bot force-pushed the renovate/github-branch-deploy-10.x branch from b1b036d to c257347 Compare January 22, 2025 20:25
@renovate renovate bot force-pushed the renovate/github-branch-deploy-10.x branch from c257347 to 23e56f6 Compare January 29, 2025 01:57
@renovate renovate bot force-pushed the renovate/github-branch-deploy-10.x branch from 23e56f6 to a0a9a3e Compare January 30, 2025 14:46
@renovate renovate bot deployed to kubernetes January 30, 2025 14:48 Active
@renovate renovate bot force-pushed the renovate/github-branch-deploy-10.x branch from a0a9a3e to c4aca3d Compare February 19, 2025 12:45
@renovate renovate bot force-pushed the renovate/github-branch-deploy-10.x branch from c4aca3d to afb8f75 Compare March 18, 2025 20:02
@renovate renovate bot force-pushed the renovate/github-branch-deploy-10.x branch from afb8f75 to 019fed1 Compare March 26, 2025 22:25
@sonarqubecloud SonarQubeCloud
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants