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

chore(release): prepare for v0.1.2 #73

Closed
releaser wants to merge 2 commits from next-release into main
pull from: next-release
merge into: unboundsoftware:main
Conversation 2 Commits 2 Files Changed 2
+13 -1
releaser commented 2026-02-17 17:05:35 +00:00
Owner
Copy Link
Copy Source

[0.1.2] - 2026-02-17

⚙️ Miscellaneous Tasks

  • (deps) Update golang:1.25.5 docker digest to 3a01526 (#64)
  • (deps) Update pre-commit hook alessandrojcm/commitlint-pre-commit-hook to v9.24.0 (#65)
  • (deps) Update golang docker tag to v1.25.6 (#67)
  • Remove unused .gitlab-ci.yml
  • Add code coverage integration
  • (deps) Update pre-commit hook golangci/golangci-lint to v2.9.0 (#71)
  • (deps) Update pre-commit hook golangci/golangci-lint to v2.10.1 (#72)

Note: Please use Squash Merge when merging this PR.

## [0.1.2] - 2026-02-17 ### ⚙️ Miscellaneous Tasks - *(deps)* Update golang:1.25.5 docker digest to 3a01526 (#64) - *(deps)* Update pre-commit hook alessandrojcm/commitlint-pre-commit-hook to v9.24.0 (#65) - *(deps)* Update golang docker tag to v1.25.6 (#67) - Remove unused .gitlab-ci.yml - Add code coverage integration - *(deps)* Update pre-commit hook golangci/golangci-lint to v2.9.0 (#71) - *(deps)* Update pre-commit hook golangci/golangci-lint to v2.10.1 (#72) <!-- generated by git-cliff --> --- **Note:** Please use **Squash Merge** when merging this PR.
releaser added 2 commits 2026-02-17 17:05:36 +00:00
chore(release): prepare for v0.1.2 14fda7c4a6
chore(release): prepare for v0.1.2
dbsetup / vulnerabilities (pull_request) Successful in 1m59s
Details
pre-commit / pre-commit (pull_request) Successful in 7m10s
Details
dbsetup / test (pull_request) Successful in 9m2s
Details
8a772c0bd8
releaser added 1 commit 2026-02-17 17:05:37 +00:00
chore(release): prepare for v0.1.2
dbsetup / vulnerabilities (pull_request) Successful in 1m59s
Details
pre-commit / pre-commit (pull_request) Successful in 7m10s
Details
dbsetup / test (pull_request) Successful in 9m2s
Details
8a772c0bd8
gitea-actions bot commented 2026-02-17 17:09:44 +00:00
Copy Link
Copy Source

Coverage Report

Total coverage: 0.0%

## Coverage Report Total coverage: **0.0%**
gitea-actions bot commented 2026-02-17 17:20:18 +00:00
Copy Link
Copy Source

Coverage Report

Total coverage: 0.0%

## Coverage Report Total coverage: **0.0%**
releaser closed this pull request 2026-02-22 17:52:34 +00:00
releaser deleted branch next-release 2026-02-22 17:52:34 +00:00
All checks were successful
dbsetup / vulnerabilities (pull_request) Successful in 1m59s
Required
Details
pre-commit / pre-commit (pull_request) Successful in 7m10s
Required
Details
dbsetup / test (pull_request) Successful in 9m2s
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unboundsoftware/dbsetup#73
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?