chore(deps): update bump go dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
github.com/gin-contrib/gzip	v1.2.0 -> v1.2.2					require	patch
go (source)	1.23.4 -> 1.24.0					toolchain	minor
golang.org/x/crypto	v0.32.0 -> v0.33.0					require	minor

---

Release Notes

gin-contrib/gzip (github.com/gin-contrib/gzip)

v1.2.2

Compare Source

Changelog

Features

• c881664: feat: add logic to handle weak ETag headers (#​100) (@​appleboy)

Bug fixes

• 438926d: fix: default auto decompressor on uncompressed or double compressed bodies (#​91) (@​alexdyukov)

Refactor

• 3529136: refactor: improve error handling and resource management in gzip utils (#​101) (@​appleboy)
• f3f028a: refactor: refactor middleware and improve API handling (@​appleboy)
• 4fc267c: refactor: improve error handling and documentation for content encoding (@​appleboy)
• aa5d8ee: refactor: optimize gzip writer pool management and resource handling (#​102) (@​appleboy)

v1.2.1

Compare Source

Changelog

Features

• 1b7e801: feat: improve compression level validation and default handling (@​appleboy)
• bc3ccd1: feat: add new endpoint and improve middleware functionality (@​appleboy)

Bug fixes

• 3bd96db: fix: use Header().Add instead of Header() for setting Vary header (#​99) (@​appleboy)

Enhancements

• fa0d885: chore: update dependencies to latest versions (@​appleboy)

Refactor

• 262eca6: refactor: improve gzip handling and optimize resource management (@​appleboy)
• 79e888f: refactor: refactor codebase to improve maintainability and performance (@​appleboy)
• e389346: refactor: refactor codebase and update API integration (@​appleboy)

Others

• 3830b8f: fix http: invalid Content-Length of "-1" (#​97) (@​evildao)

golang/go (go)

v1.24.0

v1.23.6

v1.23.5

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.51%. Comparing base (a0bad7b) to head (5444f91).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #758      +/-   ##
==========================================
+ Coverage   79.36%   79.51%   +0.15%     
==========================================
  Files          56       56              
  Lines        2641     2641              
==========================================
+ Hits         2096     2100       +4     
+ Misses        454      450       -4     
  Partials       91       91              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[renovate]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 2 additional dependencies were updated

Details:

Package	Change
golang.org/x/sys	v0.29.0 -> v0.30.0
golang.org/x/text	v0.21.0 -> v0.22.0

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[eternal-flame-AD]

There is a coverage bug here (toolchain issue?).

This line causes a lot of coverage to be missing even if the toolchain is already 1.24.0. But go.mod reference says it 'Only takes effect when the module is the main module and the default toolchain is older than the suggested toolchain.' so I understand it should be a no-op?

I am investigating more on this.