vendor: github.com/moby/sys/sequential v0.7.0

[thaJeztah]

• update minimum go version to 1.24
• use os.OpenFile with O_FILE_FLAG_SEQUENTIAL_SCAN on Go 1.26+

- What I did

- How I did it

- How to verify it

- Human readable description for the release notes

- A picture of a cute animal (not mandatory but encouraged)

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[docker-agent]

Assessment: 🟢 APPROVE

This PR vendors github.com/moby/sys/sequential v0.7.0, splitting the Windows implementation into two build-tag-gated files:

• sequential_windows_go126.go (//go:build windows && go1.26): uses os.OpenFile with windows.O_FILE_FLAG_SEQUENTIAL_SCAN — a new fast path for Go 1.26+.
• sequential_windows_pre126.go (//go:build windows && !go1.26): retains the existing manual CreateFile-based implementation for Go < 1.26.
• sequential_windows.go: correctly contains only shared API wrappers and CreateTemp helpers — no symbol conflicts.
• sequential_unix.go: CreateTemp correctly delegates to os.CreateTemp.
• vendor.mod / vendor.sum / vendor/modules.txt are consistent with the new v0.7.0 version.

No high- or medium-severity issues found. A few low-severity observations (informational only):

1. The go1.26 build tag targets a Go version not yet released; the new fast path is effectively dormant until Go 1.26 ships — this is intentional and expected for forward-compatible vendoring.
2. The perm parameter is passed through to os.OpenFile in the go1.26 path but silently ignored in the pre-1.26 path (_); this is consistent with the pre-existing behavior and the constraints of the CreateFile API.
3. The pre-1.26 path's silent perm-ignore is a pre-existing limitation carried forward, not a regression.

The implementation is correct and the split is clean.

[thaJeztah]

@docker-agent go1.26 has been released for some months now; your information looks severely outdated