Updating Continuous Deployment

Both are taken from beartype\.github\workflows\pythonrelease.yml

on:
  push:
    #FIXME: Uncomment after determining why this induces critical failures on
    #"git push --tags" attempts with remote error messages resembling:
    #    error: dst refspec refs/heads/master matches more than one
    #    error: failed to push some refs to '[e-mail]:beartype/beartype.git'
    #See also: https://github.com/actions/create-release/issues/13
    # branches: [ master ]

    # Sequence of glob expressions matched against "refs/tags" pushed to the
    # branches above.
    tags:
      - 'v*'   # Match "v"-prefixed tags (e.g., "v6.9.6").

      #FIXME: Enable after integrating this "pypi" job into the "release" job
      #above. In theory, this should be trivial. Let's test this later, eh?
      # - name: "Publishing GitHub release assets from tag..."
      #   uses: actions/upload-release-asset@v1.0.1
      #   env:
      #     GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
      #   with:
      #     upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, 
                                                                       # referencing it's ID to get its outputs object, 
                                                                       # which include an `upload_url`. 
                                                                       # See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
      #     asset_path: "dist/beartype-${{ github.ref }}.zip"
      #     asset_name: "beartype-${{ github.ref }}.zip"
      #     asset_content_type: application/zip

An update from the repository of the referenced issue notes it is no longer actively maintained and “In the last year or two since we originally published this, a large number of really good community Actions have appeared on the Marketplace for doing this.”

Thus, resolution of creating a release via Github actions will almost certainly require researching alternative solutions on the Github Marketplace.

Additional Links: Windows Package Manager (Chocolatey) PyPi Deployment Github Deployments Semaphore

See also #20 covering improvements to CI

[leycec]

I’d intended to delay this migration until after publishing our next stable release, because I am intrinsically lazy. But the author of create-release effectively just archived that repository, which inspires justifiable fear rather than unshakeable confidence.

We’re immediately migrating to @ncipollo’s release-action, which appears to be the sanest, most configurable, and best maintained release action. Thanks, @ncipollo! Have all our grateful repository stars. 🌟

[leycec]

Resolved by 3dd551e. Thanks for all the quality assurance, @Heliotrop3! You keep us honest, even when we’d rather not be. 🥰