docs(how-tos): add multiple version bootstrap guide

[rd4398]

Add a new how-to guide documenting the --multiple-versions flag for the bootstrap and bootstrap-parallel commands. Covers enabling the mode, how resolution and error handling work, flag interactions, and a complete example with verification steps.

Closes: #1110

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e0549e36-18ed-4693-849d-106bf8ee57a7

📥 Commits

Reviewing files that changed from the base of the PR and between 9fb5656 and 08ee4ba.

📒 Files selected for processing (2)

• docs/how-tos/index.rst
• docs/how-tos/multiple-version-bootstrap.rst

✅ Files skipped from review due to trivial changes (2)

• docs/how-tos/index.rst
• docs/how-tos/multiple-version-bootstrap.rst

---

📝 Walkthrough

Walkthrough

This PR adds documentation for the --multiple-versions feature. A new how-to guide (multiple-version-bootstrap.rst) explains how the flag changes resolution and build behavior to include all matching package versions rather than only the highest, distinguishes it from --skip-constraints, describes usage scenarios, covers configuration methods (CLI and requirements files), outlines operational steps, documents expected outputs, and documents interactions with other flags. An index entry in docs/how-tos/index.rst registers the new documentation under "Build Configuration" for discoverability.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: adding a new how-to guide for the multiple-version bootstrap feature.
Description check	✅ Passed	The description is directly related to the changeset, explaining what guide was added and what it covers, with reference to the closing issue.
Linked Issues check	✅ Passed	The PR fully addresses both objectives from issue #1110: documenting how to enable multiple-version bootstrap mode and how it works, with comprehensive coverage in the new guide.
Out of Scope Changes check	✅ Passed	All changes are scoped to documentation updates directly related to the linked issue requirements, with no extraneous modifications.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

docs/how-tos/index.rst (1)

50-50: ⚡ Quick win

Add a Sphinx change directive for this user-facing index update.

The new guide entry is user-facing; add a nearby .. versionchanged:: (or .. versionadded::) note to keep docs change history consistent.

As per coding guidelines, "**/*.{rst,py}: Use Sphinx versionadded, versionremoved, versionchanged directives for user-facing changes".

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/how-tos/index.rst` at line 50, Add a Sphinx version directive next to
the new entry "multiple-version-bootstrap": insert a nearby ".. versionadded::
<version>" (or ".. versionchanged:: <version>") directive directly above or
below the "multiple-version-bootstrap" line with a short one-line description of
the user-facing change, using proper RST indentation and blank-line separation
so the directive is associated with that entry.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/how-tos/multiple-version-bootstrap.rst`:
- Around line 41-44: Shell will interpret the requirement specifier in the
examples as redirection; update the two examples that call "fromager bootstrap
--multiple-versions requests>=2.28" and "fromager bootstrap-parallel
--multiple-versions requests>=2.28" to wrap the requirement specifier in quotes
(e.g. "requests>=2.28") so the shell treats it as a single argument rather than
performing output redirection.

---

Nitpick comments:
In `@docs/how-tos/index.rst`:
- Line 50: Add a Sphinx version directive next to the new entry
"multiple-version-bootstrap": insert a nearby ".. versionadded:: <version>" (or
".. versionchanged:: <version>") directive directly above or below the
"multiple-version-bootstrap" line with a short one-line description of the
user-facing change, using proper RST indentation and blank-line separation so
the directive is associated with that entry.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ddda7291-d77d-40b6-a9ab-6809e88e98c7

📥 Commits

Reviewing files that changed from the base of the PR and between 2132ef3 and 9fb5656.

📒 Files selected for processing (2)

• docs/how-tos/index.rst
• docs/how-tos/multiple-version-bootstrap.rst

[rd4398]

@mergify rebase

[mergify]

Deprecation notice: This pull request comes from a fork and was rebased using bot_account impersonation. This capability will be removed on July 1, 2026. After this date, the rebase action will no longer be able to rebase fork pull requests with this configuration. Please switch to the update action/command to ensure compatibility going forward.

[mergify]

rebase

✅ Branch has been successfully rebased