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

chore(release): prepare for v7.5.7 #301

Closed
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-03-04 18:12:28 +00:00
Owner
Copy Link
Copy Source

[7.5.7] - 2026-03-04

Chore

  • (deps) Update dependency faker to v40.8.0 (#300)

Note: Please use Squash Merge when merging this PR.

## [7.5.7] - 2026-03-04 ### Chore - *(deps)* Update dependency faker to v40.8.0 (#300) <!-- generated by git-cliff --> --- **Note:** Please use **Squash Merge** when merging this PR.
releaser added 2 commits 2026-03-04 18:12:30 +00:00
chore(release): prepare for v7.5.7 931e8fc75d
chore(release): prepare for v7.5.7
robotframework / build (pull_request) Successful in 49s
Details
b488d432fe
releaser closed this pull request 2026-03-13 15:43:48 +00:00
releaser deleted branch next-release 2026-03-13 15:43:48 +00:00
All checks were successful
robotframework / build (pull_request) Successful in 49s
Required
Details

Pull request closed

Please reopen this pull request to perform a merge.
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#301
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?