Force publish all packages on release

[cmdcolin]

This attempts to force publish all packages on each release, despite if they have not changed

This could be considered overkill and a reaction to the v1.3.4 to v1.3.5 release thing but it seemed to have resulted in a fair bit of confusion. It may be best to publish all every time. The only downside may be taking up a bit more npmjs.com server space

https://lerna.js.org/#command-publish

[cmdcolin]

This isn't tested but I believe this uses the documented lerna publish option in the right way

[codecov]

Codecov Report

Merging #2263 (ca34908) into main (dca2afa) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2263   +/-   ##
=======================================
  Coverage   62.81%   62.81%           
=======================================
  Files         495      495           
  Lines       22946    22946           
  Branches     5193     5193           
=======================================
  Hits        14414    14414           
  Misses       8265     8265           
  Partials      267      267           

Impacted Files	Coverage Δ
packages/core/util/index.ts	79.84% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dca2afa...ca34908. Read the comment docs.

[cmdcolin]

@garrettjstevens this is random but the jbrowse-web for example isn't published, this will still work for it though?

[garrettjstevens]

I think so, since that flag gets passed to the "version" command, which should update the version whether or not it's published.

[cmdcolin]

super...I figured somehow lerna was bumping jbrowse-web:)