[pull] main from pypa:main

.github/workflows/test.yml

@@ -3,6 +3,8 @@ name: Test
 on:
   merge_group:
   push:
+    branches-ignore:
+    - gh-readonly-queue/**  # Temporary merge queue-related GH-made branches
   pull_request:
   schedule:
     - cron: "0 6 * * *" # daily at 6am

source/guides/github-actions-ci-cd-sample/publish-to-test-pypi.yml

@@ -73,6 +73,11 @@ jobs:
         inputs: >-
           ./dist/*.tar.gz
           ./dist/*.whl
+    - name: Create GitHub Release
+      run: >-
+        gh release create
+        '${{ github.ref_name }}'
+        --notes ""
     - name: Upload artifact signatures to GitHub Release
       env:
         GITHUB_TOKEN: ${{ github.token }}

source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst

@@ -163,8 +163,13 @@ Signing the distribution packages
 The following job signs the distribution packages with `Sigstore`_,
 the same artifact signing system `used to sign CPython <https://www.python.org/download/sigstore/>`_.
 
-It uses the `sigstore/gh-action-sigstore-python GitHub Action`_,
-and then uploads them to a GitHub Release.
+Firstly, it uses the `sigstore/gh-action-sigstore-python GitHub Action`_
+to sign the distribution packages. In the next step, an empty GitHub Release
+from the current tag is created using the ``gh`` CLI. Note this step can be further
+customised. See the `gh release documentation <https://cli.github.com/manual/gh_release>`_
+as a reference.
+
+Finally, the signed distributions are uploaded to the GitHub Release.
 
 .. literalinclude:: github-actions-ci-cd-sample/publish-to-test-pypi.yml
    :language: yaml

source/specifications/externally-managed-environments.rst

@@ -20,3 +20,7 @@ installation to indicate to Python-specific tools such as ``pip`` that they
 neither install nor remove packages into the interpreter’s default installation
 environment, and should instead guide the end user towards using
 :ref:`virtual-environments`.
+
+History
+=======
+- `June 2022 <https://discuss.python.org/t/pep-668-marking-python-base-environments-as-externally-managed/10302/44>`_: ``EXTERNALLY-MANAGED`` marker file was originally specified in :pep:`668#marking-an-interpreter-as-using-an-external-package-manager`.