Are @aws-sdk packages being published in the correct order?

[jedwards1211]

I just got some missing version errors when trying to install some packages that depend on the AWS SDK.

The issue is no longer reproducible because it seems that new versions @aws-sdk/middleware-user-agent, @aws-sdk/core just got released. Are you publishing packages in toposorted order so that new versions of dependencies are published before new versions of dependents?

Maybe it's an NPM issue? Recently I've been getting 404s trying to install some of my own packages for a short time immediately after publishing them.

$ pnpm i @jcoreio/deploy-ssl-certs-api
ERR_PNPM_NO_MATCHING_VERSION  No matching version found for @aws-sdk/middleware-user-agent@^3.972.8 while fetching it from https://registry.npmjs.org/

This error happened while installing the dependencies of @jcoreio/deploy-ssl-certs-api@4.0.2
 at @aws-sdk/client-api-gateway@3.988.0

The latest release of @aws-sdk/middleware-user-agent is "3.972.7".

$ npm view @aws-sdk/client-api-gateway@^3.988.0

@aws-sdk/client-api-gateway@3.988.0 | Apache-2.0 | deps: 41 | versions: 563
...

dependencies:
@aws-crypto/sha256-browser: 5.2.0                 @aws-sdk/middleware-host-header: ^3.972.3         @aws-sdk/middleware-user-agent: ^3.972.8
...

$ npm view @aws-sdk/middleware-user-agent versions
[
  ...
  '3.972.4',       '3.972.5',       '3.972.6',       '3.972.7'
]

# trying again...
$ pnpm i @jcoreio/deploy-ssl-certs-api
 ERR_PNPM_NO_MATCHING_VERSION  No matching version found for @aws-sdk/core@^3.973.8 while fetching it from https://registry.npmjs.org/

This error happened while installing the dependencies of @jcoreio/deploy-ssl-certs-api@4.0.2
 at @aws-sdk/client-api-gateway@3.988.0

The latest release of @aws-sdk/core is "3.973.7".