shiny/presenter
6
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 20 Activity

chore(release): prepare for v0.3.5 #158

Closed
releaser wants to merge 2 commits from next-release into main
pull from: next-release
merge into: shiny:main
Conversation 2 Commits 2 Files Changed 2
+16 -2
releaser commented 2026-05-09 12:55:50 +00:00
Owner
Copy Link
Copy Source

[0.3.5] - 2026-05-09

🐛 Bug Fixes

  • (ci) Use go-test-coverage binary directly to fix Gitea Actions (#150)
  • (deps) Update module github.com/99designs/gqlgen to v0.17.90 (#149)

⚙️ Miscellaneous Tasks

  • (deps) Update pre-commit hook alessandrojcm/commitlint-pre-commit-hook to v9.25.0 (#152)
  • (deps) Update pre-commit hook golangci/golangci-lint to v2.12.0 (#154)
  • (deps) Update pre-commit hook golangci/golangci-lint to v2.12.1 (#155)
  • (deps) Update pre-commit hook golangci/golangci-lint to v2.12.2 (#157)

Note: Please use Squash Merge when merging this PR.

## [0.3.5] - 2026-05-09 ### 🐛 Bug Fixes - *(ci)* Use go-test-coverage binary directly to fix Gitea Actions (#150) - *(deps)* Update module github.com/99designs/gqlgen to v0.17.90 (#149) ### ⚙️ Miscellaneous Tasks - *(deps)* Update pre-commit hook alessandrojcm/commitlint-pre-commit-hook to v9.25.0 (#152) - *(deps)* Update pre-commit hook golangci/golangci-lint to v2.12.0 (#154) - *(deps)* Update pre-commit hook golangci/golangci-lint to v2.12.1 (#155) - *(deps)* Update pre-commit hook golangci/golangci-lint to v2.12.2 (#157) <!-- generated by git-cliff --> --- **Note:** Please use **Squash Merge** when merging this PR.
releaser added 2 commits 2026-05-09 12:55:51 +00:00
chore(release): prepare for v0.3.5 f3eeddf1c6
chore(release): prepare for v0.3.5
presenter / vulnerabilities (pull_request) Successful in 1m39s
Details
presenter / test (pull_request) Successful in 2m22s
Details
pre-commit / pre-commit (pull_request) Successful in 6m12s
Details
2a1f07cef2
releaser added 1 commit 2026-05-09 12:55:52 +00:00
chore(release): prepare for v0.3.5
presenter / vulnerabilities (pull_request) Successful in 1m39s
Details
presenter / test (pull_request) Successful in 2m22s
Details
pre-commit / pre-commit (pull_request) Successful in 6m12s
Details
2a1f07cef2
gitea-actions bot commented 2026-05-09 13:13:48 +00:00
Copy Link
Copy Source

Coverage Report

Total coverage: 100%

## Coverage Report Total coverage: **100%**
gitea-actions bot commented 2026-05-09 13:16:22 +00:00
Copy Link
Copy Source

Coverage Report

Total coverage: 100%

## Coverage Report Total coverage: **100%**
releaser closed this pull request 2026-06-10 22:01:05 +00:00
releaser deleted branch next-release 2026-06-10 22:01:06 +00:00
All checks were successful
presenter / vulnerabilities (pull_request) Successful in 1m39s
Required
Details
presenter / test (pull_request) Successful in 2m22s
Required
Details
pre-commit / pre-commit (pull_request) Successful in 6m12s
Required
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
Doing
To Do
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: shiny/presenter#158
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?