Kevin Ross

Thanks @laughedelic, it looks like `auto shipit --dry-run --quiet` can resolve the deterministic version, so the only question would be how to get `shipit` to allow the arg version to...

~~It looks like `publishFullRelease()` already accepts `{useVersion}` to override, but that is not used for `canary|next` functions. I'm still familiarizing myself with the code but it may be as simple...

It looks like (from `auto.ts`) that `shipit`, `release` and `latest()` allow `--use-version` as an option, though I think the behavior is not necessarily well defined as it is only included...

`useVersion || bump` (effectively) is in a lot of places. I suggest in the implementation this gets resolved early in each of the public interfaces and is taken as-is, instead...

Ok, so while this is not documented for `shipit`, `--use-version` does exist. It appears that I can get satisfactory results as-is (npm plugin) with: 1. Determine what shipit would use...

So I did get this to work with the existing code, though it is a bit of a workaround. Here is how it worked: First, get the shipit version and...

I'm extremely well versed in mui 4.x, we are _just now_ moving to 5.x. I want to say as a 5.x novice that `slots` and `slotProps` are not well defined...

I'm a comitter on react-apollo (but not an Apollo employee) and have some thoughts. @trojanowski please dm me on the Apollo slack. I do think there is an opportunity to...

All of this sounds good. The only thing I want to get done sooner than later is rollup bundles for esm and cjs, in-line with the strategy already merged in...

@trojanowski primarily to avoid hidden interop problems mixing index and path imports introduce - it's the easiest way (and a nasty problem). - https://github.com/dmtrKovalenko/material-ui-pickers/pull/695#issuecomment-430777307 - https://github.com/apollographql/apollo-client/pull/4261#issuecomment-451286899 - https://github.com/apollographql/apollo-client/pull/4401#issuecomment-459929623