Skip to content

Update dotenv-expand (again) to 5.x to resolve previously closed issues #7577

Closed

Activity

  1. heyimalex commented on Sep 9, 2019

    @heyimalex
    Contributor

    You're sure this is still happening? The bug was in dotenv, not dotenv-expand, and we're currently pinned to dotenv 6.2.0 so that fix definitely landed.

  2. kireerik commented on Sep 10, 2019

    @kireerik
    ContributorAuthor

    Yes, I am.

    The issue was in dotenv-expand: #4002 (comment)

    This is the exact commit with the resolution in the dotenv-expand repository: dotenvx/dotenv-expand@f012c66

  3. kireerik commented on Sep 10, 2019

    @kireerik
    ContributorAuthor
  4. kireerik commented on Sep 10, 2019

    @kireerik
    ContributorAuthor

    dotenvx/dotenv-expand#18 (comment)

    @heyimalex I found an open pull request: #7531

    This would solve the issue.

  5. heyimalex commented on Sep 10, 2019

    @heyimalex
    Contributor

    Forgive me :)

  6. locked and limited conversation to collaborators on Sep 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions