Skip to content

Commit e36e91e

Browse files
weblateweblate
committed
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Co-authored-by: Hosted Weblate <hosted@weblate.org> Translate-URL: https://hosted.weblate.org/projects/pypa/packaging-python-org/ Translation: pypa/packaging.python.org
1 parent cc40ab0 commit e36e91e

38 files changed

Lines changed: 1098 additions & 831 deletions

File tree

‎locales/ar/LC_MESSAGES/messages.po‎

Lines changed: 28 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ msgid ""
99
msgstr ""
1010
"Project-Id-Version: Python Packaging User Guide\n"
1111
"Report-Msgid-Bugs-To: \n"
12-
"POT-Creation-Date: 2026-08-11 10:39+0000\n"
12+
"POT-Creation-Date: 2026-08-19 11:32+0000\n"
1313
"PO-Revision-Date: 2025-12-15 04:00+0000\n"
1414
"Last-Translator: HAMDI KHALID <hamdikhalid43@gmail.com>\n"
1515
"Language-Team: Arabic <https://hosted.weblate.org/projects/pypa/packaging-"
@@ -8567,37 +8567,44 @@ msgid ""
85678567
"respectively, and an additional job to build the distribution packages."
85688568
msgstr ""
85698569

8570-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:107
8570+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:109
8571+
msgid ""
8572+
"Keep the build job separate from the publishing jobs. Building distributions "
8573+
"in a publishing job is unsupported; publishing jobs should only download the "
8574+
"already-built artifacts and upload them."
8575+
msgstr ""
8576+
8577+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:113
85718578
msgid ""
85728579
"First, we'll define the job for building the dist packages of your project "
85738580
"and storing them for later use:"
85748581
msgstr ""
85758582

8576-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:112
8583+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:118
85778584
msgid ""
85788585
"If you adapt this workflow to build multiple platform-specific wheels, use "
85798586
"uniquely named artifacts for each build job and adjust the download step "
85808587
"accordingly. The `cibuildwheel GitHub Actions examples`_ show a fuller wheel "
85818588
"matrix layout."
85828589
msgstr ""
85838590

8584-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:122
8591+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:128
85858592
msgid ""
85868593
"This will download your repository into the CI runner and then install and "
85878594
"activate the newest available Python 3 release."
85888595
msgstr ""
85898596

8590-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:125
8597+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:131
85918598
msgid ""
85928599
"And now we can build the dists from source and store them. In this example, "
85938600
"we'll use the ``build`` package. So add this to the steps list:"
85948601
msgstr ""
85958602

8596-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:135
8603+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:141
85978604
msgid "Defining a workflow job environment"
85988605
msgstr ""
85998606

8600-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:137
8607+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:143
86018608
msgid ""
86028609
"Now, let's add initial setup for our job that will publish to PyPI. It's a "
86038610
"process that will execute commands that we'll define later. In this guide, "
@@ -8608,75 +8615,75 @@ msgid ""
86088615
"implement secretless Trusted Publishing to PyPI."
86098616
msgstr ""
86108617

8611-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:151
8618+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157
86128619
msgid ""
86138620
"This will also ensure that the PyPI publishing workflow is only triggered if "
86148621
"the current commit is tagged."
86158622
msgstr ""
86168623

8617-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:155
8624+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:161
86188625
msgid "Publishing the distribution to PyPI"
86198626
msgstr ""
86208627

8621-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157
8628+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163
86228629
msgid "Finally, add the following steps at the end:"
86238630
msgstr ""
86248631

8625-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164
8632+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:170
86268633
msgid ""
86278634
"This step uses the `pypa/gh-action-pypi-publish`_ GitHub Action: after the "
86288635
"stored distribution package has been downloaded by the `download-artifact`_ "
86298636
"action, it uploads the contents of the ``dist/`` folder into PyPI "
86308637
"unconditionally."
86318638
msgstr ""
86328639

