Skip to content

1.8.0 broke environment resolving #497

@rbtcollins

Description

@rbtcollins

I haven't yet dug into why, but it is an API break, so if kong is following semver, please consider pulling 1.8, and re-tagging as 2.0. That would avoid renovate/dependabot autoupdating this everywhere.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions