CI Canary publishing is failing

[thedavidprice]

Starting with #2637, our automated canary publishing has been failing. I don't see anything suspicious in the PR #2637 but would appreciate others taking a look.

The related GH Workflow file is here. And the script it runs is here.

The reason for failing seems to be that Lerna cannot find the most recent version tag. It’s effectively trying to publish null-canary.51 instead of 0.32.3-canary.51:

...
Found 16 packages to publish:
lerna info auto-confirmed 
 - @redwoodjs/api-server => null-canary.58+91537497
 - @redwoodjs/api => null-canary.58+91537497
 - @redwoodjs/auth => null-canary.58+91537497
...
lerna info publish Publishing packages to npm...
lerna ERR! Error: Invalid tag name "^null-canary.58+91537497": Tags may not have any characters that encodeURIComponent encodes.
...

We run this command to fetch tags:

• git fetch --depth=1 origin +refs/tags/*:refs/tags/*

I tested the command locally and confirmed it's returning "null" (origin is set to the GitHub Framework repo):

redwoodjs-redwood git:(main)$ git fetch --depth=1 origin +refs/tags/*:refs/tags/*
no matches found: +refs/tags/*:refs/tags/*

The git tags do exist, as confirmed with git tag. Not sure how to diagnose further or fix.

[thedavidprice]

^^ @peterp @dac09

[thedavidprice]

ok, this seems to be resolved! (see screenshot below) I had to bump the latest Tag. As long as we correctly use git tag -am to create annotated version tags going forward I believe we are gtg. @peterp please take a look at the related PR and confirm.