chore: update dependencies

[rm-hull]

Update various project dependencies to their latest versions to ensure
compatibility, security, and performance improvements.

[github-actions]

	Tests	Passed ✅	Skipped	Failed
JUnit Test Report	36 ran	36 passed	0 skipped	0 failed

Test	Result
JUnit Test Report
postcode-polygons/internal.TestDecompressFeatureCollection_Success	✅ passed
postcode-polygons/internal.TestDecompressFeatureCollection_FileNotFound	✅ passed
postcode-polygons/internal.TestDecompressFeatureCollection_InvalidBZ2	✅ passed
postcode-polygons/internal.TestCompressFeatureCollection_Success	✅ passed
postcode-polygons/internal.TestCompressFeatureCollection_ErrorOnCreate	✅ passed
postcode-polygons/internal.TestCompressFeatureCollection_And_DecompressFeatureCollection_RoundTrip	✅ passed
postcode-polygons/routes.TestCodePointSearch_BadBBox	✅ passed
postcode-polygons/routes.TestCodePointSearch_TooBig	✅ passed
postcode-polygons/routes.TestCodePointSearch_InternalError	✅ passed
postcode-polygons/routes.TestCodePointSearch_Success	✅ passed
postcode-polygons/routes.TestPolygonSearch_BadBBox	✅ passed
postcode-polygons/routes.TestPolygonSearch_InternalError	✅ passed
postcode-polygons/routes.TestPolygonSearch_Success	✅ passed
postcode-polygons/routes.TestPolygonSearch_PolygonNotFound	✅ passed
postcode-polygons/routes.TestPolygonSearch_PolygonRepoError	✅ passed
postcode-polygons/routes.TestParseBBox/valid	✅ passed
postcode-polygons/routes.TestParseBBox/too_few_parts	✅ passed
postcode-polygons/routes.TestParseBBox/not_numbers	✅ passed
postcode-polygons/routes.TestParseBBox/min_greater_than_max	✅ passed
postcode-polygons/routes.TestParseBBox	✅ passed
postcode-polygons/routes.TestIsTooBig/not_too_big	✅ passed
postcode-polygons/routes.TestIsTooBig/too_wide	✅ passed
postcode-polygons/routes.TestIsTooBig/too_high	✅ passed
postcode-polygons/routes.TestIsTooBig	✅ passed
postcode-polygons/spatial-index.TestNewCodePointSpatialIndex_Success	✅ passed
postcode-polygons/spatial-index.TestNewCodePointSpatialIndex_BadZip	✅ passed
postcode-polygons/spatial-index.TestSearch	✅ passed
postcode-polygons/spatial-index.TestSearchIter_InvalidBounds	✅ passed
postcode-polygons/spatial-index.TestLen	✅ passed
postcode-polygons/spatial-index.Test_fromCodePointCSV	✅ passed
postcode-polygons/spatial-index.TestParseCSV_WithHeader_Success	✅ passed
postcode-polygons/spatial-index.TestParseCSV_WithoutHeader_Success	✅ passed
postcode-polygons/spatial-index.TestParseCSV_ParseError	✅ passed
postcode-polygons/spatial-index.TestParseCSV_MalformedLine	✅ passed
postcode-polygons/spatial-index.TestParseCSV_HeaderReadError	✅ passed
postcode-polygons/spatial-index.TestParseCSV_YieldStopsEarly	✅ passed

• View JUnit Test Report

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the project's dependencies to their latest versions, enhancing compatibility, security, and performance by upgrading both direct and indirect dependencies in the go.mod and go.sum files.

Highlights

• Dependency Updates: This pull request updates multiple Go dependencies in the go.mod and go.sum files to their latest versions.
• Security and Performance: The updates aim to improve compatibility, security, and performance of the project.
• Indirect Dependencies: Several indirect dependencies were updated, including github.com/bytedance/gopkg, github.com/goccy/go-json, github.com/klauspost/compress, github.com/montanaflynn/stats, github.com/oapi-codegen/runtime, go.yaml.in/yaml/v2, golang.org/x/arch, golang.org/x/crypto, golang.org/x/net, and golang.org/x/sync.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coveralls]

Pull Request Test Coverage Report for Build 23413185106

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 45.624%

---

Totals
Change from base Build 23361051368:	0.0%
Covered Lines:	245
Relevant Lines:	537

---

💛 - Coveralls

[gemini-code-assist]

Code Review

This pull request updates several indirect Go module dependencies. The changes consist of patch and minor version bumps, which is a good practice for keeping the project up-to-date with bug fixes, security patches, and performance improvements. Given the nature of these changes, the primary validation will come from the automated test suite in CI to ensure no regressions or breaking changes have been introduced. The changes in go.mod and go.sum appear to be correctly generated.