Upgrades and versioning
Use the documentation that matches the version you are operating. The Latest (main) docs may describe changes not present in an older installation; select its N.x documentation snapshot when available.
Before an upgrade
- Read the release notes and version-matched configuration reference.
- Record the currently running revision.
- Create a complete backup and verify archive integrity.
- Confirm the previous package or source revision remains available for rollback.
- Validate the new configuration before exposing the service.
During the upgrade
Stop the existing Jiandu process before starting the replacement. Do not run old and new processes concurrently against the same installation. Watch startup diagnostics and readiness before returning public traffic.
After the upgrade
Sign in through the public origin, search, open old and recent originals, confirm restricted access with a Member account, and check each enabled connector. Keep the rollback window open until these checks and a fresh backup complete.
Documentation release tags
The documentation site publishes a major snapshot for exact tags such as v1.0.0 (and the repository's four-part equivalent v1.0.0.0). Patch and prerelease tags do not create another 1.x snapshot. This keeps one durable documentation line per major release while main continues at Latest.