[PR #128] [MERGED] Bump fortio.org/fortio from 1.69.3 to 1.69.4 #134

Closed
opened 2026-03-15 16:11:39 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/fortio/dnsping/pull/128
Author: @dependabot[bot]
Created: 4/28/2025
Status: Merged
Merged: 4/28/2025
Merged by: @ldemailly

Base: mainHead: dependabot/go_modules/fortio.org/fortio-1.69.4


📝 Commits (1)

  • 32ee3ed Bump fortio.org/fortio from 1.69.3 to 1.69.4

📊 Changes

2 files changed (+3 additions, -3 deletions)

View changed files

📝 go.mod (+1 -1)
📝 go.sum (+2 -2)

📄 Description

Bumps fortio.org/fortio from 1.69.3 to 1.69.4.

Release notes

Sourced from fortio.org/fortio's releases.

v1.69.4

  • New exceptionDetails in jrpc error replies: the json version of the error object (#1042)
  • Grol has now bytes() and utf8() functions to go to array of bytes and back to utf8 string
  • Grol (and thus fortio script interactive mode) now also uses fortio.org/terminal library that uses golang.org/x/term latest commit as our change to History got merged upstream, so no more fortio.org/term needed.
  • Bump grpc

Full Changelog: https://github.com/fortio/fortio/compare/v1.69.3...v1.69.4

Commits
  • 54189cc Adding error details to jrpc server replies (#1042)
  • a0e2a15 Bump grol.io/grol from 0.80.4 to 0.82.1 in the fortio-and-grol group (#1043)
  • 84a5dc7 Bump google.golang.org/grpc from 1.71.1 to 1.72.0 (#1041)
  • See full diff in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/fortio/dnsping/pull/128 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 4/28/2025 **Status:** ✅ Merged **Merged:** 4/28/2025 **Merged by:** [@ldemailly](https://github.com/ldemailly) **Base:** `main` ← **Head:** `dependabot/go_modules/fortio.org/fortio-1.69.4` --- ### 📝 Commits (1) - [`32ee3ed`](https://github.com/fortio/dnsping/commit/32ee3edbbdde87d222a5538b92dc993bbbe9d442) Bump fortio.org/fortio from 1.69.3 to 1.69.4 ### 📊 Changes **2 files changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `go.mod` (+1 -1) 📝 `go.sum` (+2 -2) </details> ### 📄 Description Bumps [fortio.org/fortio](https://github.com/fortio/fortio) from 1.69.3 to 1.69.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/fortio/fortio/releases">fortio.org/fortio's releases</a>.</em></p> <blockquote> <h2>v1.69.4</h2> <ul> <li>New exceptionDetails in jrpc error replies: the json version of the error object (<a href="https://redirect.github.com/fortio/fortio/issues/1042">#1042</a>)</li> <li>Grol has now <code>bytes()</code> and <code>utf8()</code> functions to go to array of bytes and back to utf8 string</li> <li>Grol (and thus <code>fortio script</code> interactive mode) now also uses fortio.org/terminal library that uses golang.org/x/term latest commit as our change to History got merged upstream, so no more fortio.org/term needed.</li> <li>Bump grpc</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/fortio/fortio/compare/v1.69.3...v1.69.4">https://github.com/fortio/fortio/compare/v1.69.3...v1.69.4</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/fortio/fortio/commit/54189cc772636e28108a43aab57f8bd528eef99b"><code>54189cc</code></a> Adding error details to jrpc server replies (<a href="https://redirect.github.com/fortio/fortio/issues/1042">#1042</a>)</li> <li><a href="https://github.com/fortio/fortio/commit/a0e2a15103285921ebf6ebf46c053e835639ad59"><code>a0e2a15</code></a> Bump grol.io/grol from 0.80.4 to 0.82.1 in the fortio-and-grol group (<a href="https://redirect.github.com/fortio/fortio/issues/1043">#1043</a>)</li> <li><a href="https://github.com/fortio/fortio/commit/84a5dc7c10d28bf7536014ce4093f382e53618df"><code>84a5dc7</code></a> Bump google.golang.org/grpc from 1.71.1 to 1.72.0 (<a href="https://redirect.github.com/fortio/fortio/issues/1041">#1041</a>)</li> <li>See full diff in <a href="https://github.com/fortio/fortio/compare/v1.69.3...v1.69.4">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=fortio.org/fortio&package-manager=go_modules&previous-version=1.69.3&new-version=1.69.4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-15 16:11:39 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dnsping#134
No description provided.