Update stefanzweifel/git-auto-commit-action action from v5.0.1 to v5.1.0 (.github/workflows/release-3-master-into-dev.yml)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
stefanzweifel/git-auto-commit-action	action	minor	v5.0.1 -> v5.1.0

---

Release Notes

stefanzweifel/git-auto-commit-action (stefanzweifel/git-auto-commit-action)

v5.1.0

Compare Source

Changed

• Include github.actor_id in default commit_author (#​354) @​parkerbxyz

Fixed

• docs(README): fix broken protected branch docs link (#​346) @​scarf005
• Update README.md (#​343) @​Kludex

Dependency Updates

• Bump bats from 1.11.0 to 1.11.1 (#​353) @​dependabot
• Bump github/super-linter from 6 to 7 (#​342) @​dependabot
• Bump github/super-linter from 5 to 6 (#​335) @​dependabot

---

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 becomes conflicted, 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.

[dryrunsecurity]

DryRun Security Summary

The pull request updates GitHub Actions workflows to improve the application's release management process by modifying PlantUML diagram generation, release branch creation, and branch merging workflows, with a focus on version number updates and process automation.

Expand for full summary

Summary:

The code changes in this pull request are primarily focused on updating the GitHub Actions workflows related to the application's release process. The key changes include:

1. PlantUML Diagram Generation Workflow: The workflow responsible for generating SVG and PNG diagrams from PlantUML files has been updated to use a newer version of the stefanzweifel/git-auto-commit-action GitHub Action. While version updates are generally a good practice, it's important to review the changelog and release notes to ensure there are no known security vulnerabilities or breaking changes introduced in the new version.

2. Release Branch Creation and Version Update Workflow: This workflow automates the process of creating a new release branch, updating the version numbers in key files, and creating a pull request to merge the release branch into the master branch. The workflow ensures that the version numbers are updated correctly, which is an important security consideration to prevent version-related issues.

3. Merging Master into Dev and Bugfix Branches Workflow: This workflow is responsible for creating a pull request to merge the changes from the master branch into the dev and bugfix branches, ensuring that the version numbers are updated across all relevant branches.

Overall, the code changes in this pull request are focused on improving the application's release management process, and they do not introduce any obvious security concerns. However, it's important to review the application code changes themselves to ensure that no security vulnerabilities are introduced, and to monitor the external dependencies used in the GitHub Actions workflows for any security-related updates.

Files Changed:

1. .github/workflows/plantuml.yml: This workflow is responsible for generating SVG and PNG diagrams from PlantUML files. The key change is the update of the stefanzweifel/git-auto-commit-action GitHub Action from version 5.0.1 to 5.1.0.

2. .github/workflows/release-1-create-pr.yml: This workflow automates the process of creating a pull request to merge a new release branch into the master branch. It updates the version numbers in key files and creates the pull request.

3. .github/workflows/release-3-master-into-dev.yml: This workflow is responsible for creating a pull request to merge the changes from the master branch into the dev and bugfix branches, ensuring that the version numbers are updated across all relevant branches.

Code Analysis

We ran 9 analyzers against 3 files and 0 analyzers had findings. 9 analyzers had no findings.

View PR in the DryRun Dashboard.