8633-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:171
8640+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:177
86348641
msgid ""
86358642
"Starting with version `v1.11.0 <https://github.com/pypa/gh-action-pypi-"
86368643
"publish/releases/tag/v1.11.0>`_, `pypa/gh-action-pypi-publish`_ generates "
86378644
"and uploads :pep:`740`-compatible attestations for each distribution by "
86388645
"default. No additional manual signing steps are required."
86398646
msgstr ""
86408647

8641-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179
8648+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185
86428649
msgid "Separate workflow for publishing to TestPyPI"
86438650
msgstr ""
86448651

8645-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181
8652+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187
86468653
msgid ""
86478654
"Now, repeat these steps and create another job for publishing to the "
86488655
"TestPyPI package index under the ``jobs`` section:"
86498656
msgstr ""
86508657

8651-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191
8658+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197
86528659
msgid ""
86538660
"Requiring manual approvals in the ``testpypi`` GitHub Environment is "
86548661
"typically unnecessary as it's designed to run on each commit to the main "
86558662
"branch and is often used to indicate a healthy release publishing pipeline."
86568663
msgstr ""
86578664

8658-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195
8665+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201
86598666
msgid "The whole CI/CD workflow"
86608667
msgstr ""
86618668

8662-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197
8669+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203
86638670
msgid ""
86648671
"This paragraph showcases the whole workflow after following the above guide."
86658672
msgstr ""
86668673

8667-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205
8674+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211
86688675
msgid "That's all, folks!"
86698676
msgstr ""
86708677

8671-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207
8678+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213
86728679
msgid ""
86738680
"Now, whenever you push a tagged commit to your Git repository remote on "
86748681
"GitHub, this workflow will publish it to PyPI. And it'll publish any push to "
86758682
"TestPyPI which is useful for providing test builds to your alpha users as "
86768683
"well as making sure that your release pipeline remains healthy!"
86778684
msgstr ""
86788685

8679-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215
8686+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221
86808687
msgid ""
86818688
"If your repository has frequent commit activity and every push is uploaded "
86828689
"to TestPyPI as described, the project might exceed the `PyPI project size "
@@ -8685,7 +8692,7 @@ msgid ""
86858692
"server like :ref:`pypiserver` in the CI for testing purposes."
86868693
msgstr ""
86878694

8688-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223
8695+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229
86898696
msgid ""
86908697
"It is recommended to keep the integrated GitHub Actions at their latest "
86918698
"versions, updating them frequently."

‎locales/ars/LC_MESSAGES/messages.po‎

Lines changed: 28 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ msgid ""
66
msgstr ""
77
"Project-Id-Version: Python Packaging User Guide\n"
88
"Report-Msgid-Bugs-To: \n"
9-
"POT-Creation-Date: 2026-08-11 10:39+0000\n"
9+
"POT-Creation-Date: 2026-08-19 11:32+0000\n"
1010
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
1111
"Last-Translator: Automatically generated\n"
1212
"Language-Team: none\n"
@@ -8560,37 +8560,44 @@ msgid ""
85608560
"respectively, and an additional job to build the distribution packages."
85618561
msgstr ""
85628562

8563-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:107
8563+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:109
8564+
msgid ""
8565+
"Keep the build job separate from the publishing jobs. Building distributions "
8566+
"in a publishing job is unsupported; publishing jobs should only download the "
8567+
"already-built artifacts and upload them."
8568+
msgstr ""
8569+
8570+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:113
85648571
msgid ""
85658572
"First, we'll define the job for building the dist packages of your project "
85668573
"and storing them for later use:"
85678574
msgstr ""
85688575

8569-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:112
8576+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:118
85708577
msgid ""
85718578
"If you adapt this workflow to build multiple platform-specific wheels, use "
85728579
"uniquely named artifacts for each build job and adjust the download step "
85738580
"accordingly. The `cibuildwheel GitHub Actions examples`_ show a fuller wheel "
85748581
"matrix layout."
85758582
msgstr ""
85768583

8577-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:122
8584+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:128
85788585
msgid ""
85798586
"This will download your repository into the CI runner and then install and "
85808587
"activate the newest available Python 3 release."
85818588
msgstr ""
85828589

