unboundsoftware/storage
6
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 13 Activity

chore(release): prepare for v0.4.2 #135

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
+16 -1
releaser commented 2026-06-08 19:34:03 +00:00
Owner
Copy Link
Copy Source

[0.4.2] - 2026-06-08

🐛 Bug Fixes

  • (deps) Update aws-sdk-go-v2 monorepo (#116)
  • (deps) Update aws-sdk-go-v2 monorepo (#118)
  • (deps) Update aws-sdk-go-v2 monorepo (#120)
  • (deps) Update aws-sdk-go-v2 monorepo (#122)
  • (deps) Update aws-sdk-go-v2 monorepo (#124)
  • (deps) Update module github.com/aws/aws-sdk-go-v2/feature/s3/transfermanager to v0.2.3 (#126)
  • (deps) Update aws-sdk-go-v2 monorepo (#128)
  • (deps) Update aws-sdk-go-v2 monorepo (#130)
  • (deps) Update aws-sdk-go-v2 monorepo (#132)
  • (deps) Update aws-sdk-go-v2 monorepo to v0.2.7 (#134)

Note: Please use Squash Merge when merging this PR.

## [0.4.2] - 2026-06-08 ### 🐛 Bug Fixes - *(deps)* Update aws-sdk-go-v2 monorepo (#116) - *(deps)* Update aws-sdk-go-v2 monorepo (#118) - *(deps)* Update aws-sdk-go-v2 monorepo (#120) - *(deps)* Update aws-sdk-go-v2 monorepo (#122) - *(deps)* Update aws-sdk-go-v2 monorepo (#124) - *(deps)* Update module github.com/aws/aws-sdk-go-v2/feature/s3/transfermanager to v0.2.3 (#126) - *(deps)* Update aws-sdk-go-v2 monorepo (#128) - *(deps)* Update aws-sdk-go-v2 monorepo (#130) - *(deps)* Update aws-sdk-go-v2 monorepo (#132) - *(deps)* Update aws-sdk-go-v2 monorepo to v0.2.7 (#134) <!-- generated by git-cliff --> --- **Note:** Please use **Squash Merge** when merging this PR.
releaser added 2 commits 2026-06-08 19:34:05 +00:00
chore(release): prepare for v0.4.2 043a17d4c8
chore(release): prepare for v0.4.2
storage / test (pull_request) Successful in 1m34s
Details
storage / vulnerabilities (pull_request) Successful in 1m33s
Details
pre-commit / pre-commit (pull_request) Successful in 6m6s
Details
331981e56a
releaser closed this pull request 2026-06-08 21:34:11 +00:00
releaser deleted branch next-release 2026-06-08 21:34:11 +00:00
All checks were successful
storage / test (pull_request) Successful in 1m34s
Required
Details
storage / vulnerabilities (pull_request) Successful in 1m33s
Required
Details
pre-commit / pre-commit (pull_request) Successful in 6m6s
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/storage#135
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?