[dependabot]

Bumps the actions group with 4 updates: huggingface/doc-builder/.github/workflows/build_main_documentation.yml, huggingface/doc-builder/.github/workflows/build_pr_documentation.yml, huggingface/doc-builder/.github/workflows/delete_doc_comment_trigger.yml and huggingface/doc-builder/.github/workflows/upload_pr_documentation.yml.

Updates huggingface/doc-builder/.github/workflows/build_main_documentation.yml from 90b4ee2c10b81b5c1a6367c4e6fc9e2fb510a7e3 to cf20b09f274383f0d91a7055c5e43f0a2ab3d1a3

Changelog

Sourced from huggingface/doc-builder/.github/workflows/build_main_documentation.yml's changelog.

Release checklist

1. Checkout the release branch (for a patch the current release branch, for a new minor version, create one):

   git checkout -b vXX.xx-release

   The -b is only necessary for creation (so remove it when doing a patch).
2. Change the version in src/doc_builder/__init__.py and pyproject.toml to the proper value.
3. Commit these changes with the message: "Release: v<VERSION>".
4. Add a tag in git to mark the release:

   git tag v<VERSION> -m 'Adds tag v<VERSION> for pypi'

   Push the tag and release commit to git:

   git push --tags origin vXX.xx-release

5. Build the source distribution and the wheel in the top-level directory:

   rm -rf dist
   uv build

