[PR #138] [MERGED] Bump fortio.org/fortio from 1.71.0 to 1.71.1 #139

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

📋 Pull Request Information

Original PR: https://github.com/fortio/dnsping/pull/138
Author: @dependabot[bot]
Created: 8/25/2025
Status: Merged
Merged: 8/25/2025
Merged by: @ldemailly

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


📝 Commits (1)

  • 6c64fcd Bump fortio.org/fortio from 1.71.0 to 1.71.1

📊 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.71.0 to 1.71.1.

Release notes

Sourced from fortio.org/fortio's releases.

v1.71.1

Stats bug fix

fortio/fortio#1081

  • If all the data is in the last (overflow) bucket, the min was not set as start of bucket Note that if all the data is in that bucket it does mean you should use a larger -r and/or an -offset so your data fits into the buckets so you get more meaningful percentiles.

(Also changed: Bump grol.io/grol (and thus fortio/terminal) from 0.91.5 to 0.91.9)

Full Changelog: https://github.com/fortio/fortio/compare/v1.71.0...v1.71.1

Commits
  • bb4c5f6 Issue with stats bucket with extreme resolution (#1081)
  • 574cf73 Bump grol.io/grol from 0.91.8 to 0.91.9 in the fortio-and-grol group (#1082)
  • a2d7109 Bump grol.io/grol from 0.91.5 to 0.91.8 in the fortio-and-grol group (#1079)
  • 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/138 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 8/25/2025 **Status:** ✅ Merged **Merged:** 8/25/2025 **Merged by:** [@ldemailly](https://github.com/ldemailly) **Base:** `main` ← **Head:** `dependabot/go_modules/fortio.org/fortio-1.71.1` --- ### 📝 Commits (1) - [`6c64fcd`](https://github.com/fortio/dnsping/commit/6c64fcde11c1f1a6cf333cead4733e01bca5bfcc) Bump fortio.org/fortio from 1.71.0 to 1.71.1 ### 📊 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.71.0 to 1.71.1. <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.71.1</h2> <p>Stats bug fix</p> <p><a href="https://redirect.github.com/fortio/fortio/pull/1081">fortio/fortio#1081</a></p> <ul> <li>If all the data is in the last (overflow) bucket, the <code>min</code> was not set as start of bucket Note that if all the data is in that bucket it does mean you should use a larger <code>-r</code> and/or an <code>-offset</code> so your data fits into the buckets so you get more meaningful percentiles.</li> </ul> <p>(Also changed: Bump grol.io/grol (and thus fortio/terminal) from 0.91.5 to 0.91.9)</p> <p><strong>Full Changelog</strong>: <a href="https://github.com/fortio/fortio/compare/v1.71.0...v1.71.1">https://github.com/fortio/fortio/compare/v1.71.0...v1.71.1</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/fortio/fortio/commit/bb4c5f63de9a738e5a656527e0d7d25b35cb5a3e"><code>bb4c5f6</code></a> Issue with stats bucket with extreme resolution (<a href="https://redirect.github.com/fortio/fortio/issues/1081">#1081</a>)</li> <li><a href="https://github.com/fortio/fortio/commit/574cf73eef33d2f6bb318aaf85eb37c1cfec0f12"><code>574cf73</code></a> Bump grol.io/grol from 0.91.8 to 0.91.9 in the fortio-and-grol group (<a href="https://redirect.github.com/fortio/fortio/issues/1082">#1082</a>)</li> <li><a href="https://github.com/fortio/fortio/commit/a2d71097ba6b44ca63a4222f313ba26e7337b6ce"><code>a2d7109</code></a> Bump grol.io/grol from 0.91.5 to 0.91.8 in the fortio-and-grol group (<a href="https://redirect.github.com/fortio/fortio/issues/1079">#1079</a>)</li> <li>See full diff in <a href="https://github.com/fortio/fortio/compare/v1.71.0...v1.71.1">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.71.0&new-version=1.71.1)](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:55 +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#139
No description provided.