diff --git a/locales/ar/LC_MESSAGES/messages.po b/locales/ar/LC_MESSAGES/messages.po index c45a4a294..e7ba7249c 100644 --- a/locales/ar/LC_MESSAGES/messages.po +++ b/locales/ar/LC_MESSAGES/messages.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2025-12-15 04:00+0000\n" "Last-Translator: HAMDI KHALID \n" "Language-Team: Arabic `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8638,37 +8645,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8676,7 +8683,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8685,7 +8692,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/ars/LC_MESSAGES/messages.po b/locales/ars/LC_MESSAGES/messages.po index 51f25a758..b2d5aa8d9 100644 --- a/locales/ars/LC_MESSAGES/messages.po +++ b/locales/ars/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -8560,13 +8560,20 @@ msgid "" "respectively, and an additional job to build the distribution packages." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:107 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:109 +msgid "" +"Keep the build job separate from the publishing jobs. Building distributions " +"in a publishing job is unsupported; publishing jobs should only download the " +"already-built artifacts and upload them." +msgstr "" + +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:113 msgid "" "First, we'll define the job for building the dist packages of your project " "and storing them for later use:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:112 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:118 msgid "" "If you adapt this workflow to build multiple platform-specific wheels, use " "uniquely named artifacts for each build job and adjust the download step " @@ -8574,23 +8581,23 @@ msgid "" "matrix layout." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:122 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:128 msgid "" "This will download your repository into the CI runner and then install and " "activate the newest available Python 3 release." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:125 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:131 msgid "" "And now we can build the dists from source and store them. In this example, " "we'll use the ``build`` package. So add this to the steps list:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:135 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:141 msgid "Defining a workflow job environment" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:137 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:143 msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -8601,21 +8608,21 @@ msgid "" "implement secretless Trusted Publishing to PyPI." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:151 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 msgid "" "This will also ensure that the PyPI publishing workflow is only triggered if " "the current commit is tagged." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:155 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:161 msgid "Publishing the distribution to PyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 msgid "Finally, add the following steps at the end:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:170 msgid "" "This step uses the `pypa/gh-action-pypi-publish`_ GitHub Action: after the " "stored distribution package has been downloaded by the `download-artifact`_ " @@ -8623,7 +8630,7 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:171 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:177 msgid "" "Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8631,37 +8638,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8669,7 +8676,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8678,7 +8685,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/cs/LC_MESSAGES/messages.po b/locales/cs/LC_MESSAGES/messages.po index 625528c6e..0a7ad1d0c 100644 --- a/locales/cs/LC_MESSAGES/messages.po +++ b/locales/cs/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2025-10-16 23:52+0000\n" "Last-Translator: Karolína Wallenfelsová \n" "Language-Team: Czech `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8642,37 +8649,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8680,7 +8687,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8689,7 +8696,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/da/LC_MESSAGES/messages.po b/locales/da/LC_MESSAGES/messages.po index a032f8b6c..94366a582 100644 --- a/locales/da/LC_MESSAGES/messages.po +++ b/locales/da/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2025-10-09 04:07+0000\n" "Last-Translator: Philip Mallegol-Hansen \n" "Language-Team: Danish `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8636,37 +8643,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8674,7 +8681,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8683,7 +8690,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/de/LC_MESSAGES/messages.po b/locales/de/LC_MESSAGES/messages.po index a8b014c12..8cf0bb963 100644 --- a/locales/de/LC_MESSAGES/messages.po +++ b/locales/de/LC_MESSAGES/messages.po @@ -19,7 +19,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2026-07-22 20:54+0000\n" "Last-Translator: VfBFan \n" "Language-Team: German `_, `pypa/gh-action-pypi-publish`_ generates " @@ -9214,37 +9221,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -9252,7 +9259,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -9261,7 +9268,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/eo/LC_MESSAGES/messages.po b/locales/eo/LC_MESSAGES/messages.po index e4fbb88e3..f9660e56d 100644 --- a/locales/eo/LC_MESSAGES/messages.po +++ b/locales/eo/LC_MESSAGES/messages.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2025-06-29 12:03+0000\n" "Last-Translator: phlostically \n" "Language-Team: Esperanto `_, `pypa/gh-action-pypi-publish`_ generates " @@ -11170,11 +11177,11 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "Aparta laborfluo por eldoni al TestPyPI" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" @@ -11182,7 +11189,7 @@ msgstr "" "Nun ripetu tiujn paŝojn, kreante alian taskon por eldonado al la pakindekso " "Prova PyPI sub la sekcio ``jobs``:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " @@ -11192,20 +11199,20 @@ msgstr "" "necesas, ĉar ĝi laŭfasone ruliĝas post ĉiu enmeto en la ĉefbranĉon kaj ofte " "indikas sanan eldonadan ĉenstablon." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "La plena laborfluo por kontinuaj integrado kaj disponigo" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "Jen alineo pri la plena laborfluo laŭ la ĉi-supra gvidilo." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "Jen fino!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -11213,7 +11220,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -11222,7 +11229,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/es/LC_MESSAGES/messages.po b/locales/es/LC_MESSAGES/messages.po index 67a0a6894..cf841aa25 100644 --- a/locales/es/LC_MESSAGES/messages.po +++ b/locales/es/LC_MESSAGES/messages.po @@ -17,7 +17,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2025-12-12 01:00+0000\n" "Last-Translator: Joseph Hale \n" "Language-Team: Spanish `_, `pypa/gh-action-pypi-publish`_ generates " @@ -9035,37 +9042,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -9073,7 +9080,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -9082,7 +9089,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/fa/LC_MESSAGES/messages.po b/locales/fa/LC_MESSAGES/messages.po index 7e52fee40..5cf7b149a 100644 --- a/locales/fa/LC_MESSAGES/messages.po +++ b/locales/fa/LC_MESSAGES/messages.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2026-07-30 20:47+0000\n" "Last-Translator: Kamrani \n" "Language-Team: Persian `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8686,37 +8693,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8724,7 +8731,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8733,7 +8740,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/fil/LC_MESSAGES/messages.po b/locales/fil/LC_MESSAGES/messages.po index eeef52514..0a025df91 100644 --- a/locales/fil/LC_MESSAGES/messages.po +++ b/locales/fil/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2022-11-19 08:28+0000\n" "Last-Translator: RedFurrFox \n" "Language-Team: Filipino `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8637,37 +8644,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8675,7 +8682,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8684,7 +8691,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/fr/LC_MESSAGES/messages.po b/locales/fr/LC_MESSAGES/messages.po index e77658e81..416943ffc 100644 --- a/locales/fr/LC_MESSAGES/messages.po +++ b/locales/fr/LC_MESSAGES/messages.po @@ -12,7 +12,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2026-01-20 00:01+0000\n" "Last-Translator: Nathan \n" "Language-Team: French `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8875,37 +8882,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8913,7 +8920,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8922,7 +8929,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/frc/LC_MESSAGES/messages.po b/locales/frc/LC_MESSAGES/messages.po index dca4a6078..06a3c5983 100644 --- a/locales/frc/LC_MESSAGES/messages.po +++ b/locales/frc/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -8560,13 +8560,20 @@ msgid "" "respectively, and an additional job to build the distribution packages." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:107 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:109 +msgid "" +"Keep the build job separate from the publishing jobs. Building distributions " +"in a publishing job is unsupported; publishing jobs should only download the " +"already-built artifacts and upload them." +msgstr "" + +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:113 msgid "" "First, we'll define the job for building the dist packages of your project " "and storing them for later use:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:112 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:118 msgid "" "If you adapt this workflow to build multiple platform-specific wheels, use " "uniquely named artifacts for each build job and adjust the download step " @@ -8574,23 +8581,23 @@ msgid "" "matrix layout." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:122 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:128 msgid "" "This will download your repository into the CI runner and then install and " "activate the newest available Python 3 release." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:125 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:131 msgid "" "And now we can build the dists from source and store them. In this example, " "we'll use the ``build`` package. So add this to the steps list:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:135 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:141 msgid "Defining a workflow job environment" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:137 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:143 msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -8601,21 +8608,21 @@ msgid "" "implement secretless Trusted Publishing to PyPI." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:151 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 msgid "" "This will also ensure that the PyPI publishing workflow is only triggered if " "the current commit is tagged." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:155 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:161 msgid "Publishing the distribution to PyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 msgid "Finally, add the following steps at the end:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:170 msgid "" "This step uses the `pypa/gh-action-pypi-publish`_ GitHub Action: after the " "stored distribution package has been downloaded by the `download-artifact`_ " @@ -8623,7 +8630,7 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:171 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:177 msgid "" "Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8631,37 +8638,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8669,7 +8676,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8678,7 +8685,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/gl/LC_MESSAGES/messages.po b/locales/gl/LC_MESSAGES/messages.po index 9d7543116..3e34bfb3e 100644 --- a/locales/gl/LC_MESSAGES/messages.po +++ b/locales/gl/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -8560,13 +8560,20 @@ msgid "" "respectively, and an additional job to build the distribution packages." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:107 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:109 +msgid "" +"Keep the build job separate from the publishing jobs. Building distributions " +"in a publishing job is unsupported; publishing jobs should only download the " +"already-built artifacts and upload them." +msgstr "" + +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:113 msgid "" "First, we'll define the job for building the dist packages of your project " "and storing them for later use:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:112 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:118 msgid "" "If you adapt this workflow to build multiple platform-specific wheels, use " "uniquely named artifacts for each build job and adjust the download step " @@ -8574,23 +8581,23 @@ msgid "" "matrix layout." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:122 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:128 msgid "" "This will download your repository into the CI runner and then install and " "activate the newest available Python 3 release." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:125 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:131 msgid "" "And now we can build the dists from source and store them. In this example, " "we'll use the ``build`` package. So add this to the steps list:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:135 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:141 msgid "Defining a workflow job environment" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:137 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:143 msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -8601,21 +8608,21 @@ msgid "" "implement secretless Trusted Publishing to PyPI." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:151 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 msgid "" "This will also ensure that the PyPI publishing workflow is only triggered if " "the current commit is tagged." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:155 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:161 msgid "Publishing the distribution to PyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 msgid "Finally, add the following steps at the end:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:170 msgid "" "This step uses the `pypa/gh-action-pypi-publish`_ GitHub Action: after the " "stored distribution package has been downloaded by the `download-artifact`_ " @@ -8623,7 +8630,7 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:171 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:177 msgid "" "Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8631,37 +8638,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8669,7 +8676,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8678,7 +8685,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/gmh/LC_MESSAGES/messages.po b/locales/gmh/LC_MESSAGES/messages.po index a753f6b58..17ca0aa04 100644 --- a/locales/gmh/LC_MESSAGES/messages.po +++ b/locales/gmh/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -8560,13 +8560,20 @@ msgid "" "respectively, and an additional job to build the distribution packages." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:107 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:109 +msgid "" +"Keep the build job separate from the publishing jobs. Building distributions " +"in a publishing job is unsupported; publishing jobs should only download the " +"already-built artifacts and upload them." +msgstr "" + +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:113 msgid "" "First, we'll define the job for building the dist packages of your project " "and storing them for later use:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:112 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:118 msgid "" "If you adapt this workflow to build multiple platform-specific wheels, use " "uniquely named artifacts for each build job and adjust the download step " @@ -8574,23 +8581,23 @@ msgid "" "matrix layout." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:122 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:128 msgid "" "This will download your repository into the CI runner and then install and " "activate the newest available Python 3 release." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:125 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:131 msgid "" "And now we can build the dists from source and store them. In this example, " "we'll use the ``build`` package. So add this to the steps list:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:135 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:141 msgid "Defining a workflow job environment" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:137 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:143 msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -8601,21 +8608,21 @@ msgid "" "implement secretless Trusted Publishing to PyPI." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:151 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 msgid "" "This will also ensure that the PyPI publishing workflow is only triggered if " "the current commit is tagged." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:155 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:161 msgid "Publishing the distribution to PyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 msgid "Finally, add the following steps at the end:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:170 msgid "" "This step uses the `pypa/gh-action-pypi-publish`_ GitHub Action: after the " "stored distribution package has been downloaded by the `download-artifact`_ " @@ -8623,7 +8630,7 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:171 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:177 msgid "" "Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8631,37 +8638,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8669,7 +8676,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8678,7 +8685,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/hi/LC_MESSAGES/messages.po b/locales/hi/LC_MESSAGES/messages.po index b79fdcaa3..7fac139f5 100644 --- a/locales/hi/LC_MESSAGES/messages.po +++ b/locales/hi/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2024-09-16 10:09+0000\n" "Last-Translator: kumar Shivam \n" "Language-Team: Hindi `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8687,37 +8694,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8725,7 +8732,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8734,7 +8741,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/id/LC_MESSAGES/messages.po b/locales/id/LC_MESSAGES/messages.po index fbcbfbd0a..8a0259b9d 100644 --- a/locales/id/LC_MESSAGES/messages.po +++ b/locales/id/LC_MESSAGES/messages.po @@ -10,7 +10,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2024-10-17 21:16+0000\n" "Last-Translator: oon arfiandwi \n" "Language-Team: Indonesian `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8689,37 +8696,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8727,7 +8734,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8736,7 +8743,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/ja/LC_MESSAGES/messages.po b/locales/ja/LC_MESSAGES/messages.po index 4e636dcfd..b5551ad95 100644 --- a/locales/ja/LC_MESSAGES/messages.po +++ b/locales/ja/LC_MESSAGES/messages.po @@ -12,8 +12,8 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" -"PO-Revision-Date: 2026-08-10 20:01+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" +"PO-Revision-Date: 2026-08-14 01:51+0000\n" "Last-Translator: moto kawasaki \n" "Language-Team: Japanese \n" @@ -11632,7 +11632,14 @@ msgstr "" "ければならず、また、配布物のパッケージ群をビルドするための追加のジョブも定義" "しなければなりません。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:107 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:109 +msgid "" +"Keep the build job separate from the publishing jobs. Building distributions " +"in a publishing job is unsupported; publishing jobs should only download the " +"already-built artifacts and upload them." +msgstr "" + +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:113 msgid "" "First, we'll define the job for building the dist packages of your project " "and storing them for later use:" @@ -11640,7 +11647,7 @@ msgstr "" "最初に、あなたのプロジェクトの dist パッケージをビルドして、その後の使用のた" "めに保存するジョブを定義しましょう:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:112 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:118 msgid "" "If you adapt this workflow to build multiple platform-specific wheels, use " "uniquely named artifacts for each build job and adjust the download step " @@ -11653,7 +11660,7 @@ msgstr "" "GitHub Actions examples`_ がもっと完全な wheel マトリクスレイアウトをお見せし" "ます。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:122 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:128 msgid "" "This will download your repository into the CI runner and then install and " "activate the newest available Python 3 release." @@ -11661,7 +11668,7 @@ msgstr "" "これによって、あなたのリポジトリを CI ランナーにダウンロードして、利用可能な" "最新の Python 3 リリースをインストールしアクティベートすることになります。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:125 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:131 msgid "" "And now we can build the dists from source and store them. In this example, " "we'll use the ``build`` package. So add this to the steps list:" @@ -11670,11 +11677,11 @@ msgstr "" "できます。この例では、パッケージを ``build`` することになります。ですから、こ" "れをステップリストに加えましょう:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:135 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:141 msgid "Defining a workflow job environment" msgstr "ワークフローのジョブ環境を定義する" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:137 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:143 msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -11693,7 +11700,7 @@ msgstr "" "トなしの PyPI への信頼ある公開を実装するために必要となる OpenID Connect の" "トークンを取得することを可能にするものでもあります。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:151 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 msgid "" "This will also ensure that the PyPI publishing workflow is only triggered if " "the current commit is tagged." @@ -11701,15 +11708,15 @@ msgstr "" "これは、当該コミットがタグ付きである時にだけ PyPI 公開 ワークフ" "ローが起動されることをも保証するものです。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:155 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:161 msgid "Publishing the distribution to PyPI" msgstr "PyPI へ配布物を公開する " -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 msgid "Finally, add the following steps at the end:" msgstr "最後に、次の手続きを末尾に追加しましょう:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:170 msgid "" "This step uses the `pypa/gh-action-pypi-publish`_ GitHub Action: after the " "stored distribution package has been downloaded by the `download-artifact`_ " @@ -11721,7 +11728,7 @@ msgstr "" "Action: を使って、 ``dist/`` フォルダの内容物を無条件に PyPI へアップロードし" "ます。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:171 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:177 msgid "" "Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " @@ -11733,11 +11740,11 @@ msgstr "" "に対する :pep:`740` 互換の証明書を生成しアップロードするようになりました。手" "動の署名手順はもはや必要ありません。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "TestPyPI へ公開 するもうひとつのワークフロー" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" @@ -11745,7 +11752,7 @@ msgstr "" "さて、これらのステップを繰り返して、 ``jobs`` セクションに TestPyPI パッケー" "ジインデックスに公開 するようなもうひとつのジョブを作成しましょう:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " @@ -11756,22 +11763,22 @@ msgstr "" "いて、使われるとすればリリースの公開 パイプラインが健全であることを" "示すためであることが多いのです。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "CI/CD ワークフローの全体像" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" "この段落には、上述のガイド文書に従った場合のワークフローの全体像を披露しま" "す。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "これでできましたよ、皆さん!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -11784,7 +11791,7 @@ msgstr "" "にテストビルドを提供するためにも、あなたのリリースパイプラインが健全な状態に" "保たれていることを確認するためにも役に立ちます!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -11799,7 +11806,7 @@ msgstr "" "で :ref:`pypiserver` のような PyPI と互換のあるサーバを使うように構成すること" "かもしれません。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -13360,6 +13367,10 @@ msgid "" "optional features (such as an ``all`` extra hosting dependencies from both " "``gui`` and ``cli``):" msgstr "" +"他の追加物を持つような現在のプロジェクトへ参照し返すような追加物を定義するこ" +"ともできます。 (``gui`` と ``cli`` の両方からの依存関係をホストする ``all`` " +"追加物のような) いくつかのオプションの機能を一体化した便利な追加物向けに有用" +"です。" #: ../source/guides/writing-pyproject-toml.rst:189 msgid "" @@ -13367,6 +13378,9 @@ msgid "" "referenced extra's dependencies, which can otherwise fall out of sync after " "a few years of maintenance and bug fixes:" msgstr "" +"一体化された追加物は、参照された先の追加物のそれぞれの依存関係のコピーを手動" +"で維持管理する必要はなく、その代わりに数年後のメンテナンスやバグ修正の時に同" +"期から外れて行くでしょう:" #: ../source/guides/writing-pyproject-toml.rst:203 msgid "" @@ -13374,6 +13388,9 @@ msgid "" "including :ref:`pip`, :ref:`uv`, :ref:`poetry`, :ref:`hatch`, :ref:`pdm` " "and :ref:`pipenv`." msgstr "" +":ref:`pip` ・ :ref:`uv` ・ :ref:`poetry` ・ :ref:`hatch` ・ :ref:`pdm` " +"や :ref:`pipenv` を含む、ほとんどのパッケージ管理機構は、今や、このような種類" +"の追加物をサポートしています。" #: ../source/guides/writing-pyproject-toml.rst:210 #: ../source/specifications/pylock-toml.rst:95 @@ -28945,6 +28962,12 @@ msgid "" "including :ref:`pip`, :ref:`uv`, :ref:`poetry`, :ref:`hatch`, :ref:`pdm` " "and :ref:`pipenv`." msgstr "" +"追加物の中の依存関係指定子は、 (例えば、 ``all = [\"your-project-name[gui, " +"cli]\"]`` のような) 現在のプロジェクトから他の追加物へ自己参照をしても構いま" +"せん。例を見たければ、 :ref:`自己参照用追加物 ` を見" +"て下さい。 :ref:`pip` ・ :ref:`uv` ・ :ref:`poetry` ・ :ref:`hatch` " +"・ :ref:`pdm` や :ref:`pipenv` を含む、ほとんどのパッケージ管理機構は、今や、" +"この種の追加物をサポートしています。" #: ../source/specifications/pyproject-toml.rst:520 msgid "" @@ -29154,9 +29177,10 @@ msgid "" "statically as well as being listed in ``dynamic``, *unless* the key " "represents a list or arbitrary table that can be extended, listed below." msgstr "" -"以下に列挙するように、そのキーが展開可能な知るとないし任意のテーブルでない限" -"り、メタデータ内のあるキーが静的に指定されていて、かつ、 ``dynamic`` にも挙げ" -"てある場合には、ビルド用バックエンドはエラーを発生させなければなりません。" +"以下に列挙するように、そのキーが展開可能な知るとないし任意のテーブル *でない" +"限り* 、メタデータ内のあるキーが静的に指定されていて、かつ、 ``dynamic`` にも" +"挙げてある場合には、ビルド用バックエンドはエラーを発生させなければなりませ" +"ん。" #: ../source/specifications/pyproject-toml.rst:637 msgid "" @@ -29203,12 +29227,20 @@ msgid "" "new keys and MAY append to the values of existing keys (in the case of a " "list), but MUST NOT change or remove the entries given statically." msgstr "" +"ビルド用バックエンドは、その値に *追加* だけを行うことができます; 静的に指定" +"されたエントリについて削除・順序変更や修正を行ってはなりません。 (``optional-" +"dependencies`` や ``entry-points`` のような) テーブルについては、これは、バッ" +"クエンドは新しいキーを追加することや (リストの場合は) 既存のキーにその値を追" +"加することは許されるが、静的に与えられたエントリを修正したり削除したりするこ" +"とは許されないということです。" #: ../source/specifications/pyproject-toml.rst:673 msgid "" "A build back-end SHOULD raise an error if a key is listed in ``dynamic`` and " "it does not support extending that key." msgstr "" +"あるキーが ``dynamic`` に列挙されていて、しかも、そのキーを拡張することをサ" +"ポートしていないなら、ビルド用バックエンドはエラーを発生させるべきです。" #: ../source/specifications/pyproject-toml.rst:680 msgid "Arbitrary tool configuration: the ``[tool]`` table" @@ -29288,12 +29320,17 @@ msgid "" "listed in ``dynamic``, with build back-ends only able to append entries, " "through :pep:`808`." msgstr "" +"2026年5月: ビルド用バックエンドがエントリを追加することしかできないという形" +"で、リストやテーブルのキーが静的に与えられると同時に ``dynamic`` に列挙される" +"ことを :pep:`808` を通じて許可した。" #: ../source/specifications/pyproject-toml.rst:722 msgid "" "August 2026: Document self-referential extra as a supported feature by many " "modern package managers of Python." msgstr "" +"2026年8月: 自己参照型追加物が多くの近代的な Python のパッケージ管理機構によっ" +"てサポートされた機能であることを文書化しました。" #: ../source/specifications/recording-installed-packages.rst:7 msgid "Recording installed projects" diff --git a/locales/kab/LC_MESSAGES/messages.po b/locales/kab/LC_MESSAGES/messages.po index 8d46a8aa7..4cf42a764 100644 --- a/locales/kab/LC_MESSAGES/messages.po +++ b/locales/kab/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2026-06-24 22:01+0000\n" "Last-Translator: ButterflyOfFire \n" "Language-Team: Kabyle `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8649,37 +8656,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8687,7 +8694,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8696,7 +8703,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/ko/LC_MESSAGES/messages.po b/locales/ko/LC_MESSAGES/messages.po index fbcd4c0ad..1b9dca84d 100644 --- a/locales/ko/LC_MESSAGES/messages.po +++ b/locales/ko/LC_MESSAGES/messages.po @@ -14,7 +14,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2026-02-05 03:01+0000\n" "Last-Translator: 스이미 \n" "Language-Team: Korean `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8846,37 +8853,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8884,7 +8891,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8893,7 +8900,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/lzh/LC_MESSAGES/messages.po b/locales/lzh/LC_MESSAGES/messages.po index fb6fe1af9..f800da947 100644 --- a/locales/lzh/LC_MESSAGES/messages.po +++ b/locales/lzh/LC_MESSAGES/messages.po @@ -3,21 +3,22 @@ # This file is distributed under the same license as the Python Packaging User Guide package. # 王玎珰 <1330274738@qq.com>, 2023. # maker , 2024. +# Haozhe Xu , 2026. msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" -"PO-Revision-Date: 2024-01-31 06:01+0000\n" -"Last-Translator: maker \n" -"Language-Team: Chinese (Literary) \n" +"Language-Team: Literary Chinese \n" "Language: lzh\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" -"X-Generator: Weblate 5.4-dev\n" +"X-Generator: Weblate 2026.9.dev0\n" #: ../source/contribute.rst:5 msgid "Contribute to this guide" @@ -27,15 +28,15 @@ msgstr "助此引" msgid "" "The |PyPUG| welcomes contributors! There are lots of ways to help out, " "including:" -msgstr "" +msgstr "|PyPUG| 迎贡献者也！为是以助也：" #: ../source/contribute.rst:10 msgid "Reading the guide and giving feedback" -msgstr "" +msgstr "阅此引而反馈者也" #: ../source/contribute.rst:11 msgid "Reviewing new contributions" -msgstr "" +msgstr "顾新贡献者" #: ../source/contribute.rst:12 msgid "Revising existing content" @@ -43,11 +44,11 @@ msgstr "" #: ../source/contribute.rst:13 msgid "Writing new content" -msgstr "" +msgstr "书新文" #: ../source/contribute.rst:14 msgid "Translating the guide" -msgstr "" +msgstr "译此引" #: ../source/contribute.rst:16 msgid "" @@ -61,11 +62,11 @@ msgstr "" msgid "" "By contributing to the |PyPUG|, you're expected to follow the PSF's `Code of " "Conduct`__." -msgstr "" +msgstr "汝可助 |PyPUG| ，而随 PSF 之 `Code of Conduct`__ 。" #: ../source/contribute.rst:32 msgid "Documentation types" -msgstr "" +msgstr "档之类" #: ../source/contribute.rst:34 msgid "" @@ -90,7 +91,7 @@ msgstr "" #: ../source/contribute.rst:51 ../source/guides/index.rst:2 #: ../source/index.rst:69 msgid "Guides" -msgstr "" +msgstr "引" #: ../source/contribute.rst:53 msgid "" @@ -104,7 +105,7 @@ msgstr "" #: ../source/contribute.rst:60 ../source/discussions/index.rst:2 msgid "Discussions" -msgstr "" +msgstr "论" #: ../source/contribute.rst:62 msgid "" @@ -112,10 +113,12 @@ msgid "" "specific topic without a specific goal in mind. :doc:`example discussion-" "style document `." msgstr "" +"论者，释与信息也。是可免细思而探新题也。:doc:`引档之例 `。" #: ../source/contribute.rst:67 msgid "Specifications" -msgstr "" +msgstr "指定" #: ../source/contribute.rst:69 msgid "" @@ -127,28 +130,30 @@ msgstr "" #: ../source/contribute.rst:75 msgid "Translations" -msgstr "" +msgstr "译文" #: ../source/contribute.rst:77 msgid "" "We use `Weblate`_ to manage translations of this project. Please visit the " "`packaging.python.org`_ project on Weblate to contribute." msgstr "" +"吾以 `Weblate`_ 辖此项之译文也。汝可访 `packaging.python.org`_ 于Weblate以" +"助。" #: ../source/contribute.rst:80 msgid "" "If you are experiencing issues while you are working on translations, please " "open an issue on `GitHub`_." -msgstr "" +msgstr "若汝译之而感不佳，可开一issue于 `GitHub`_ 。" #: ../source/contribute.rst:85 msgid "" "Any translations of this project should follow `reStructuredText syntax`_." -msgstr "" +msgstr "此项之译均须循 `reStructedText syntax`_ 之法。" #: ../source/contribute.rst:93 msgid "Adding a language" -msgstr "" +msgstr "增一语言" #: ../source/contribute.rst:95 msgid "" @@ -8566,13 +8571,20 @@ msgid "" "respectively, and an additional job to build the distribution packages." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:107 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:109 +msgid "" +"Keep the build job separate from the publishing jobs. Building distributions " +"in a publishing job is unsupported; publishing jobs should only download the " +"already-built artifacts and upload them." +msgstr "" + +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:113 msgid "" "First, we'll define the job for building the dist packages of your project " "and storing them for later use:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:112 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:118 msgid "" "If you adapt this workflow to build multiple platform-specific wheels, use " "uniquely named artifacts for each build job and adjust the download step " @@ -8580,23 +8592,23 @@ msgid "" "matrix layout." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:122 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:128 msgid "" "This will download your repository into the CI runner and then install and " "activate the newest available Python 3 release." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:125 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:131 msgid "" "And now we can build the dists from source and store them. In this example, " "we'll use the ``build`` package. So add this to the steps list:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:135 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:141 msgid "Defining a workflow job environment" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:137 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:143 msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -8607,21 +8619,21 @@ msgid "" "implement secretless Trusted Publishing to PyPI." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:151 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 msgid "" "This will also ensure that the PyPI publishing workflow is only triggered if " "the current commit is tagged." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:155 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:161 msgid "Publishing the distribution to PyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 msgid "Finally, add the following steps at the end:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:170 msgid "" "This step uses the `pypa/gh-action-pypi-publish`_ GitHub Action: after the " "stored distribution package has been downloaded by the `download-artifact`_ " @@ -8629,7 +8641,7 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:171 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:177 msgid "" "Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8637,37 +8649,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8675,7 +8687,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8684,7 +8696,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/mk/LC_MESSAGES/messages.po b/locales/mk/LC_MESSAGES/messages.po index dbb8d0e6c..bcaa89a37 100644 --- a/locales/mk/LC_MESSAGES/messages.po +++ b/locales/mk/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2023-10-21 04:04+0000\n" "Last-Translator: \"Kristijan \\\"Fremen\\\" Velkovski\" \n" "Language-Team: Macedonian `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8643,37 +8650,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8681,7 +8688,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8690,7 +8697,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/mr/LC_MESSAGES/messages.po b/locales/mr/LC_MESSAGES/messages.po index 30d8fa1e4..a44a7290e 100644 --- a/locales/mr/LC_MESSAGES/messages.po +++ b/locales/mr/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2025-01-25 14:18+0000\n" "Last-Translator: Prachi Joshi \n" "Language-Team: Marathi `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8634,37 +8641,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8672,7 +8679,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8681,7 +8688,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/mrh/LC_MESSAGES/messages.po b/locales/mrh/LC_MESSAGES/messages.po index 3c5a3e098..9d6000a48 100644 --- a/locales/mrh/LC_MESSAGES/messages.po +++ b/locales/mrh/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2026-05-05 16:17+0000\n" "Last-Translator: Laitei \n" "Language-Team: Mara `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8634,37 +8641,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8672,7 +8679,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8681,7 +8688,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/my/LC_MESSAGES/messages.po b/locales/my/LC_MESSAGES/messages.po index b6a8be281..3ccca5959 100644 --- a/locales/my/LC_MESSAGES/messages.po +++ b/locales/my/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -8561,13 +8561,20 @@ msgid "" "respectively, and an additional job to build the distribution packages." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:107 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:109 +msgid "" +"Keep the build job separate from the publishing jobs. Building distributions " +"in a publishing job is unsupported; publishing jobs should only download the " +"already-built artifacts and upload them." +msgstr "" + +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:113 msgid "" "First, we'll define the job for building the dist packages of your project " "and storing them for later use:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:112 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:118 msgid "" "If you adapt this workflow to build multiple platform-specific wheels, use " "uniquely named artifacts for each build job and adjust the download step " @@ -8575,23 +8582,23 @@ msgid "" "matrix layout." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:122 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:128 msgid "" "This will download your repository into the CI runner and then install and " "activate the newest available Python 3 release." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:125 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:131 msgid "" "And now we can build the dists from source and store them. In this example, " "we'll use the ``build`` package. So add this to the steps list:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:135 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:141 msgid "Defining a workflow job environment" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:137 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:143 msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -8602,21 +8609,21 @@ msgid "" "implement secretless Trusted Publishing to PyPI." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:151 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 msgid "" "This will also ensure that the PyPI publishing workflow is only triggered if " "the current commit is tagged." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:155 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:161 msgid "Publishing the distribution to PyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 msgid "Finally, add the following steps at the end:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:170 msgid "" "This step uses the `pypa/gh-action-pypi-publish`_ GitHub Action: after the " "stored distribution package has been downloaded by the `download-artifact`_ " @@ -8624,7 +8631,7 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:171 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:177 msgid "" "Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8632,37 +8639,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8670,7 +8677,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8679,7 +8686,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/pl/LC_MESSAGES/messages.po b/locales/pl/LC_MESSAGES/messages.po index de7dd6428..e5f34d33c 100644 --- a/locales/pl/LC_MESSAGES/messages.po +++ b/locales/pl/LC_MESSAGES/messages.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2026-02-11 07:09+0000\n" "Last-Translator: Maciej Olko \n" "Language-Team: Polish `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8656,37 +8663,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8694,7 +8701,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8703,7 +8710,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/pt/LC_MESSAGES/messages.po b/locales/pt/LC_MESSAGES/messages.po index e42b26768..485f83af7 100644 --- a/locales/pt/LC_MESSAGES/messages.po +++ b/locales/pt/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2026-06-14 08:02+0000\n" "Last-Translator: ssantos \n" "Language-Team: Portuguese `_, `pypa/gh-action-pypi-publish`_ generates " @@ -10871,11 +10878,11 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "Fluxo de trabalho separado para publicação no TestPyPI" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" @@ -10883,7 +10890,7 @@ msgstr "" "Agora, repita estas etapas e crie outro trabalho para publicação no índice " "do pacote TestPyPI na secção ``jobs``:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " @@ -10894,21 +10901,21 @@ msgstr "" "branch principal e é frequentemente usado para indicar um pipeline de " "publicação de lançamento íntegro." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "O fluxo de trabalho de CI/CD completo" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" "Este parágrafo mostra todo o fluxo de trabalho após seguir o guia acima." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "Isso é tudo, pessoal!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -10921,7 +10928,7 @@ msgstr "" "construções de teste para os seus utilizadores alfa, bem como garantir que a " "sua versão pipeline permaneça saudável!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -10936,7 +10943,7 @@ msgstr "" "um servidor compatível com PyPI como :ref:`pypiserver` no CI para fins de " "teste." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/pt_BR/LC_MESSAGES/messages.po b/locales/pt_BR/LC_MESSAGES/messages.po index b97a0082b..f7757faf9 100644 --- a/locales/pt_BR/LC_MESSAGES/messages.po +++ b/locales/pt_BR/LC_MESSAGES/messages.po @@ -12,7 +12,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2025-08-07 00:01+0000\n" "Last-Translator: Rafael Fontenelle \n" "Language-Team: Portuguese (Brazil) `_, `pypa/gh-action-pypi-publish`_ generates " @@ -11489,11 +11496,11 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "Fluxo de trabalho separado para publicação no TestPyPI" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" @@ -11501,7 +11508,7 @@ msgstr "" "Agora, repita essas etapas e crie outro trabalho para publicação no índice " "do pacote TestPyPI na seção ``jobs``:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " @@ -11512,21 +11519,21 @@ msgstr "" "branch principal e é frequentemente usado para indicar um pipeline de " "publicação de lançamento íntegro." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "O fluxo de trabalho de CI/CD completo" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" "Este parágrafo mostra todo o fluxo de trabalho após seguir o guia acima." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "Isso é tudo, pessoal!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -11539,7 +11546,7 @@ msgstr "" "construções de teste para seus usuários alfa, bem como garantir que sua " "versão pipeline permaneça saudável!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -11554,7 +11561,7 @@ msgstr "" "um servidor compatível com PyPI como :ref:`pypiserver` no CI para fins de " "teste." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/ro/LC_MESSAGES/messages.po b/locales/ro/LC_MESSAGES/messages.po index cced27637..dca6d6a1c 100644 --- a/locales/ro/LC_MESSAGES/messages.po +++ b/locales/ro/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2021-08-20 01:32+0000\n" "Last-Translator: GUILHERME FERNANDES NETO \n" "Language-Team: Romanian `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8639,37 +8646,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8677,7 +8684,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8686,7 +8693,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/ru/LC_MESSAGES/messages.po b/locales/ru/LC_MESSAGES/messages.po index 51d5cb090..92a9021e9 100644 --- a/locales/ru/LC_MESSAGES/messages.po +++ b/locales/ru/LC_MESSAGES/messages.po @@ -15,7 +15,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2025-06-07 08:01+0000\n" "Last-Translator: da070116 \n" "Language-Team: Russian `_, `pypa/gh-action-pypi-publish`_ generates " @@ -11611,11 +11618,11 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "Отдельный рабочий процесс для публикации в TestPyPI" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" @@ -11623,7 +11630,7 @@ msgstr "" "Теперь повторите эти шаги и создайте еще одно задание для публикации в " "индекс пакета TestPyPI в разделе ``jobs``:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " @@ -11634,22 +11641,22 @@ msgstr "" "основной ветке и часто используется для обозначения здорового конвейера " "публикации pipрелизов." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "Весь рабочий процесс CI/CD" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" "В этом пункте показан весь рабочий процесс после выполнения вышеописанного " "руководства." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "Вот и все, друзья!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -11662,7 +11669,7 @@ msgstr "" "сборок вашим альфа-пользователям, а также для того, чтобы убедиться, что ваш " "конвейер релизовpip остаётся здоровым!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -11676,7 +11683,7 @@ msgstr "" "увеличен, но лучшим решением может быть использование PyPI-совместимого " "сервера, например :ref:`pypiserver`, в CI для тестирования." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/sai/LC_MESSAGES/messages.po b/locales/sai/LC_MESSAGES/messages.po index 4844f501d..82e440e7d 100644 --- a/locales/sai/LC_MESSAGES/messages.po +++ b/locales/sai/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -8560,13 +8560,20 @@ msgid "" "respectively, and an additional job to build the distribution packages." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:107 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:109 +msgid "" +"Keep the build job separate from the publishing jobs. Building distributions " +"in a publishing job is unsupported; publishing jobs should only download the " +"already-built artifacts and upload them." +msgstr "" + +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:113 msgid "" "First, we'll define the job for building the dist packages of your project " "and storing them for later use:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:112 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:118 msgid "" "If you adapt this workflow to build multiple platform-specific wheels, use " "uniquely named artifacts for each build job and adjust the download step " @@ -8574,23 +8581,23 @@ msgid "" "matrix layout." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:122 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:128 msgid "" "This will download your repository into the CI runner and then install and " "activate the newest available Python 3 release." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:125 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:131 msgid "" "And now we can build the dists from source and store them. In this example, " "we'll use the ``build`` package. So add this to the steps list:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:135 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:141 msgid "Defining a workflow job environment" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:137 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:143 msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -8601,21 +8608,21 @@ msgid "" "implement secretless Trusted Publishing to PyPI." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:151 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 msgid "" "This will also ensure that the PyPI publishing workflow is only triggered if " "the current commit is tagged." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:155 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:161 msgid "Publishing the distribution to PyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 msgid "Finally, add the following steps at the end:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:170 msgid "" "This step uses the `pypa/gh-action-pypi-publish`_ GitHub Action: after the " "stored distribution package has been downloaded by the `download-artifact`_ " @@ -8623,7 +8630,7 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:171 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:177 msgid "" "Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8631,37 +8638,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8669,7 +8676,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8678,7 +8685,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/si/LC_MESSAGES/messages.po b/locales/si/LC_MESSAGES/messages.po index f1798fff2..c18a1bcb3 100644 --- a/locales/si/LC_MESSAGES/messages.po +++ b/locales/si/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2022-06-11 08:19+0000\n" "Last-Translator: Kushan Gunasekera \n" "Language-Team: Sinhala `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8635,37 +8642,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8673,7 +8680,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8682,7 +8689,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/sk/LC_MESSAGES/messages.po b/locales/sk/LC_MESSAGES/messages.po index b767f8e70..136566d78 100644 --- a/locales/sk/LC_MESSAGES/messages.po +++ b/locales/sk/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2024-11-02 00:54+0000\n" "Last-Translator: Milan Šalka \n" "Language-Team: Slovak `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8791,37 +8798,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8829,7 +8836,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8838,7 +8845,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/ta/LC_MESSAGES/messages.po b/locales/ta/LC_MESSAGES/messages.po index 92682ba40..462a25165 100644 --- a/locales/ta/LC_MESSAGES/messages.po +++ b/locales/ta/LC_MESSAGES/messages.po @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2025-07-19 06:36+0000\n" "Last-Translator: தமிழ்நேரம் \n" "Language-Team: Tamil `_, `pypa/gh-action-pypi-publish`_ generates " @@ -11210,11 +11217,11 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "டெச்ட்பிபிக்கு வெளியிடுவதற்கு பணிப்பாய்வு தனி" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" @@ -11222,7 +11229,7 @@ msgstr "" "இப்போது, இந்த படிகளை மீண்டும் செய்து, `` வேலைகள்`` பிரிவின் கீழ் டெச்ட்பை தொகுப்பு " "குறியீட்டுக்கு வெளியிட மற்றொரு வேலையை உருவாக்கவும்:" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " @@ -11233,21 +11240,21 @@ msgstr "" "வடிவமைக்கப்பட்டுள்ளது மற்றும் ஆரோக்கியமான வெளியீட்டு வெளியீட்டு குழாய்த்திட்டத்தைக் குறிக்க " "பெரும்பாலும் பயன்படுத்தப்படுகிறது." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "முழு சிஐ/சிடி பணிப்பாய்வு" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" "இந்த பத்தி மேலே உள்ள வழிகாட்டியைப் பின்பற்றிய பிறகு முழு பணிப்பாய்வுகளையும் காட்டுகிறது." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "அவ்வளவுதான், எல்லோரும்!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -11259,7 +11266,7 @@ msgstr "" "சோதனை கட்டமைப்பை வழங்குவதற்கும், உங்கள் வெளியீட்டு குழாய் ஆரோக்கியமாக இருப்பதை " "உறுதிசெய்வதற்கும் பயனுள்ளதாக இருக்கும் டெச்ட்பிபிக்கு எந்தவொரு உந்துதலையும் வெளியிடும்!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -11273,7 +11280,7 @@ msgstr "" "ஒரு சிறந்த தீர்வு ஒரு பைபி-இணக்கமான சேவையகத்தைப் பயன்படுத்தலாம்: குறிப்பு நோக்கங்களுக்காக " "தொஒ இல் `பைபிசெவர்`." -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/th/LC_MESSAGES/messages.po b/locales/th/LC_MESSAGES/messages.po index 3dd6a3e0a..78ef3650a 100644 --- a/locales/th/LC_MESSAGES/messages.po +++ b/locales/th/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" @@ -8560,13 +8560,20 @@ msgid "" "respectively, and an additional job to build the distribution packages." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:107 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:109 +msgid "" +"Keep the build job separate from the publishing jobs. Building distributions " +"in a publishing job is unsupported; publishing jobs should only download the " +"already-built artifacts and upload them." +msgstr "" + +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:113 msgid "" "First, we'll define the job for building the dist packages of your project " "and storing them for later use:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:112 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:118 msgid "" "If you adapt this workflow to build multiple platform-specific wheels, use " "uniquely named artifacts for each build job and adjust the download step " @@ -8574,23 +8581,23 @@ msgid "" "matrix layout." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:122 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:128 msgid "" "This will download your repository into the CI runner and then install and " "activate the newest available Python 3 release." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:125 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:131 msgid "" "And now we can build the dists from source and store them. In this example, " "we'll use the ``build`` package. So add this to the steps list:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:135 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:141 msgid "Defining a workflow job environment" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:137 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:143 msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -8601,21 +8608,21 @@ msgid "" "implement secretless Trusted Publishing to PyPI." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:151 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 msgid "" "This will also ensure that the PyPI publishing workflow is only triggered if " "the current commit is tagged." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:155 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:161 msgid "Publishing the distribution to PyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 msgid "Finally, add the following steps at the end:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:170 msgid "" "This step uses the `pypa/gh-action-pypi-publish`_ GitHub Action: after the " "stored distribution package has been downloaded by the `download-artifact`_ " @@ -8623,7 +8630,7 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:171 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:177 msgid "" "Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8631,37 +8638,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8669,7 +8676,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8678,7 +8685,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/tr/LC_MESSAGES/messages.po b/locales/tr/LC_MESSAGES/messages.po index f3057435b..d8eec28b6 100644 --- a/locales/tr/LC_MESSAGES/messages.po +++ b/locales/tr/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2025-09-29 04:02+0000\n" "Last-Translator: Rüzgar Hünerel \n" "Language-Team: Turkish `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8658,37 +8665,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8696,7 +8703,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8705,7 +8712,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/uk/LC_MESSAGES/messages.po b/locales/uk/LC_MESSAGES/messages.po index 28f1f873d..88f50ed66 100644 --- a/locales/uk/LC_MESSAGES/messages.po +++ b/locales/uk/LC_MESSAGES/messages.po @@ -15,7 +15,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2024-03-01 20:00+0000\n" "Last-Translator: Sviatoslav Sydorenko \n" "Language-Team: Ukrainian `_, `pypa/gh-action-pypi-publish`_ generates " @@ -9141,37 +9148,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "Це все, добродії!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -9179,7 +9186,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -9188,7 +9195,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/vi/LC_MESSAGES/messages.po b/locales/vi/LC_MESSAGES/messages.po index 63aeb0f2e..e48ac5102 100644 --- a/locales/vi/LC_MESSAGES/messages.po +++ b/locales/vi/LC_MESSAGES/messages.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2025-09-23 05:02+0000\n" "Last-Translator: Lenny Tran \n" "Language-Team: Vietnamese `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8778,37 +8785,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8816,7 +8823,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8825,7 +8832,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." diff --git a/locales/zh_Hans/LC_MESSAGES/messages.po b/locales/zh_Hans/LC_MESSAGES/messages.po index 68ee244d3..b2710473c 100644 --- a/locales/zh_Hans/LC_MESSAGES/messages.po +++ b/locales/zh_Hans/LC_MESSAGES/messages.po @@ -38,14 +38,17 @@ # rand777 , 2025. # monios , 2025. # reducedradius <137701630+flytothehighest@users.noreply.github.com>, 2026. +# Haozhe Xu , 2026. +# B10112 , 2026. +# Hosted Weblate user 162400 , 2026. msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" -"PO-Revision-Date: 2026-06-28 07:02+0000\n" -"Last-Translator: reducedradius " -"<137701630+flytothehighest@users.noreply.github.com>\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" +"PO-Revision-Date: 2026-08-18 21:41+0000\n" +"Last-Translator: Hosted Weblate user 162400 \n" "Language-Team: Chinese (Simplified Han script) \n" "Language: zh_Hans\n" @@ -53,7 +56,7 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" -"X-Generator: Weblate 2026.7.dev0\n" +"X-Generator: Weblate 2026.9.dev0\n" #: ../source/contribute.rst:5 msgid "Contribute to this guide" @@ -1095,9 +1098,9 @@ msgid "" "time. For example, automatically generated Git archives do not guarantee " "this, as the compressed data may change if gzip is upgraded on the server." msgstr "" -"下游经常使用哈希来验证后续构建中源文件的真实性，而这需要文件长期保持二进制相" -"同。举个例子，自动生成的 Git 存档就不保证这一点，因为如果服务器上的 gzip 升级" -"了，那么压缩的数据可能会改变。" +"下游项目经常使用哈希值，在后续构建过程中校验源码文件的真实性，这就要求源码文" +"件随时间推移必须保持按比特完全一致。例如，自动生成的 Git 归档文件无法保证这一" +"点：如果服务端的 gzip 版本升级，压缩得到的数据就可能发生变化。" #: ../source/discussions/downstream-packaging.rst:88 msgid "" @@ -1520,19 +1523,21 @@ msgstr "验证下游包没有引入任何漏洞。" #: ../source/discussions/downstream-packaging.rst:312 msgid "" "Testing on additional platforms that are not covered by upstream testing." -msgstr "" +msgstr "在未被上游测试所覆盖的第三方平台上进行的测试。" #: ../source/discussions/downstream-packaging.rst:314 msgid "" "Finding subtle bugs that can only be reproduced with particular hardware, " "system package versions, and so on." -msgstr "" +msgstr "找出那些只在特定硬件、系统包版本等环境下才能重现的隐蔽漏洞。" #: ../source/discussions/downstream-packaging.rst:317 msgid "" "Testing the released package against newer (or older) dependency versions " "than the ones present during upstream release testing." msgstr "" +"对已发布的软件包进行测试时，使用比上游发布测试时所采用的依赖版本更新（或更" +"旧）的版本。" #: ../source/discussions/downstream-packaging.rst:320 msgid "" @@ -1541,12 +1546,16 @@ msgid "" "different installed packages, including packages that are not dependencies " "of your package, but nevertheless can cause issues." msgstr "" +"在尽可能接近生产环境的环境中测试该软件包。这可以检测出由不同已安装包之间复杂" +"交互所导致的问题，包括那些并非你软件包依赖项、但仍然可能引发问题的包。" #: ../source/discussions/downstream-packaging.rst:325 msgid "" "Testing the released package against newer Python versions (including newer " "point releases), or less tested Python implementations such as PyPy." msgstr "" +"针对较新版本的 Python（包括新的次要/补丁版本），或测试覆盖较少的 Python 实现" +"（如 PyPy），对已发布的软件包进行测试。" #: ../source/discussions/downstream-packaging.rst:328 msgid "" @@ -1558,6 +1567,10 @@ msgid "" "downstream packagers are doing their best to double-check their results, and " "help upstream maintainers triage and fix the bugs that they reported." msgstr "" +"诚然，下游测试有时可能会产生误报，或者报告一些上游项目无意支持的场景。然而，" +"更多时候它确实能提前预警问题，或发现那些否则会给上游项目用户带来麻烦的隐蔽缺" +"陷。尽管错误确实难免，但绝大多数下游打包者都在尽力反复核验自己的结果，并帮助" +"上游维护者对报告的问题进行诊断和修复。" #: ../source/discussions/downstream-packaging.rst:339 msgid "" @@ -1568,12 +1581,15 @@ msgid "" "use for everyone, not just downstream packagers. Some specific suggestions " "are:" msgstr "" +"上游项目可以做许多事情来帮助下游重新打包者高效、有效地测试他们的软件包，其中" +"就包括上文提到的一些建议。这些改进通常能让测试套件对所有人来说都更可靠、更易" +"用，而不仅仅是对下游打包者。以下是一些具体建议：" #: ../source/discussions/downstream-packaging.rst:345 msgid "" "Include the test files and fixtures in the source distribution, or make it " "possible to easily download them separately." -msgstr "" +msgstr "在源代码分发包中包含测试文件及测试夹具，或者使其能够单独轻松下载。" #: ../source/discussions/downstream-packaging.rst:348 msgid "" @@ -1582,6 +1598,9 @@ msgid "" "modifications performed during testing and temporary test files may end up " "being part of the installed package!" msgstr "" +"测试期间不要向包目录中写入任何内容。下游测试环境有时会在已安装的包之上直接运" +"行测试，而测试过程中所做的修改以及临时测试文件最终可能会被误纳入已安装的包" +"中！" #: ../source/discussions/downstream-packaging.rst:353 msgid "" @@ -1591,6 +1610,10 @@ msgid "" "Use pytest-socket_ to verify that your tests work offline. This often makes " "your own test workflows faster and more reliable as well." msgstr "" +"使测试套件能够在离线状态下工作。使用诸如 responses_ 或 vcrpy_ 之类的包来模拟" +"网络交互。如果无法做到，则应提供便捷的方式禁用需要互联网访问的测试，例如通过 " +"pytest_ 标记。可使用 pytest-socket_ 来验证你的测试确实在离线状态下运行。这样" +"做通常也能让你的测试工作流更快、更可靠。" #: ../source/discussions/downstream-packaging.rst:359 msgid "" @@ -1599,6 +1622,8 @@ msgid "" "system services such as databases — in an extreme case, you could crash a " "production service!" msgstr "" +"让测试无需专门配置即可运行，或将必要配置作为测试固件的一部分来执行。切勿假设" +"你可以连接到数据库等系统服务——在极端情况下，这可能导致生产服务崩溃！" #: ../source/discussions/downstream-packaging.rst:364 msgid "" @@ -1606,6 +1631,8 @@ msgid "" "well. Either skip them if the needed packages are not installed, or add " "markers to make deselecting easy." msgstr "" +"如果你的软件包有可选依赖，那么这些依赖对应的测试也应当是可选的。如果所需的包" +"未安装，则跳过这些测试；或者添加标记，以便于轻松取消选择它们。" #: ../source/discussions/downstream-packaging.rst:368 msgid "" @@ -1613,6 +1640,8 @@ msgid "" "include e.g. significant space usage, significant memory usage, long " "runtime, incompatibility with parallel testing." msgstr "" +"更一般地说，为有特殊要求的测试添加标记。例如，这类测试可能会占用大量磁盘空" +"间、消耗大量内存、运行耗时较长，或是与并行测试不兼容。" #: ../source/discussions/downstream-packaging.rst:372 msgid "" @@ -1621,6 +1650,9 @@ msgid "" "dependency versions. Assert for warnings using ``pytest.warns()`` rather " "than ``pytest.raises()``!" msgstr "" +"不要假定测试套件会使用 ``-Werror`` 运行。下游项目往往需要禁用该选项，因为它会" +"产生误报，例如依赖库版本更新就可能导致该问题。请使用 ``pytest.warns()`` 对警" +"告进行断言，而不要使用 ``pytest.raises()`` ！" #: ../source/discussions/downstream-packaging.rst:377 msgid "" @@ -1630,6 +1662,9 @@ msgid "" "its advantages, but you want to have static test cases for completeness as " "well." msgstr "" +"请力求让你的测试套件可靠且可复现。避免不稳定测试。不要依赖特定平台细节，不要" +"依赖浮点计算的精确结果、操作执行时序等内容。模糊测试固然有其优势，但为保证完" +"备性，你同样应当编写静态测试用例。" #: ../source/discussions/downstream-packaging.rst:383 msgid "" @@ -1641,6 +1676,10 @@ msgid "" "upgraded or the system is under load, without actually affecting the package " "itself." msgstr "" +"请按照用途拆分测试，并让无关或存在问题的测试类别可以方便地跳过。下游测试的主" +"要目的是确保软件包本身能够正常工作，因此下游项目通常并不关心代码覆盖率检查、" +"代码格式化、类型检查或是运行基准测试这类任务。当依赖升级或者系统处于高负载" +"时，这类测试可能会失败，但并不会真正影响软件包本身的功能。" #: ../source/discussions/downstream-packaging.rst:390 msgid "" @@ -1649,6 +1688,8 @@ msgid "" "them all takes a lot of time. Using pytest-xdist_ can help them avoid " "bottlenecks." msgstr "" +"如果你的测试套件运行耗时较长，请支持并行测试。下游项目通常要维护大量软件包，" +"全部测试会消耗大量时间。使用 pytest‑xdist_ 可以帮助他们消除测试瓶颈。" #: ../source/discussions/downstream-packaging.rst:395 msgid "" @@ -1661,6 +1702,13 @@ msgid "" "``pytest``: ``pytest`` is able to find and execute almost all test cases " "that are compatible with the standard library's ``unittest`` test discovery." msgstr "" +"在理想情况下，请支持通过 ``pytest`` 运行你的测试套件。``pytest``_ 拥有大量对" +"下游项目十分实用的命令行参数，例如可以便捷地剔除指定测试、重跑不稳定测试（借" +"助 ``pytest‑rerunfailures``_）、设置超时防止测试挂起（借助 " +"``pytest‑timeout``_），或是并行执行测试（借助 ``pytest‑xdist``_）。请注意：测" +"试套件无需用 ``pytest`` *written*，也能够用 ``pytest`` *executed*；" +"``pytest`` 几乎能够发现并运行所有兼容标准库 ``unittest`` 测试发现机制的测试用" +"例。" #: ../source/discussions/downstream-packaging.rst:409 msgid "Aim for stable releases" @@ -1673,6 +1721,9 @@ msgid "" "upgrades to users with higher stability needs. These users often prefer to " "trade having the newest features available for lower risk of issues." msgstr "" +"许多下游项目除主软件包源之外还提供稳定发布渠道。设置这些渠道的目的，是为对稳" +"定性要求较高的用户提供更保守的版本升级。这类用户往往宁愿放弃最新功能，换取更" +"低的故障风险。" #: ../source/discussions/downstream-packaging.rst:419 msgid "" @@ -1683,6 +1734,10 @@ msgid "" "available in testing for a month, and being tested against the versions of " "its dependencies that are marked stable at the time." msgstr "" +"尽管具体策略各有差异，但将软件包新版本纳入稳定发布渠道的一项重要标准是：该版" +"本已经在测试渠道中发布一段时间，且不存在已知的严重功能退化问题。例如，在 " +"Gentoo Linux 中，软件包通常需要在测试渠道中发布满一个月，并且针对当时标记为稳" +"定版本的依赖项完成测试后，才会被标记为稳定。" #: ../source/discussions/downstream-packaging.rst:426 msgid "" @@ -1692,24 +1747,29 @@ msgid "" "a need to resolve it. In this case, they need to consider various options, " "such as:" msgstr "" +"但也存在需要更快速处理的情形。例如，如果稳定渠道当前提供的版本中发现安全漏洞" +"或重大缺陷，下游项目就需要着手解决该问题。此时他们需要权衡多种可选方案，例" +"如：" #: ../source/discussions/downstream-packaging.rst:431 msgid "putting a new version in the stable channel early," -msgstr "" +msgstr "提前将新版本纳入稳定渠道，" #: ../source/discussions/downstream-packaging.rst:433 msgid "adding patches to the version currently published," -msgstr "" +msgstr "为当前已发布的版本应用补丁，" #: ../source/discussions/downstream-packaging.rst:435 msgid "or even downgrading the stable channel to an earlier release." -msgstr "" +msgstr "甚至将稳定渠道降级至更早的发行版本。" #: ../source/discussions/downstream-packaging.rst:437 msgid "" "Each of these options involves certain risks and a certain amount of work, " "and packagers needs to weigh them to determine the course of action." msgstr "" +"上述每一种方案都伴随着相应的风险与工作量，打包维护者需要权衡利弊来确定处理方" +"案。" #: ../source/discussions/downstream-packaging.rst:443 msgid "" @@ -1717,6 +1777,8 @@ msgid "" "stable release channels. These actions often are beneficial to the package's " "users as well. Some specific suggestions are:" msgstr "" +"上游项目可以采取一些措施，让自身工作流适配稳定发布渠道。这些做法通常也会对软" +"件包的用户带来益处。部分具体建议如下：" #: ../source/discussions/downstream-packaging.rst:447 msgid "" @@ -1724,6 +1786,8 @@ msgid "" "released rarely often bring significant changes with every release, and a " "higher risk of accidental regressions." msgstr "" +"根据代码变更的幅度调整版本发布频率。低频发布的软件包往往每次更新都会引入大量" +"改动，出现意外功能退化的风险也会更高。" #: ../source/discussions/downstream-packaging.rst:451 msgid "" @@ -9440,13 +9504,20 @@ msgid "" "respectively, and an additional job to build the distribution packages." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:107 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:109 +msgid "" +"Keep the build job separate from the publishing jobs. Building distributions " +"in a publishing job is unsupported; publishing jobs should only download the " +"already-built artifacts and upload them." +msgstr "" + +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:113 msgid "" "First, we'll define the job for building the dist packages of your project " "and storing them for later use:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:112 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:118 msgid "" "If you adapt this workflow to build multiple platform-specific wheels, use " "uniquely named artifacts for each build job and adjust the download step " @@ -9454,24 +9525,24 @@ msgid "" "matrix layout." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:122 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:128 msgid "" "This will download your repository into the CI runner and then install and " "activate the newest available Python 3 release." msgstr "" "这将把您的版本库下载到 CI 运行程序中，然后安装并激活最新的 Python 3 版本。" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:125 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:131 msgid "" "And now we can build the dists from source and store them. In this example, " "we'll use the ``build`` package. So add this to the steps list:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:135 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:141 msgid "Defining a workflow job environment" msgstr "定义一个工作流程的工作环境" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:137 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:143 msgid "" "Now, let's add initial setup for our job that will publish to PyPI. It's a " "process that will execute commands that we'll define later. In this guide, " @@ -9482,21 +9553,21 @@ msgid "" "implement secretless Trusted Publishing to PyPI." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:151 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 msgid "" "This will also ensure that the PyPI publishing workflow is only triggered if " "the current commit is tagged." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:155 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:161 msgid "Publishing the distribution to PyPI" msgstr "将发行版发布到 PyPI" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163 msgid "Finally, add the following steps at the end:" msgstr "最后，在结尾添加以下步骤：" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:170 msgid "" "This step uses the `pypa/gh-action-pypi-publish`_ GitHub Action: after the " "stored distribution package has been downloaded by the `download-artifact`_ " @@ -9504,7 +9575,7 @@ msgid "" "unconditionally." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:171 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:177 msgid "" "Starting with version `v1.11.0 `_, `pypa/gh-action-pypi-publish`_ generates " @@ -9512,37 +9583,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "就这些了，伙计们!" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -9550,7 +9621,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -9559,7 +9630,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently." @@ -16461,7 +16532,7 @@ msgstr "" #: ../source/specifications/core-metadata.rst:1093 msgid "reStructuredText markup: https://docutils.sourceforge.io/" -msgstr "reStructuredText 标记：https://docutils.sourceforge.io/" +msgstr "`reStructuredText 标记 `_" #: ../source/specifications/core-metadata.rst:1098 msgid "RFC 822 Long Header Fields: :rfc:`822#section-3.1.1`" diff --git a/locales/zh_Hant/LC_MESSAGES/messages.po b/locales/zh_Hant/LC_MESSAGES/messages.po index 30d776a18..057e2c199 100644 --- a/locales/zh_Hant/LC_MESSAGES/messages.po +++ b/locales/zh_Hant/LC_MESSAGES/messages.po @@ -14,7 +14,7 @@ msgid "" msgstr "" "Project-Id-Version: Python Packaging User Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-08-11 10:39+0000\n" +"POT-Creation-Date: 2026-08-19 11:32+0000\n" "PO-Revision-Date: 2025-02-24 15:37+0000\n" "Last-Translator: toto6038 \n" "Language-Team: Chinese (Traditional Han script) `_, `pypa/gh-action-pypi-publish`_ generates " @@ -8733,37 +8740,37 @@ msgid "" "default. No additional manual signing steps are required." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185 msgid "Separate workflow for publishing to TestPyPI" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187 msgid "" "Now, repeat these steps and create another job for publishing to the " "TestPyPI package index under the ``jobs`` section:" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 msgid "" "Requiring manual approvals in the ``testpypi`` GitHub Environment is " "typically unnecessary as it's designed to run on each commit to the main " "branch and is often used to indicate a healthy release publishing pipeline." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201 msgid "The whole CI/CD workflow" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203 msgid "" "This paragraph showcases the whole workflow after following the above guide." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211 msgid "That's all, folks!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213 msgid "" "Now, whenever you push a tagged commit to your Git repository remote on " "GitHub, this workflow will publish it to PyPI. And it'll publish any push to " @@ -8771,7 +8778,7 @@ msgid "" "well as making sure that your release pipeline remains healthy!" msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221 msgid "" "If your repository has frequent commit activity and every push is uploaded " "to TestPyPI as described, the project might exceed the `PyPI project size " @@ -8780,7 +8787,7 @@ msgid "" "server like :ref:`pypiserver` in the CI for testing purposes." msgstr "" -#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223 +#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229 msgid "" "It is recommended to keep the integrated GitHub Actions at their latest " "versions, updating them frequently."