chore(deps): update module github.com/labstack/echo/v5 to v5.3.1 #44
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
github_actions
go
good first issue
help wanted
invalid
npm
onice
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
maxpeterkaya/web-proxy!44
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/github.com-labstack-echo-v5-5.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v5.0.4→v5.3.1Release Notes
labstack/echo (github.com/labstack/echo/v5)
v5.3.1Compare Source
Fixes
Enhancements
Anygodoc to reflect true arbitrary-method matching by @hyorimitsu in #3046v5.3.0Compare Source
Logic changes
PR #2996 revert back to
v4behavior for a group registering implicit 404 handlers.If you do not want this behavior, can do not want implicit 404 handlers for groups, use:
some other noteworthy echancements:
Enhancements
v5.2.1Compare Source
Security
Make serving static file releated methods and middleware not unescape path by default - so how the way Router interprets paths and Static methods/middleware is consistent.
Given following situation:
Then requests to
/admin%2fprivate.txtwould not be matched toGET /admin/*route (routing does not look unescaped path) and static file serving will use unescaped path to serve the file.Note: this way of "guarding" subfolders will never work for for paths like
/assets/../admin%2fprivate.txtwhich willpath.Clean("/assets/../admin%2fprivate.txt")to/admin/private.txtand are servable if static file serving is configured to unescape paths.If you want to guard routes - use middlewares on
Static*methods and beforeStaticmiddleware.Closes GHSA-vfp3-v2gw-7wfq more completely: the previous fix (#3009) rejected explicitly encoded
separators at the handler level; this patch makes the no-unescape behavior the default so new configurations are safe without extra opt-out steps.
What changed:
DisablePathUnescaping(onStaticConfigandStaticDirectoryHandlerConfig) is deprecated and replaced byEnablePathUnescaping(defaultfalse). Path unescaping is now opt-in.What this protects: With
EnablePathUnescaping: false(new default), encoded separators (%2F,%5C) are never decoded before routing or file lookup, so they cannotbypass route-level authentication or other middleware guards.
What this does NOT protect: Serving a directory with
Static,StaticFS, orStaticDirectoryHandlerexposes its entire subtree. Sibling routes are not a reliableACL boundary — attach authorization middleware directly to the static mount, or serve sensitive sub-trees under separate guarded routes.
Breaking change / migration: If you serve files whose names contain URL-encoded characters (e.g.,
/hello%20world.txt→hello world.txt), you must now opt in:Full Changelog: https://github.com/labstack/echo/compare/v5.2.0...v5.2.1
v5.2.0Compare Source
Security
Fixes GHSA-vfp3-v2gw-7wfq: an encoded path separator (
%2For%5C) in a static file URL could bypass route-level middleware (e.g. authentication on a sibling route) and disclose static files. BothStaticDirectoryHandler/StaticFSand theStaticmiddleware are affected. Thanks to @a-tt-om and @oran-gugu for reporting.Enhancements
New Contributors
Full Changelog: https://github.com/labstack/echo/compare/v5.1.1...v5.2.0
v5.1.1Compare Source
Security
Context.Scheme()should validate values taken from header by @aldas in #2953Thanks to @shblue21 for reporting this issue.
Enhancements
v5.1.0Compare Source
Security
This change does not break the API contract, but it does introduce breaking changes in logic/behavior.
If your application is using
c.RealIP()beware and read https://echo.labstack.com/docs/ip-addressv4behavior can be restored with:Enhancements
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
chore(deps): update module github.com/labstack/echo/v5 to v5.1.0to chore(deps): update module github.com/labstack/echo/v5 to v5.1.141677431e9to16beeb8162chore(deps): update module github.com/labstack/echo/v5 to v5.1.1to chore(deps): update module github.com/labstack/echo/v5 to v5.2.016beeb8162to051c98626bchore(deps): update module github.com/labstack/echo/v5 to v5.2.0to chore(deps): update module github.com/labstack/echo/v5 to v5.2.1051c98626btof24d472d5af24d472d5atoa8a16800d0chore(deps): update module github.com/labstack/echo/v5 to v5.2.1to chore(deps): update module github.com/labstack/echo/v5 to v5.3.0ℹ️ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the
go getcommand, which resulted in the following additional change(s):Details:
golang.org/x/cryptov0.47.0->v0.54.0golang.org/x/netv0.49.0->v0.57.0golang.org/x/sysv0.40.0->v0.47.0golang.org/x/textv0.33.0->v0.40.0golang.org/x/timev0.14.0->v0.15.0a8a16800d0to074ac99091chore(deps): update module github.com/labstack/echo/v5 to v5.3.0to chore(deps): update module github.com/labstack/echo/v5 to v5.3.1074ac99091toe6a455f315View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.