update links in jsonschema to current v1.0.0 docs

[6543]

we have a lot of wrong links in the jsonschema linking to old v0.15.0 paths

[6543]

it would also be nice if the 'current' version also has a prefix, this will make links not break that easily

now

• v0.15 -> https://woodpecker-ci.org/docs/0.15/...
• v1.0 -> https://woodpecker-ci.org/docs/...
• next -> https://woodpecker-ci.org/docs/next/...

desired

• v0.15 -> https://woodpecker-ci.org/docs/0.15/...
• v1.0 -> https://woodpecker-ci.org/docs/1.0/...
• next -> https://woodpecker-ci.org/docs/next/...

woodpecker/docs/docusaurus.config.js

Lines 215 to 227 in e01c478

	lastVersion: '1.0',
	versions: {
	'current': {
	label: 'Next',
	banner: 'unreleased',
	},
	'1.0': {
	label: '1.0.x',
	},
	'0.15': {
	label: '0.15.x',
	banner: 'unmaintained',
	},

[6543]

cc @anbraten ☝️ ?

[lonix1]

From my dupe issue:

Since #1948 was fixed, the json schema for .woodpecker.yml is out of date.

Consider this code: it ensures the logs show "clone" instead of "git" (as it was before the fix):

clone:
  clone:           # can be any word: "clone", "git" or whatever
    image: woodpeckerci/plugin-git:2.0.3

steps:
    # ...

But the schema only allows "git". If I use "clone" then I get an error in vscode: Property clone is not allowed.

I couldn't submit a PR because I'm unsure how to fix it - I can't just change "git" to "clone" as both are valid, as well as any other word.

[anbraten]

it would also be nice if the 'current' version also has a prefix, this will make links not break that easily

Using old links (with a prefix) however will send users to outdated docs (as most users will / should use the newest version anyways) this would introduce more new issues than actually solving.

[gedw99]

Mhh gen json Schema of golang types ?

Saw a package for it last week if there is any interest

[6543]

@gedw99 if you know the link again just comment it here :)