@limited-rainbow-51650 I had to laugh so hard, when I saw THIS:

Me too. 😄

Perhaps we should configure soem `pre-commit`rules for this. Great tool BTW. Did you ever use it in a project?

Maybe it’s a good thing you try it yourself. One note: don’t use signed git tags for now. (git tag cli arg

--no-sign

)

Ummm ... Didn't get you. I created the v0.0.6 tag by myself, what created the first successful publication of the provider. But I mean: who triggers the pipeline in the Registry repo again. Or are the Registry CI connected to the different provider repos and fire when a new release tag in he provider repo is defined?

There is a cron job which checks the provider repos for new releases. When a new release is available, a PR is auto-created in the registry repo which is then processed by one of the engineering teams at Pulumi. So nothing to be done by any of us

@limited-rainbow-51650 thanks for elaborating on this 👍🏼

Last week, I always had the args reversed:

git tag v0.0.x -m "Some message" --no-sign

Ugh 😞 Didn't expect that the sequence of parameters to the

tag

command is of any relevance. Thanks for the tip 👍🏼

It shouldn’t, according the docs. Not sure what would happen if I would have changed the order of the args on my system. Was just reporting that I had them reversed last week. 😉

Next time I'll add

--no-sign

at the end of the command like you did. We'll see then what happens