6. Upload the package to the pypi test server first:

   twine upload dist/* -r testpypi

7. Check that you can install it in a virtualenv by running:

   pip install hf-doc-builder
   pip uninstall hf-doc-builder
   pip install -i https://test.pypi.org/simple/ hf-doc-builder

   It's recommended to check that there are no issues building the docs, so try running a command like doc-builder.
8. Upload the final version to actual pypi:

   twine upload dist/* -r pypi

9. Add release notes to the tag in github once everything is looking hunky-dory.
10. Go back to the main branch and update the version in src/doc_builder/__init__.py and pyproject.toml to the new version ".dev" and push to main.

Commits

• cf20b09 Revert "Comment out schedule for search engine population (#826)" (#827)
• 9978a41 Comment out schedule for search engine population (#826)
• c2d27f6 Fix vectorless Meilisearch document payload (#825)
• 953aa44 Add vectorless full-text docs ingestion (#824)
• 1b16dac Remove setup.py in favor of pyproject.toml (#816)
• bcd143e Check anchors in links (#820)
• 68667a5 fix(kit): accept a lowercase region in language codes (pt-br) (#823)
• 0ab9ea0 Ship a pre-commit hook for doc-builder style (#818)
• 4a56e30 Escape HTML and strip ANSI codes in notebook-to-mdx text outputs (#819)
• da05e70 delete-old-prs: use a trusted publisher instead of the HF_ACCESS_TOKEN secret...
• Additional commits viewable in compare view

Updates huggingface/doc-builder/.github/workflows/build_pr_documentation.yml from 90b4ee2c10b81b5c1a6367c4e6fc9e2fb510a7e3 to cf20b09f274383f0d91a7055c5e43f0a2ab3d1a3

Changelog

Sourced from huggingface/doc-builder/.github/workflows/build_pr_documentation.yml's changelog.

Release checklist

1. Checkout the release branch (for a patch the current release branch, for a new minor version, create one):

   git checkout -b vXX.xx-release

   The -b is only necessary for creation (so remove it when doing a patch).
2. Change the version in src/doc_builder/__init__.py and pyproject.toml to the proper value.
3. Commit these changes with the message: "Release: v<VERSION>".
4. Add a tag in git to mark the release:

   git tag v<VERSION> -m 'Adds tag v<VERSION> for pypi'

   Push the tag and release commit to git:

   git push --tags origin vXX.xx-release

5. Build the source distribution and the wheel in the top-level directory:

   rm -rf dist
   uv build

6. Upload the package to the pypi test server first:

   twine upload dist/* -r testpypi

7. Check that you can install it in a virtualenv by running:

   pip install hf-doc-builder
   pip uninstall hf-doc-builder
   pip install -i https://test.pypi.org/simple/ hf-doc-builder

   It's recommended to check that there are no issues building the docs, so try running a command like doc-builder.
8. Upload the final version to actual pypi:

   twine upload dist/* -r pypi

9. Add release notes to the tag in github once everything is looking hunky-dory.
10. Go back to the main branch and update the version in src/doc_builder/__init__.py and pyproject.toml to the new version ".dev" and push to main.

Commits

• cf20b09 Revert "Comment out schedule for search engine population (#826)" (#827)
• 9978a41 Comment out schedule for search engine population (#826)
• c2d27f6 Fix vectorless Meilisearch document payload (#825)
• 953aa44 Add vectorless full-text docs ingestion (#824)
• 1b16dac Remove setup.py in favor of pyproject.toml (#816)
• bcd143e Check anchors in links (#820)
• 68667a5 fix(kit): accept a lowercase region in language codes (pt-br) (#823)
• 0ab9ea0 Ship a pre-commit hook for doc-builder style (#818)
• 4a56e30 Escape HTML and strip ANSI codes in notebook-to-mdx text outputs (#819)
• da05e70 delete-old-prs: use a trusted publisher instead of the HF_ACCESS_TOKEN secret...
• Additional commits viewable in compare view

Updates huggingface/doc-builder/.github/workflows/delete_doc_comment_trigger.yml from 90b4ee2c10b81b5c1a6367c4e6fc9e2fb510a7e3 to cf20b09f274383f0d91a7055c5e43f0a2ab3d1a3

Changelog

Sourced from huggingface/doc-builder/.github/workflows/delete_doc_comment_trigger.yml's changelog.

Release checklist

1. Checkout the release branch (for a patch the current release branch, for a new minor version, create one):

   git checkout -b vXX.xx-release

   The -b is only necessary for creation (so remove it when doing a patch).
2. Change the version in src/doc_builder/__init__.py and pyproject.toml to the proper value.
3. Commit these changes with the message: "Release: v<VERSION>".
4. Add a tag in git to mark the release:

   git tag v<VERSION> -m 'Adds tag v<VERSION> for pypi'

   Push the tag and release commit to git:

   git push --tags origin vXX.xx-release

5. Build the source distribution and the wheel in the top-level directory:

   rm -rf dist
   uv build

6. Upload the package to the pypi test server first:

   twine upload dist/* -r testpypi

7. Check that you can install it in a virtualenv by running:

   pip install hf-doc-builder
   pip uninstall hf-doc-builder
   pip install -i https://test.pypi.org/simple/ hf-doc-builder

   It's recommended to check that there are no issues building the docs, so try running a command like doc-builder.
8. Upload the final version to actual pypi:

   twine upload dist/* -r pypi

9. Add release notes to the tag in github once everything is looking hunky-dory.
10. Go back to the main branch and update the version in src/doc_builder/__init__.py and pyproject.toml to the new version ".dev" and push to main.

Commits

• cf20b09 Revert "Comment out schedule for search engine population (#826)" (#827)
• 9978a41 Comment out schedule for search engine population (#826)
• c2d27f6 Fix vectorless Meilisearch document payload (#825)
• 953aa44 Add vectorless full-text docs ingestion (#824)
• 1b16dac Remove setup.py in favor of pyproject.toml (#816)
• bcd143e Check anchors in links (#820)
• 68667a5 fix(kit): accept a lowercase region in language codes (pt-br) (#823)
• 0ab9ea0 Ship a pre-commit hook for doc-builder style (#818)
• 4a56e30 Escape HTML and strip ANSI codes in notebook-to-mdx text outputs (#819)
• da05e70 delete-old-prs: use a trusted publisher instead of the HF_ACCESS_TOKEN secret...
• Additional commits viewable in compare view

Updates huggingface/doc-builder/.github/workflows/upload_pr_documentation.yml from 9ad2de8582b56c017cb530c1165116d40433f1c6 to cf20b09f274383f0d91a7055c5e43f0a2ab3d1a3

Changelog

Sourced from huggingface/doc-builder/.github/workflows/upload_pr_documentation.yml's changelog.

Release checklist

1. Checkout the release branch (for a patch the current release branch, for a new minor version, create one):

   git checkout -b vXX.xx-release

   The -b is only necessary for creation (so remove it when doing a patch).
2. Change the version in src/doc_builder/__init__.py and pyproject.toml to the proper value.
3. Commit these changes with the message: "Release: v<VERSION>".
4. Add a tag in git to mark the release:

   git tag v<VERSION> -m 'Adds tag v<VERSION> for pypi'

   Push the tag and release commit to git:

   git push --tags origin vXX.xx-release

5. Build the source distribution and the wheel in the top-level directory:

   rm -rf dist
   uv build

6. Upload the package to the pypi test server first:

   twine upload dist/* -r testpypi

7. Check that you can install it in a virtualenv by running:

   pip install hf-doc-builder
   pip uninstall hf-doc-builder
   pip install -i https://test.pypi.org/simple/ hf-doc-builder

   It's recommended to check that there are no issues building the docs, so try running a command like doc-builder.
8. Upload the final version to actual pypi:

   twine upload dist/* -r pypi

9. Add release notes to the tag in github once everything is looking hunky-dory.
10. Go back to the main branch and update the version in src/doc_builder/__init__.py and pyproject.toml to the new version ".dev" and push to main.

Commits

• cf20b09 Revert "Comment out schedule for search engine population (#826)" (#827)
• 9978a41 Comment out schedule for search engine population (#826)
• c2d27f6 Fix vectorless Meilisearch document payload (#825)
• 953aa44 Add vectorless full-text docs ingestion (#824)
• 1b16dac Remove setup.py in favor of pyproject.toml (#816)
• bcd143e Check anchors in links (#820)
• 68667a5 fix(kit): accept a lowercase region in language codes (pt-br) (#823)
• 0ab9ea0 Ship a pre-commit hook for doc-builder style (#818)
• 4a56e30 Escape HTML and strip ANSI codes in notebook-to-mdx text outputs (#819)
• da05e70 delete-old-prs: use a trusted publisher instead of the HF_ACCESS_TOKEN secret...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions