Calculate new release version

[niccokunzmann]

Linked issue

• Contributes to 7.3.0 checklist #1681 8.0 Checklist #1595

Description

• Calculate the new version reliably
• Add this to the release process docs
• add a scripts directory to collect all the scripts and Makefile helpers

Checklist

• I added a change log entry, following the instructions in Change log entry format.
• I followed icalendar's Artificial intelligence policy and disclosed my Responsible AI use in my commit messages, if applicable.
• I added or updated tests, if applicable.
• I ran and ensured all tests pass locally by following Run tests.
• I added or edited documentation as necessary, both as docstrings to be rendered in the API documentation and narrative documentation, following the Style guide.

Additional information

[github-actions]

Profile summary:

GitHub user: niccokunzmann
🟢 No concerns found with user's profile.
🟢 No concerns found with recent PR activity.
🟢 No concerns found with recent issue activity.

For a more detailed report, run `gh-profiler niccokunzmann`.

Full profile

GitHub user: niccokunzmann
🟢 No concerns found with user's profile.
   🟢 Account age: 15 years
   🟢 Profile information:
        name: Nicco Kunzmann
        blog: https://niccokunzmann.github.io
        location: Wales
        email: niccokunzmann@rambler.ru
        bio:
          Software is only a tool.
          Humanity, your house 🌍 is burning 
          🔥. 
          You can pay me if you would like me to prioritize issues on my repositories.
        mastodon: https://toot.wales/@niccokunzmann
      Empty fields: company
      Orgs: collective, OpenTechSchool, BP2012H1, Jugendhackt, fossasia, loklak, MasterprojectOpenStack2015, Freifunk-Potsdam, cdpoffline, HPIMakerKlub, coderdojo-de-ev, CodersOS, gruener-campus-malchow, KDD-OpenSource, CoderDojoDeutschland, fablabcb, spaceapi-community, HashTec-Potsdam, Brandenburger-Maker, yogdaan, Chaostreff-Potsdam, bioPunkKitchen, Freifunk-Wolfen, foss-wales, AmmanVMS, foss-fund, pycalendar

🟢 No concerns found with recent PR activity.
   5 PRs opened in the last 21 days.
      0 opened against repos the user owns.
      4 opened against repos in publicly associated orgs.
      1 opened against external repos.

   🟢 0 of 1 external PRs merged in the last 21 days.
   🟢 0 of 1 external PRs closed without merging in the last 21 days.

🟢 No concerns found with recent issue activity.
   12 new issues opened in the last 21 days.
      0 opened in repos the user owns.
      6 opened in repos in publicly associated orgs.
      6 opened in external repos.

   🟢 0 external issues closed as NOT_PLANNED.
   🟢 0 external issues opened with the same title.

[read-the-docs-community]

Documentation build overview

📚 icalendar | 🛠️ Build #34156016 | 📁 Comparing cb85a02 against latest (698624c)

  🔍 Preview build  

7 files changed · ± 7 modified

± Modified

• 404.html
• genindex.html
• contribute/index.html
• contribute/maintenance.html
• reference/changelog.html
• reference/api/icalendar.cal.todo.html
• _modules/icalendar/cal/todo.html

[stevepiercy]

I'd use either next or new, not both. Your call. What will your muscle memory prefer?

[stevepiercy]

@niccokunzmann I tried to create a patch on your fork, but I lack permission. Would you please add this to line 218 in docs/contribute/index.rst?

    All types except ``chore`` will be published.

    Changes in the ``breaking`` type will be released in the next major version.
    Changes in the ``feature`` type will be released in the next minor or major version.
    Changes for all other types will be released in the next version.

[stevepiercy]

Auto-merge is disabled because the ref is protected. Did someone change branch protection settings somewhere?

[stevepiercy]

@niccokunzmann I think it's this new ruleset that's blocking a force push by Admin and Maintainer roles https://github.com/collective/icalendar/settings/rules/21082190. Please have a look.