-
Notifications
You must be signed in to change notification settings - Fork 0
fix(deps): update go minor/patch updates #37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
0f55432 to
7e03c68
Compare
7e03c68 to
b091840
Compare
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
b091840 to
1e9cb46
Compare
|
1e9cb46 to
f29f961
Compare
f29f961 to
fccffce
Compare
This PR contains the following updates:
v4.14.0→v4.15.0v7.0.97→v7.0.98v3.19.4→v3.19.5v0.34.3→v0.35.0v0.34.3→v0.35.0v0.34.3→v0.35.0v0.34.3→v0.35.0v0.34.3→v0.35.0Release Notes
labstack/echo (github.com/labstack/echo/v4)
v4.15.0Compare Source
Security
NB: If your application relies on cross-origin or same-site (same subdomain) requests do not blindly push this version to production
The CSRF middleware now supports the Sec-Fetch-Site header as a modern, defense-in-depth approach to CSRF
protection, implementing the OWASP-recommended Fetch Metadata API alongside the traditional token-based mechanism.
How it works:
Modern browsers automatically send the
Sec-Fetch-Siteheader with all requests, indicating the relationshipbetween the request origin and the target. The middleware uses this to make security decisions:
same-originornone: Requests are allowed (exact origin match or direct user navigation)same-site: Falls back to token validation (e.g., subdomain to main domain)cross-site: Blocked by default with 403 error for unsafe methods (POST, PUT, DELETE, PATCH)For browsers that don't send this header (older browsers), the middleware seamlessly falls back to
traditional token-based CSRF protection.
New Configuration Options:
TrustedOrigins []string: Allowlist specific origins for cross-site requests (useful for OAuth callbacks, webhooks)AllowSecFetchSiteFunc func(echo.Context) (bool, error): Custom logic for same-site/cross-site request validationExample:
PR: #2858
Type-Safe Generic Parameter Binding
Added generic functions for type-safe parameter extraction and context access by @aldas in #2856
Echo now provides generic functions for extracting path, query, and form parameters with automatic type conversion,
eliminating manual string parsing and type assertions.
New Functions:
PathParam[T],PathParamOr[T]QueryParam[T],QueryParamOr[T],QueryParams[T],QueryParamsOr[T]FormParam[T],FormParamOr[T],FormParams[T],FormParamsOr[T]ContextGet[T],ContextGetOr[T]Supported Types:
Primitives (
bool,string,int/uintvariants,float32/float64),time.Duration,time.Time(with custom layouts and Unix timestamp support), and custom types implementing
BindUnmarshaler,TextUnmarshaler, orJSONUnmarshaler.Example:
PR: #2856
DEPRECATION NOTICE Timeout Middleware Deprecated - Use ContextTimeout Instead
The
middleware.Timeoutmiddleware has been deprecated due to fundamental architectural issues that causedata races. Use
middleware.ContextTimeoutormiddleware.ContextTimeoutWithConfiginstead.Why is this being deprecated?
The Timeout middleware manipulates response writers across goroutine boundaries, which causes data races that
cannot be reliably fixed without a complete architectural redesign. The middleware:
http.TimeoutHandlerWhat should you use instead?
The
ContextTimeoutmiddleware (available since v4.12.0) provides timeout functionality using Go's standardcontext mechanism. It is:
Migration Guide:
Important Behavioral Differences:
Handler cooperation required: With ContextTimeout, your handlers must check
context.Done()for cooperativecancellation. The old Timeout middleware would send a 503 response regardless of handler cooperation, but had
data race issues.
Error handling: ContextTimeout returns errors through the standard error handling flow. Handlers that receive
context.DeadlineExceededshould handle it appropriately:Enhancements
minio/minio-go (github.com/minio/minio-go/v7)
v7.0.98Compare Source
What's Changed
New Contributors
Full Changelog: minio/minio-go@v7.0.97...v7.0.98
helm/helm (helm.sh/helm/v3)
v3.19.5: Helm v3.19.5Compare Source
Helm v3.19.5 is a patch release. Users are encouraged to upgrade for the best experience.
The community keeps growing, and we'd love to see you there!
Notable Changes
Installation and Upgrading
Download Helm v3.19.5. The common platform binaries are here:
This release was signed with
208D D36E D5BB 3745 A167 43A4 C7C6 FBB5 B91C 1155and can be found at @scottrigby keybase account. Please use the attached signatures for verifying this release usinggpg.The Quickstart Guide will get you going from there. For upgrade instructions or detailed installation notes, check the install guide. You can also use a script to install on any system with
bash.What's Next
Changelog
errors.Isinstead of string comp4a19a5b(Hidde Beydals)7a00235(Hidde Beydals)578564e(Ben Foster)kubernetes/api (k8s.io/api)
v0.35.0Compare Source
kubernetes/apiextensions-apiserver (k8s.io/apiextensions-apiserver)
v0.35.0Compare Source
kubernetes/apimachinery (k8s.io/apimachinery)
v0.35.0Compare Source
kubernetes/cli-runtime (k8s.io/cli-runtime)
v0.35.0Compare Source
kubernetes/client-go (k8s.io/client-go)
v0.35.0Compare Source
Configuration
📅 Schedule: Branch creation - "before 3am on sunday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.