8583-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:125
8590+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:131
85848591
msgid ""
85858592
"And now we can build the dists from source and store them. In this example, "
85868593
"we'll use the ``build`` package. So add this to the steps list:"
85878594
msgstr ""
85888595

8589-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:135
8596+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:141
85908597
msgid "Defining a workflow job environment"
85918598
msgstr ""
85928599

8593-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:137
8600+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:143
85948601
msgid ""
85958602
"Now, let's add initial setup for our job that will publish to PyPI. It's a "
85968603
"process that will execute commands that we'll define later. In this guide, "
@@ -8601,75 +8608,75 @@ msgid ""
86018608
"implement secretless Trusted Publishing to PyPI."
86028609
msgstr ""
86038610

8604-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:151
8611+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157
86058612
msgid ""
86068613
"This will also ensure that the PyPI publishing workflow is only triggered if "
86078614
"the current commit is tagged."
86088615
msgstr ""
86098616

8610-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:155
8617+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:161
86118618
msgid "Publishing the distribution to PyPI"
86128619
msgstr ""
86138620

8614-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:157
8621+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:163
86158622
msgid "Finally, add the following steps at the end:"
86168623
msgstr ""
86178624

8618-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:164
8625+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:170
86198626
msgid ""
86208627
"This step uses the `pypa/gh-action-pypi-publish`_ GitHub Action: after the "
86218628
"stored distribution package has been downloaded by the `download-artifact`_ "
86228629
"action, it uploads the contents of the ``dist/`` folder into PyPI "
86238630
"unconditionally."
86248631
msgstr ""
86258632

8626-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:171
8633+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:177
86278634
msgid ""
86288635
"Starting with version `v1.11.0 <https://github.com/pypa/gh-action-pypi-"
86298636
"publish/releases/tag/v1.11.0>`_, `pypa/gh-action-pypi-publish`_ generates "
86308637
"and uploads :pep:`740`-compatible attestations for each distribution by "
86318638
"default. No additional manual signing steps are required."
86328639
msgstr ""
86338640

8634-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:179
8641+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:185
86358642
msgid "Separate workflow for publishing to TestPyPI"
86368643
msgstr ""
86378644

8638-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:181
8645+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:187
86398646
msgid ""
86408647
"Now, repeat these steps and create another job for publishing to the "
86418648
"TestPyPI package index under the ``jobs`` section:"
86428649
msgstr ""
86438650

8644-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:191
8651+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197
86458652
msgid ""
86468653
"Requiring manual approvals in the ``testpypi`` GitHub Environment is "
86478654
"typically unnecessary as it's designed to run on each commit to the main "
86488655
"branch and is often used to indicate a healthy release publishing pipeline."
86498656
msgstr ""
86508657

8651-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:195
8658+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:201
86528659
msgid "The whole CI/CD workflow"
86538660
msgstr ""
86548661

8655-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:197
8662+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:203
86568663
msgid ""
86578664
"This paragraph showcases the whole workflow after following the above guide."
86588665
msgstr ""
86598666

8660-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:205
8667+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:211
86618668
msgid "That's all, folks!"
86628669
msgstr ""
86638670

8664-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:207
8671+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:213
86658672
msgid ""
86668673
"Now, whenever you push a tagged commit to your Git repository remote on "
86678674
"GitHub, this workflow will publish it to PyPI. And it'll publish any push to "
86688675
"TestPyPI which is useful for providing test builds to your alpha users as "
86698676
"well as making sure that your release pipeline remains healthy!"
86708677
msgstr ""
86718678

8672-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:215
8679+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:221
86738680
msgid ""
86748681
"If your repository has frequent commit activity and every push is uploaded "
86758682
"to TestPyPI as described, the project might exceed the `PyPI project size "
@@ -8678,7 +8685,7 @@ msgid ""
86788685
"server like :ref:`pypiserver` in the CI for testing purposes."
86798686
msgstr ""
86808687

8681-
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:223
8688+
#: ../source/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows.rst:229
86828689
msgid ""
86838690
"It is recommended to keep the integrated GitHub Actions at their latest "
86848691
"versions, updating them frequently."

0 commit comments

Comments
 (0)