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

chore(release): prepare for v0.9.7 #801

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
+16 -1
releaser commented 2026-04-11 00:13:27 +00:00
Owner
Copy Link
Copy Source

[0.9.7] - 2026-04-11

🐛 Bug Fixes

  • (deps) Update module gitlab.com/unboundsoftware/eventsourced/pg to v1.18.6 (#790)
  • (deps) Update module github.com/alecthomas/kong to v1.15.0 (#791)
  • (deps) Update opentelemetry-go monorepo (#793)
  • (deps) Update module go.opentelemetry.io/contrib/bridges/otelslog to v0.18.0 (#797)
  • (deps) Update module github.com/wundergraph/graphql-go-tools/v2 to v2.0.0-rc.268 (#798)

⚙️ Miscellaneous Tasks

  • (deps) Update golang:1.26.1 docker digest to 5ba1126 (#795)
  • (deps) Update golang docker tag to v1.26.2 (#800)

Note: Please use Squash Merge when merging this PR.

## [0.9.7] - 2026-04-11 ### 🐛 Bug Fixes - *(deps)* Update module gitlab.com/unboundsoftware/eventsourced/pg to v1.18.6 (#790) - *(deps)* Update module github.com/alecthomas/kong to v1.15.0 (#791) - *(deps)* Update opentelemetry-go monorepo (#793) - *(deps)* Update module go.opentelemetry.io/contrib/bridges/otelslog to v0.18.0 (#797) - *(deps)* Update module github.com/wundergraph/graphql-go-tools/v2 to v2.0.0-rc.268 (#798) ### ⚙️ Miscellaneous Tasks - *(deps)* Update golang:1.26.1 docker digest to 5ba1126 (#795) - *(deps)* Update golang docker tag to v1.26.2 (#800) <!-- generated by git-cliff --> --- **Note:** Please use **Squash Merge** when merging this PR.
releaser added 2 commits 2026-04-11 00:13:31 +00:00
chore(release): prepare for v0.9.7 24e583c26c
chore(release): prepare for v0.9.7
schemas / vulnerabilities (pull_request) Successful in 1m57s
Details
schemas / check (pull_request) Successful in 2m39s
Details
schemas / check-release (pull_request) Successful in 3m6s
Details
pre-commit / pre-commit (pull_request) Successful in 6m36s
Details
schemas / build (pull_request) Successful in 6m33s
Details
schemas / deploy-prod (pull_request) Has been skipped
Details
5403f497f3
All checks were successful
schemas / vulnerabilities (pull_request) Successful in 1m57s
Required
Details
schemas / check (pull_request) Successful in 2m39s
Required
Details
schemas / check-release (pull_request) Successful in 3m6s
Required
Details
pre-commit / pre-commit (pull_request) Successful in 6m36s
Required
Details
schemas / build (pull_request) Successful in 6m33s
Required
Details
schemas / deploy-prod (pull_request) Has been skipped
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
Clear labels
dependencies
Pull requests that update a dependency file
 docker
go
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/schemas#801
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?