Update the release process to leverage GitHub Actions

[clintval]

Dependent on:

• Making GitHub a trusted PyPi publisher for this package: https://docs.pypi.org/trusted-publishers/adding-a-publisher/
• Allowing the use of conventional commits: https://www.conventionalcommits.org/en/v1.0.0/
  • If conventional commits are not used, this workflow still does the right thing!
• Updating the release process: https://github.com/fulcrumgenomics/pybedlite/wiki/Performing-a-Release
  • Move the process out of GitHub wiki and into CONTRIBUTING.md so it is easier to find
  • Process minimizes to:
    1. Manually and locally, bump the package version in the pyproject.toml to your desired SemVer
    2. Open a local branch, commit version bump changes, and then push to a remote branch
    3. Open a PR for your branch with a Git commit message like chore(release): bump to X.X.X
    4. Squash merge the PR
    5. Tag the new commit on main with the same SemVer, triggering a publish to PyPi and GitHub:
       • Source distribution
       • Binary distributions for all Python versions and architectures

The publish workflow looks like:

[nh13]

A few Qs, and we'll need to set up a few things before merge

[nh13]

LGTM

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.25%. Comparing base (b01175e) to head (b949f6d).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #37   +/-   ##
=======================================
  Coverage   95.25%   95.25%           
=======================================
  Files           8        8           
  Lines         674      674           
  Branches      119      119           
=======================================
  Hits          642      642           
  Misses         18       18           
  Partials       14       14           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[clintval]

@nh13 I might need some help allowing GitHub to be a PyPi publisher. Although I have access to release new versions of pybedlite on PyPi, I don't have authorization to manage the project:

Could you navigate to here and add a GitHub publisher with the following values?

• Owner: fulcrumgenomics
• Repository name: pybedlite
• Workflow name: publish.yml
• Environment name: pypi

[nh13]

Done, for pybedlite (not bedspec as per your link :P)

[clintval]

Done, for pybedlite (not bedspec as per your link :P)

Ah! My playground for ideas :)

[nh13]

Should this be ${{ matrix.python }}?

[clintval]

No, you really do just need a single and separate Python for building the wheels. It's OK to use 3.8 here. I think I've tried bumping it up, but you'll hit compatibility issues with cibuidwheel and a few of the other configuration in the GitHub action. At some point I'll get this up to 3.12 and fixup the rest too. You're welcome to try swapping 3.8 for 3.12 (or something else newer) here and chasing down any errors/warnings with cibuildwheel.