Skip to content

Clarify upgrade process for multi-node environments #39345

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vgrl merged 3 commits into from
Jul 17, 2025
Merged

Clarify upgrade process for multi-node environments #39345

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3f5ad23
Clarify upgrade process for multi-node environments
Fuzzwah Jul 16, 2025
a18ce0d
Update content/admin/upgrading-your-instance/performing-an-upgrade/up…
Sharra-writes Jul 16, 2025
2c49a73
Merge branch 'main' into patch-2
vgrl Jul 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...rading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea

## Upgrading an instance with multiple nodes using an upgrade package

To upgrade an instance that comprises multiple nodes using an upgrade package, you must upgrade the primary node, then upgrade any additional nodes.
To upgrade a multi-node GitHub Enterprise Server environment using an upgrade package, you must first upgrade the primary node and wait for its configuration run to complete successfully. Only after the primary is fully upgraded and configured can you proceed to upgrade any replica or additional nodes. Attempting to upgrade other nodes before the primary is complete will result in upgrade failures.
Copy link

Copilot AI Jul 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The text 'GitHub Enterprise Server' should use the Liquid variable {% data variables.product.prodname_ghe_server %} instead of hardcoded text to ensure consistency and easier global updates.

Copilot generated this review using guidance from repository custom instructions.
Comment thread
Sharra-writes marked this conversation as resolved.
Outdated

* [Upgrading the primary node with an upgrade package](#upgrading-the-primary-node-with-an-upgrade-package)
* [Upgrading additional nodes with an upgrade package](#upgrading-additional-nodes-with-an-upgrade-package)
Expand Down
Loading