Skip to content

fix(deps): update module github.com/labstack/echo/v4 to v5#169

Open
netic-renovate[bot] wants to merge 1 commit intomainfrom
renovate/github.com-labstack-echo-v4-5.x
Open

fix(deps): update module github.com/labstack/echo/v4 to v5#169
netic-renovate[bot] wants to merge 1 commit intomainfrom
renovate/github.com-labstack-echo-v4-5.x

Conversation

@netic-renovate
Copy link
Contributor

@netic-renovate netic-renovate bot commented Jan 20, 2026

This PR contains the following updates:

Package Change Age Confidence
github.com/labstack/echo/v4 v4.15.0v5.0.4 age confidence

Release Notes

labstack/echo (github.com/labstack/echo/v4)

v5.0.4

Compare Source

Enhancements

v5.0.3

Compare Source

Security

  • Fix directory traversal vulnerability under Windows in Static middleware when default Echo filesystem is used. Reported by @​shblue21.

This applies to cases when:

  • Windows is used as OS
  • middleware.StaticConfig.Filesystem is nil (default)
  • echo.Filesystem is has not been set explicitly (default)

Exposure is restricted to the active process working directory and its subfolders.

v5.0.2

Compare Source

Security

  • Fix Static middleware with config.Browse=true lists all files/subfolders from config.Filesystem root and not starting from config.Root in #​2887

v5.0.1

Compare Source

v5.0.0

Compare Source

Echo v5 is maintenance release with major breaking changes

  • Context is now struct instead of interface and we can add method to it in the future in minor versions.
  • Adds new Router interface for possible new routing implementations.
  • Drops old logging interface and uses moderm log/slog instead.
  • Rearranges alot of methods/function signatures to make them more consistent.

Upgrade notes and v4 support:

  • Echo v4 is supported with security* updates and bug fixes until 2026-12-31
  • If you are using Echo in a production environment, it is recommended to wait until after 2026-03-31 before upgrading.
  • Until 2026-03-31, any critical issues requiring breaking v5 API changes will be addressed, even if this violates semantic versioning.

See API_CHANGES_V5.md for public API changes between v4 and v5, notes on upgrading.

Upgrading TLDR:

If you are using Linux you can migrate easier parts like that:

find . -type f -name "*.go" -exec sed -i 's/ echo.Context/ *echo.Context/g' {} +
find . -type f -name "*.go" -exec sed -i 's/echo\/v4/echo\/v5/g' {} +

macOS

find . -type f -name "*.go" -exec sed -i '' 's/ echo.Context/ *echo.Context/g' {} +
find . -type f -name "*.go" -exec sed -i '' 's/echo\/v4/echo\/v5/g' {} +

or in your favorite IDE

Replace all:

  1. echo.Context -> *echo.Context
  2. echo/v4 -> echo/v5

This should solve most of the issues. Probably the hardest part is updating all the tests.


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 has been generated by Renovate Bot.

@netic-renovate netic-renovate bot added the major-update Signal this PR is a major update label Jan 20, 2026
@netic-renovate netic-renovate bot force-pushed the renovate/github.com-labstack-echo-v4-5.x branch 2 times, most recently from 0478297 to 591ce84 Compare February 2, 2026 06:52
@netic-renovate netic-renovate bot force-pushed the renovate/github.com-labstack-echo-v4-5.x branch 3 times, most recently from 374f41b to eb64253 Compare February 9, 2026 06:53
@netic-renovate netic-renovate bot force-pushed the renovate/github.com-labstack-echo-v4-5.x branch 3 times, most recently from 80029a4 to 3ad7c84 Compare February 16, 2026 07:49
@netic-renovate netic-renovate bot force-pushed the renovate/github.com-labstack-echo-v4-5.x branch from 3ad7c84 to 8f8dc42 Compare February 17, 2026 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

major-update Signal this PR is a major update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants

Comments