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

chore(release): prepare for v0.9.6 #753

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
+17 -1
releaser commented 2026-03-06 03:27:50 +00:00
Owner
Copy Link
Copy Source

[0.9.6] - 2026-03-06

🐛 Bug Fixes

  • (graph) Stabilize debouncer tests with synctest fake clock
  • (deps) Update module github.com/wundergraph/graphql-go-tools/v2 to v2.0.0-rc.257 (#743)
  • (deps) Update golang.org/x/net to v0.51.0
  • (deps) Update module go.opentelemetry.io/contrib/bridges/otelslog to v0.16.0 (#745)
  • (deps) Update opentelemetry-go monorepo (#744)
  • (deps) Update module github.com/wundergraph/graphql-go-tools/v2 to v2.0.0-rc.260 (#750)
  • (deps) Update module github.com/wundergraph/graphql-go-tools/v2 to v2.0.0-rc.261 (#751)

⚙️ Miscellaneous Tasks

  • (deps) Update golang docker tag to v1.26.1 (#752)

Note: Please use Squash Merge when merging this PR.

## [0.9.6] - 2026-03-06 ### 🐛 Bug Fixes - *(graph)* Stabilize debouncer tests with synctest fake clock - *(deps)* Update module github.com/wundergraph/graphql-go-tools/v2 to v2.0.0-rc.257 (#743) - *(deps)* Update golang.org/x/net to v0.51.0 - *(deps)* Update module go.opentelemetry.io/contrib/bridges/otelslog to v0.16.0 (#745) - *(deps)* Update opentelemetry-go monorepo (#744) - *(deps)* Update module github.com/wundergraph/graphql-go-tools/v2 to v2.0.0-rc.260 (#750) - *(deps)* Update module github.com/wundergraph/graphql-go-tools/v2 to v2.0.0-rc.261 (#751) ### ⚙️ Miscellaneous Tasks - *(deps)* Update golang docker tag to v1.26.1 (#752) <!-- generated by git-cliff --> --- **Note:** Please use **Squash Merge** when merging this PR.
releaser added 2 commits 2026-03-06 03:27:51 +00:00
chore(release): prepare for v0.9.6 d78afa18a8
chore(release): prepare for v0.9.6
schemas / vulnerabilities (pull_request) Successful in 2m14s
Details
schemas / check-release (pull_request) Successful in 3m8s
Details
schemas / check (pull_request) Successful in 4m14s
Details
pre-commit / pre-commit (pull_request) Successful in 6m57s
Details
schemas / build (pull_request) Successful in 6m44s
Details
schemas / deploy-prod (pull_request) Has been skipped
Details
f4edad8cd9
releaser closed this pull request 2026-03-06 20:00:02 +00:00
releaser deleted branch next-release 2026-03-06 20:00:03 +00:00
All checks were successful
schemas / vulnerabilities (pull_request) Successful in 2m14s
Required
Details
schemas / check-release (pull_request) Successful in 3m8s
Required
Details
schemas / check (pull_request) Successful in 4m14s
Required
Details
pre-commit / pre-commit (pull_request) Successful in 6m57s
Required
Details
schemas / build (pull_request) Successful in 6m44s
Required
Details
schemas / deploy-prod (pull_request) Has been skipped
Details

Pull request closed

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