ci: Automate the release process

[janbuchar]

• closes Automatically generate changelog from the commit messages #241

[vdusek]

Great, but please update also:

• .pre-commit-config.yaml - rm legacy checks,
• Makefile - rm legacy commands,
• and CONTRIBUTING.md - basically just copy it from Crawlee and make necessary adjustments.
  • Which will also close #288.

[vdusek]

We're removing run_release.yaml in the client, but leaving it in here. Is that correct?

[vdusek]

All our pipeline files so far follow a verb-based naming style (build_and_deploy_docs.yaml, check_pr_title.yaml, run_code_checks.yaml, update_new_issue.yaml). The release pipelines, however, are named release and pre_release. While I'm not insisting we have to use verb-style naming—I'm not sure what the best convention is—but please keep it consistent.

[B4nan]

but release is also verb, right? :]

[janbuchar]

All our pipeline files so far follow a verb-based naming style (build_and_deploy_docs.yaml, check_pr_title.yaml, run_code_checks.yaml, update_new_issue.yaml). The release pipelines, however, are named release and pre_release. While I'm not insisting we have to use verb-style naming—I'm not sure what the best convention is—but please keep it consistent.

but release is also verb, right? :]

apify/apify-client-python#278 (comment)

[janbuchar]

We're removing run_release.yaml in the client, but leaving it in here. Is that correct?

It isn't! Thank you!

[vdusek]

Great job! Thanks