Ivan

Hi @eloo-abi, thanks for reporting the issue. >i can access the filesystem in the same way as without a k6 archive Unfortunately, this is not how it is expected to...

>because in our scenario we want to share the code for our tests between our stages. but for sure we don't want to share our secrets and configurations between our...

Hi @po45ke95, do you get this error during the `docker build` command? I tried it and I don't get the same issue. Did you change the Dockerfile?

This is no required, this sounds like a misconfiguration on your machine. Please, provide a GitHub repository with a failing CI so we can debug the commands. Otherwise, this sounds...

I've updated the Dockerfile with the most recent k6, Alpine and Go version. A new `v0.5.0` version of the extension is available. Please, retry and if you continue to get...

Hi @jameshounshell, apologies for the delayed response; this issue unfortunately slipped off our radar. We don't think that incorporating this feature directly into k6 is correct. As you've noted, we...

If we don't have good reasons to keep it then I'm all for it, can we deprecate it just right now?

Hey @Codex- , thanks for sharing this! ❤️ I'm closing this issue since we already have a dedicated one open on the polyfill's repository. This documentation remains accessible for anyone...

Hey reviewers, please take another look :pray:

@olegbespalov did we reach some shared consensus on what should be the hotfix path? Because this was one of the changes introduced. So we might re-align this pull request with...