gyp-next icon indicating copy to clipboard operation
gyp-next copied to clipboard

chore: setup release automation

Open legendecas opened this issue 1 year ago • 5 comments

Registries included:

  • pypi
  • github release

Refs: https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

legendecas avatar Apr 30 '24 13:04 legendecas

I appreciate the work you put in this, but we're already using release-please to create the release, so I'm surprised you're not adding something to the existing workflow.

targos avatar Apr 30 '24 13:04 targos

release-please doesn't publish the package to the registry. I'll merge the two workflow so that they can be pipelined. Thanks for the suggestion!

legendecas avatar Apr 30 '24 13:04 legendecas

This is ready for review. I ran it on my own repo and published https://test.pypi.org/project/gyp-next/0.18.0.post1/

legendecas avatar May 09 '24 09:05 legendecas

It is a shame that GitHub Packages still lacks support for the Python Packaging Index (PyPI). https://docs.github.com/en/packages/learn-github-packages/introduction-to-github-packages#support-for-package-registries

cclauss avatar May 09 '24 12:05 cclauss

Well, yeah, no idea why pypi api isn't supported.

legendecas avatar May 09 '24 20:05 legendecas

@legendecas https://github.com/legendecas/gyp-next/pull/2

targos avatar May 21 '24 12:05 targos

@cclauss @targos would you mind taking a look again? thank you!

legendecas avatar May 23 '24 14:05 legendecas

I'd prefer someone else to review as I did part of the changes and I'm not familiar with the release of Python packages.

targos avatar May 24 '24 08:05 targos