Canary release publishing is not setting correct canary version on @redwoodjs dependencies

Canary releases are successfully being published for all packages. However, some @redwoodjs packages are not being installed at the canary release version. Instead, they are at the current stable release 0.19.2.

Reproducing the Issue

• run yarn rw upgrade -t canary in a Redwood project
• inspecting package.json in each of the main installed packages (e.g. node_modules/@redwoodjs for core, api, auth, forms, router, and web) shows the correct canary version for the package as well as for each @redwoodjs dependency
• however, the package.json shows v0.19.2 for the installed packages cli, dev-server, eslint-config,eslint-plugin-redwood, internal, structure, testing

Diagnosis

yarn.lock is showing some funky versions.

@redwoodjs/core is correct:

"@redwoodjs/core@^0.19.2-canary.45":
  version "0.19.2-canary.45"
...

@redwoodjs/cli includes the +hash, which means semver resolves to 0.19.2:

"@redwoodjs/cli@^0.19.2-canary.45+f354b564":
  version "0.19.2"

It’s most likely this started after I released the .2 patch. Which means it might resolve once v0.20.0 is released.

Workaround

For now, the workaround is manually installing the packages at the correct canary version. So after running yarn rw upgrade -t canary to upgrade to 0.19.2-canary.45, for example, you’d then need to run:

yarn add -W @redwoodjs/cli@0.19.2-canary.45 @redwoodjs/dev-server@0.19.2-canary.45  @redwoodjs/eslint-config@0.19.2-canary.45 @redwoodjs/eslint-plugin-redwood@0.19.2-canary.45  @redwoodjs/internal@0.19.2-canary.45  @redwoodjs/structure@0.19.2-canary.45  @redwoodjs/testing@0.19.2-canary.45 

Yeah, I know… 🤢

[AntonioMeireles]

fwiw, afaict, alternatively placing snippet bellow inside top level’s package.json will do the trick for now …

  "resolutions": {
    "@redwoodjs/cli": "0.19.2-canary.52",
    "@redwoodjs/web": "0.19.2-canary.52",
    "@redwoodjs/dev-server": "0.19.2-canary.52",
    "@redwoodjs/eslint-config": "0.19.2-canary.52",
    "@redwoodjs/eslint-plugin-redwood": "0.19.2-canary.52",
    "@redwoodjs/internal": "0.19.2-canary.52",
    "@redwoodjs/structure": "0.19.2-canary.52",
    "@redwoodjs/testing": "0.19.2-canary.52"
  }

[thedavidprice]

turns out the sha is supposed to be included here, but npm strips it out

^^ Ah, very interesting!

We did resolve this back in October. But good to know as there are still occasional hiccups.