Udit Vasu

@bagrip You can export the final environment variables file before completing a run using the `--export-environment ` option. In order to update the same input file, run: ```console $ newman...

@k0enf0rNL As mentioned above [#1679 (comment)](https://github.com/postmanlabs/newman/issues/1679#issuecomment-424324313), this issue is about syncing the updated environment variables with Postman Cloud.

@dependabot ignore this dependency

@dependabot rebase

Closing in favor of #1332

Fixed by #1332

This is fixed in Newman v6.1.2. Thank you @yardenshoham for the fix. 🙌🏻

I verified using [this test](https://github.com/sindresorhus/file-type/commit/d86835680f4cccbee1a60628783c36700ec9e254#diff-13876b4beb64b9f156474dc78f9c923952a7ca210d4507b6b3135bbe244f8a60R547) that `[email protected]` is not affected by the reported CVE, because the vulnerable code doesn't exist in this version. I don't see this getting flagged using...

@deividas-pelakauskas Thanks for the feature request. Collections with WebSocket and gRPC requests have limited functionality for now. We are tracking this internally. Can you also share your workflow with the...

@IsrraBanton That's by design and you can know more about variable sessions here: https://blog.getpostman.com/2018/08/09/sessions-faq/ Changing this to feature request and updating the issue title accordingly.