Update the core tools to support v0.7

[bfabio]

Tracking issue to update the core tools to the upcoming v0.7 version.

• Adapt publiccode-parser-go implementation (feat: support publiccode.yml 0.7 italia/publiccode-parser-go#395)
  • Release a new version
• Adapt publiccode-parser-php
  • Release a new version
• publiccode-parser-action
  • Release a new version
• Adapt publiccode-parser-gitlab-ci
• Adapt publiccode-crawler
  • Release a new version
• Update https://github.com/SchemaStore/schemastore (Update publiccode.yml schema to version 0.5.0 SchemaStore/schemastore#5065)
• Update the CHANGELOG
• Make an announcement in Discussions

[bfabio]

I can't merge my own PRs anymore on italia/publiccode-parser-go and maybe other ones.

My access was reduced to write level, so I can no longer bypass the rule on main that requires a review from someone other than the author. I'm the only one working on the code, so there's no one able to approve them.

I can still merge dependabot's PRs, just not mine.

So what do we do? There are PRs waiting, eg:

• feat: support publiccode.yml 0.7 italia/publiccode-parser-go#395
• Support publiccode.yml v1 italia/publiccode-parser-go#396
• ci: make builds reproducible italia/publiccode-parser-go#388
• ci: pin Go toolchain from go.mod and add go mod verify italia/publiccode-parser-go#389

and a new version to support, and none of it can move right now, not even this issue, because everything else depends on the parser.

One option is to move the repos to the publiccodeyml org to better reflect where the actual maintenance work is happening.

@italia/developers @astagi @mfortini @Lorezz @peppelinux @tensor5 @valeriocomo @AlexPalaz

[Lorezz]

Access has been reduced from admin to maintainer, mainly because the changes broke or caused problems on the front end of the production software catalog, primarily the crawler. I've scheduled a meeting with the other devs to decide what to do: whether to divide the tasks by tool and verify the pr ourselves or give you back your admin privileges. In the meantime, we've moved to a stable release to avoid these problems. We tried to involve you in a couple of meetings to discuss this and other issues, but you preferred to address the issues directly, so here are the answers to your questions.

[Lorezz]

Together we choose to give you the ability to continue working on your pull reqs, removing the validation lock. You should be able to merge on all the projects now, also on the crawler and api. We would like to be involved anyway it the further developments.