Joel Gallant

Release notes: https://github.com/openpgpjs/openpgpjs/releases/tag/v5.0.0 I believe this would necessitate a breaking change in app-config's API, unfortunately, because we do re-export `Key` in a couple places. Right now we lock all subpackages...

> On a side note, I'd like to leave a suggestion for maybe putting all the encryption functionality on a separate package. > If you don't need encryption, it will...

I'm updating some today, although my time is stretched very thin lately. Version 3 is still somewhere on my bucket list, but I wouldn't want to get anyone's hopes up.

Could you `yarn why node-fetch`? I believe this is from quicktype-core -> isomorphic-fetch, which we can't update w/o a breaking change. We don't use the XHR request part of that...

Going to say this should be done with #131

I think there's still value in a `qa+staging` or `qa|staging` syntax in `$env`. Reopening. Partially, I think we should reserve this syntax by adding a deprecation warning for environment names...

Note that it's possible to do this (now) with at the root level of the app-config file: ```yaml $env: default: {} qa: $extendsSelf: env: staging select: . # any qa...

Interesting, that makes enough sense. FWIW if you need a workaround, you can of course just `touch .app-config.yml`. In terms of implementing this suggestion, I think we'll need to catch...

> If the above is true, have we considered using the `$env` extension somehow to be more idiomatic with other app-config patterns? (asking this in full naivety - maybe this...

> Thoughts on calling this default instead of none? Eg. in situations where we do set an environment, but that environment doesn't exist under teamMembers. This is already the case,...