Breaking changes before releasing 0.15.0

[anbraten]

To have less breaking changes in the future to not annoy users again and again, breaking changes should be part of the next version.

Some ideas

• replace DRONE_ env vars with WOODPECKER_ prefix Clean up config environment variables for server and agent #218
• drop Gitea basic auth support Remote Gitea drop basic auth support #365
• change config path resolution (.woodpecker/*.ymll -> .woodpecker.yml -> .drone.yml) Change pipeline config path resolution #299
• replace repository hooks setting with only allow PRs Remove push, tag and deployment webhook filters #281
• migrate to cert-magic Migrate to certmagic #360
• remove DRONE_ env vars passed to pipeline steps (only use CI_) Replace DRONE_ with CI_ variables in pipeline steps #427
• rename default paths /var/lib/drone => /var/lib/woodpecker and /drone => /woodpecker Change default paths to woodpecker #431
• rename default datasource: /var/lib/drone/drone.sqlite => /var/lib/woodpecker/woodpecker.sqlite Move sqlite to woodpecker #438
• rename prometheus namespace drone => woodpecker Change prometheus to woodpecker #439
• pipeline config changes
  • move plugin-settings in pipeline steps to some sub-setting like: pipeline.[step].settings and pass all KV options as PLUGIN_ Move plugin config to root.pipeline.[step].settings  #464
  • remove support for root.pipeline.[step].commands string values in favor of array lists
  • move root.skip_clone under root.clone.skip
  • move root.platform, root.branches, root.labels, root.runs_on, root.depends_on to root.when.xxx to match step filters Use when keyword for pipeline conditions #283 -> next release
  • make root.when and root.pipeline.[step].when an array of the current with items using the current settings to allow ORs non breaking & can move into next release
  • remove root.Cache and functionality in favor of plugins? - need more discussion

[ivictbor]

Very good point, this will also allow woodpecker users to create some public docs / bloogs / tootorials that might be compatible in future, at least for 0.15.* according to https://semver.org/