Fix to release workflow

[zain-sohail]

In reference to #285

Some comments in #280 are also addressed here

[coveralls]

Pull Request Test Coverage Report for Build 6943253162

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 90.586%

---

Totals
Change from base Build 6942939676:	0.0%
Covered Lines:	5562
Relevant Lines:	6140

---

💛 - Coveralls

[rettigl]

We can try it out, not sure I understand if it should work or not.

[rettigl]

Did not work, was it because the version was out of date with pipy?
I'd suggest to make a new main release 1.6, how do I do that?

[zain-sohail]

Did not work, was it because the version was out of date with pipy? I'd suggest to make a new main release 1.6, how do I do that?

It's because last time the publish job worked but the bump version job didn't. So next time the bump job would be a version behind. Easy fix is to just bump the version once manually.

git tag v0.1.6 and pushing the tag will trigger the workflow to update to version 0.1.6

[rettigl]

Still not working

[zain-sohail]

Still not working

Fixed now.
I also included should include paths-ignore pyproject.toml to all workflows since otherwise they will execute twice for no reason. Once for actual PR and once after bumping version.

[rettigl]

Thanks, great. Also great development guide. Do we have some mechanism to restrict anyone from creating new releases?
When I pushed my created tag, it pushed all kind of tags with version numbers >0.2, no idea where they came from. Can you clean that up?

[zain-sohail]

Thanks, great. Also great development guide.

Thanks. Also thinking to extend for general contributions but also great if we extend it for developing loaders, as an API reference is clearly not enough.

Do we have some mechanism to restrict anyone from creating new releases?

Ok just added v* to protected tags. But currently, it's just a very few of us with write access to the repo. But still a good idea.

Do we have some mechanism to restrict anyone from creating new releases? When I pushed my created tag, it pushed all kind of tags with version numbers >0.2, no idea where they came from. Can you clean that up?

The other versions were my tests on testpypi. You can see those are from a few days ago. I will remove them