use caret for burner-connector versioning

[technophile-04]

Description

For some wired reason, when if we use ~ for burner-connector it give me "module not found error"

, using ^ does seem to solve that problem

[rin-st]

Strange, ~ doesn't work for me too.

Noticed that on gh last burner-connector release on the repo is 0.0.3, but on npm is 0.04. How does this work? Also I think it should have a version on package json.

Create-eth also has a version mismatch (0.0.39 gh vs 0.0.35 npm), but it's another story

[technophile-04]

Noticed that on gh last burner-connector release on the repo is 0.0.3, but on npm is 0.04. How does this work?

Ohh actually gh is not showing 0.0.4 tags release because, yesterday instead of creating PR and publishing version with github bot we published the version directly through CLI.

@carletex could you please run git push --follow-tags on burnerConnector repo, I think this will publish the tags to github repo too as mentioned here, I think we forgot to do this step yesterday my bad.

Also I think it should have a version on package json.

Ohh yeah we do have a version in pacakge.json here, maybe you were looking at root of monorepo ?

Create-eth also has a version mismatch (0.0.39 gh vs 0.0.35 npm), but it's another story

Strange, for me both are at same version

GH	npm

---

Merging this, just tested it out. Thanks all !!

[rin-st]

Ohh yeah we do have a version in pacakge.json here, maybe you were looking at root of monorepo ?

Got it, thanks!

Strange, for me both are at same version

Sorry, for some reason it was a version inside URL 😄

[carletex]

@carletex could you please run git push --follow-tags on burnerConnector repo, I think this will publish the tags to github repo too as mentioned here, I think we forgot to do this step yesterday my bad.

Just did! @technophile-04