unboundsoftware/robotframework
6
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 86 Activity

chore(release): prepare for v7.5.20 #382

Open
releaser wants to merge 2 commits from next-release into main
pull from: next-release
merge into: unboundsoftware:main
Conversation 0 Commits 2 Files Changed 2
+7 -1
releaser commented 2026-06-20 20:06:00 +00:00
Owner
Copy Link
Copy Source

[7.5.20] - 2026-06-20

Chore

  • (deps) Update actions/checkout action to v7 (#381)

Note: Please use Squash Merge when merging this PR.

## [7.5.20] - 2026-06-20 ### Chore - *(deps)* Update actions/checkout action to v7 (#381) <!-- generated by git-cliff --> --- **Note:** Please use **Squash Merge** when merging this PR.
releaser added 2 commits 2026-06-20 20:06:01 +00:00
chore(release): prepare for v7.5.20 219b0b36a9
chore(release): prepare for v7.5.20
robotframework / build (pull_request) Successful in 9m18s
Details
adc2cb1c62
All checks were successful
robotframework / build (pull_request) Successful in 9m18s
Required
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin next-release:next-release
git checkout next-release
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
acctest (Shiny Acctest) argoyle (Joakim Olsson) buildtools (Buildtools) kubernetes (Kubernetes) releaser (Unbound Releaser) renovate (Renovate Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unboundsoftware/robotframework#382
Delete Branch "next-release"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?