[PR #46] [CLOSED] Bump fortio.org/fortio from 1.54.0 to 1.55.0 #48

New issue

Closed

opened 2026-03-15 16:07:01 +03:00 by kerem · 0 comments

kerem commented

2026-03-15 16:07:01 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/fortio/dnsping/pull/46
Author: @dependabot[bot]
Created: 6/19/2023
Status: ❌ Closed

Base: main ← Head: dependabot/go_modules/fortio.org/fortio-1.55.0

📝 Commits (1)

ab31783 Bump fortio.org/fortio from 1.54.0 to 1.55.0

📊 Changes

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

View changed files

📝 go.mod (+4 -4)
📝 go.sum (+9 -9)

📄 Description

Bumps fortio.org/fortio from 1.54.0 to 1.55.0.

Release notes

Sourced from fortio.org/fortio's releases.

Fortio 1.55.0

What's Changed

Big change is to be using JSON structured logging (unless calling -json-log=false) (fortio/fortio#768)

Also add log-errors=on option setting to rest api and web UI

Also add the runid to the structured logs (run=...) so errors from specific runs can be identified even if more than one are currently running

Structured JSON logging is coming from fortio.org/log 1.4.0 / fortio/log#22 - it includes http request logging in that format too (log.LogRequest)

Other changes:

go1.20.5 build image (fortio/fortio#762)

dependency updates

Full Changelog: https://github.com/fortio/fortio/compare/v1.54.3...v1.55.0

Fortio 1.54.3

What's Changed

Rebuilt with Go 1.20.4 (fortio/fortio#755)

Remove non idiomatic use of new() and use recommended var buf bytes.Buffer directly (fortio/fortio#751)

Dependency updates

Full Changelog: https://github.com/fortio/fortio/compare/v1.54.2...v1.54.3

Fortio 1.54.2

What's Changed

Fix long standing boundary condition rare bug with histogram buckets (in #746)

Fix error handling so passing an invalid -payload-file cause fortio to not proceed with curl/load test (abort, fixes #748 )

Dep updates

Full Changelog: https://github.com/fortio/fortio/compare/v1.54.1...v1.54.2

Fortio 1.54.1

What's Changed

Use newer go 1.20.3 (security fixes plus switch from 1.19) and corresponding new lints(fortio/fortio#743)

Note the linter identified an incompatible change needed:
func HandleCall[Q any](https://github.com/fortio/fortio/blob/HEAD/w http.ResponseWriter, r *http.Request) (*Q, error) {
to
func ProcessRequest[Q any](https://github.com/fortio/fortio/blob/HEAD/r *http.Request) (*Q, error) {
as HandleCall doesn't... handle it just unserializes. kept the old api as Deprecated for now.

Full Changelog: https://github.com/fortio/fortio/compare/v1.54.0...v1.54.1

Commits

7d76c8e using json structured logging, add log-errors option setting to rapi and UI...
9e5da81 Bump golang.org/x/net from 0.10.0 to 0.11.0 (#769)
690092b Bump docker/build-push-action from 4.0.0 to 4.1.0 (#764)
c7d2db5 Bump docker/setup-buildx-action from 2.5.0 to 2.6.0 (#765)
a4c5db0 Bump docker/setup-qemu-action from 2.1.0 to 2.2.0 (#767)
0eed2fd Bump actions/checkout from 3.5.2 to 3.5.3 (#766)
d4955ba Bump github/codeql-action from 2.3.6 to 2.13.4 (#763)
da8c0b9 go1.20.5 build image (#762)
7eb5747 Bump github/codeql-action from 2.3.3 to 2.3.6 (#761)
c2430aa Bump golang.org/x/net from 0.9.0 to 0.10.0 (#759)
Additional commits viewable in compare view

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 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/46 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 6/19/2023 **Status:** ❌ Closed **Base:** `main` ← **Head:** `dependabot/go_modules/fortio.org/fortio-1.55.0` --- ### 📝 Commits (1) - [`ab31783`](https://github.com/fortio/dnsping/commit/ab3178326a080f8a85dadc273e011cdd949d4c52) Bump fortio.org/fortio from 1.54.0 to 1.55.0 ### 📊 Changes **2 files changed** (+13 additions, -13 deletions) <details> <summary>View changed files</summary> 📝 `go.mod` (+4 -4) 📝 `go.sum` (+9 -9) </details> ### 📄 Description Bumps [fortio.org/fortio](https://github.com/fortio/fortio) from 1.54.0 to 1.55.0. <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>Fortio 1.55.0</h2> <h2>What's Changed</h2> <ul> <li>Big change is to be using JSON structured logging (unless calling <code>-json-log=false</code>) (<a href="https://redirect.github.com/fortio/fortio/pull/768">fortio/fortio#768</a>) <ul> <li>Also add <code>log-errors=on</code> option setting to rest api and web UI</li> <li>Also add the runid to the structured logs (run=...) so errors from specific runs can be identified even if more than one are currently running</li> </ul> </li> </ul> <p>Structured JSON logging is coming from <a href="https://github.com/fortio/log/releases/tag/v1.4.0">fortio.org/log 1.4.0 </a> / <a href="https://redirect.github.com/fortio/log/pull/22">fortio/log#22</a> - it includes http request logging in that format too (log.LogRequest)</p> <p>Other changes:</p> <ul> <li>go1.20.5 build image (<a href="https://redirect.github.com/fortio/fortio/pull/762">fortio/fortio#762</a>)</li> <li>dependency updates</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/fortio/fortio/compare/v1.54.3...v1.55.0">https://github.com/fortio/fortio/compare/v1.54.3...v1.55.0</a></p> <h2>Fortio 1.54.3</h2> <h2>What's Changed</h2> <ul> <li>Rebuilt with Go 1.20.4 (<a href="https://redirect.github.com/fortio/fortio/pull/755">fortio/fortio#755</a>)</li> <li>Remove non idiomatic use of new() and use recommended var buf bytes.Buffer directly (<a href="https://redirect.github.com/fortio/fortio/pull/751">fortio/fortio#751</a>)</li> <li>Dependency updates</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/fortio/fortio/compare/v1.54.2...v1.54.3">https://github.com/fortio/fortio/compare/v1.54.2...v1.54.3</a></p> <h2>Fortio 1.54.2</h2> <h2>What's Changed</h2> <ul> <li>Fix long standing boundary condition rare bug with histogram buckets (in <a href="https://redirect.github.com/fortio/fortio/issues/746">#746</a>)</li> <li>Fix error handling so passing an invalid <code>-payload-file</code> cause fortio to not proceed with curl/load test (abort, fixes <a href="https://redirect.github.com/fortio/fortio/issues/748">#748</a> )</li> <li>Dep updates</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/fortio/fortio/compare/v1.54.1...v1.54.2">https://github.com/fortio/fortio/compare/v1.54.1...v1.54.2</a></p> <h2>Fortio 1.54.1</h2> <h2>What's Changed</h2> <ul> <li>Use newer go 1.20.3 (security fixes plus switch from 1.19) and corresponding new lints(<a href="https://redirect.github.com/fortio/fortio/pull/743">fortio/fortio#743</a>)</li> </ul> <p>Note the linter identified an incompatible change needed:</p> <pre lang="golang"><code>func HandleCall[Q any](https://github.com/fortio/fortio/blob/HEAD/w http.ResponseWriter, r *http.Request) (*Q, error) { </code></pre> <p>to</p> <pre lang="golang"><code>func ProcessRequest[Q any](https://github.com/fortio/fortio/blob/HEAD/r *http.Request) (*Q, error) { </code></pre> <p>as HandleCall doesn't... handle it just unserializes. kept the old api as Deprecated for now.</p> <p><strong>Full Changelog</strong>: <a href="https://github.com/fortio/fortio/compare/v1.54.0...v1.54.1">https://github.com/fortio/fortio/compare/v1.54.0...v1.54.1</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/fortio/fortio/commit/7d76c8ef1ea2b66f736b3d54d093ed0d2ce2a768"><code>7d76c8e</code></a> using json structured logging, add <code>log-errors</code> option setting to rapi and UI...</li> <li><a href="https://github.com/fortio/fortio/commit/9e5da817e663e83351d96e0264b970eb56e97bcb"><code>9e5da81</code></a> Bump golang.org/x/net from 0.10.0 to 0.11.0 (<a href="https://redirect.github.com/fortio/fortio/issues/769">#769</a>)</li> <li><a href="https://github.com/fortio/fortio/commit/690092bf06b7b9bc770040869da9d16e59518185"><code>690092b</code></a> Bump docker/build-push-action from 4.0.0 to 4.1.0 (<a href="https://redirect.github.com/fortio/fortio/issues/764">#764</a>)</li> <li><a href="https://github.com/fortio/fortio/commit/c7d2db5ea9e2e6faa98560ca1e5ca04b9bdba8ee"><code>c7d2db5</code></a> Bump docker/setup-buildx-action from 2.5.0 to 2.6.0 (<a href="https://redirect.github.com/fortio/fortio/issues/765">#765</a>)</li> <li><a href="https://github.com/fortio/fortio/commit/a4c5db07469e950bc9172c3554b0c5d140ce9521"><code>a4c5db0</code></a> Bump docker/setup-qemu-action from 2.1.0 to 2.2.0 (<a href="https://redirect.github.com/fortio/fortio/issues/767">#767</a>)</li> <li><a href="https://github.com/fortio/fortio/commit/0eed2fdca39f570180c8c4c75feb2eb25f086c06"><code>0eed2fd</code></a> Bump actions/checkout from 3.5.2 to 3.5.3 (<a href="https://redirect.github.com/fortio/fortio/issues/766">#766</a>)</li> <li><a href="https://github.com/fortio/fortio/commit/d4955ba0f77e9902d454dc4dafdd02ef6637f5a2"><code>d4955ba</code></a> Bump github/codeql-action from 2.3.6 to 2.13.4 (<a href="https://redirect.github.com/fortio/fortio/issues/763">#763</a>)</li> <li><a href="https://github.com/fortio/fortio/commit/da8c0b9dceafe47e3beb8c7681ce66573d4336a3"><code>da8c0b9</code></a> go1.20.5 build image (<a href="https://redirect.github.com/fortio/fortio/issues/762">#762</a>)</li> <li><a href="https://github.com/fortio/fortio/commit/7eb5747f3dbaa9ba1be78e0db553b0f86eb64975"><code>7eb5747</code></a> Bump github/codeql-action from 2.3.3 to 2.3.6 (<a href="https://redirect.github.com/fortio/fortio/issues/761">#761</a>)</li> <li><a href="https://github.com/fortio/fortio/commit/c2430aa7179a0311b1aa823ded9fdd15ce5ffefe"><code>c2430aa</code></a> Bump golang.org/x/net from 0.9.0 to 0.10.0 (<a href="https://redirect.github.com/fortio/fortio/issues/759">#759</a>)</li> <li>Additional commits viewable in <a href="https://github.com/fortio/fortio/compare/v1.54.0...v1.55.0">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.54.0&new-version=1.55.0)](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 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>