docs: simplify Docker image pinning documentation

[d-bytebase]

Summary

• Moved Docker image pinning instructions from upgrade.mdx to production-setup.mdx for better discoverability
• Simplified the explanation to focus on essential information about SHA256 digests
• Cleaned up outdated content about version management and complex restoration procedures

Changes

• Move Docker image version pinning section to production setup checklist
• Simplify wording and focus on practical usage
• Remove outdated version management section
• Remove complex database restoration steps that are rarely needed
• Delete unused change-migration-history.webp image

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
bytebase-com	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 11, 2025 9:12am

[Copilot]

Pull Request Overview

This PR simplifies and consolidates Docker image pinning documentation by moving it from the upgrade guide to the production setup checklist for better discoverability. The changes focus on practical usage while removing outdated and complex restoration procedures.

• Moved Docker image pinning instructions from upgrade.mdx to production-setup.mdx
• Simplified migration history restoration steps by removing complex dump file modification procedures
• Removed extensive version management documentation and downgrade procedures

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File	Description
upgrade.mdx	Removed complex database restoration steps, version management section, and Docker image pinning documentation
production-setup.mdx	Added simplified Docker image pinning guidance with SHA256 digest example

[github-actions]

📝 Broken Links Check Report

Note: Entries under /api-reference/ are likely false positives and can be ignored.

The following is the output from the broken links check:

found 16 broken links in 9 files

integrations/api/audit-log.mdx
 ⎿  /api-reference/auditlogservice/post-v1auditlogs:search

integrations/api/authentication.mdx
 ⎿  /api-reference/authservice/post-v1authlogin

integrations/api/data-classification.mdx
 ⎿  /api-reference/settingservice/patch-v1settings
 ⎿  /api-reference/databaseservice/patch-v1instances-databases

integrations/api/issue.mdx
 ⎿  /api-reference/issueservice/post-v1projects-issues

integrations/api/permission.mdx
 ⎿  /api-reference/workspaceservice/get-v1workspaces-:getIamPolicy
 ⎿  /api-reference/projectservice/get-v1projects-:getIamPolicy
 ⎿  /api-reference/roleservice/get-v1roles
 ⎿  /api-reference/userservice/get-v1users
 ⎿  /api-reference/groupservice/get-v1groups

integrations/api/plan.mdx
 ⎿  /api-reference/planservice/post-v1projects-plans
 ⎿  /api-reference/sheetservice/post-v1projects-sheets

integrations/api/release.mdx
 ⎿  /api-reference/releaseservice/post-v1projects-releases

integrations/api/rollout.mdx
 ⎿  /api-reference/rolloutservice/post-v1projects-rollouts

integrations/api/sql-review.mdx
 ⎿  /api-reference/releaseservice/post-v1projects-releases:check
 ⎿  /api-reference/sqlservice/post-v1sqlcheck

[tianzhou]

I see that we also removed upgrade from old version. But we still get asked about how to get upgraded from old version occasionally.

[d-bytebase]

I see that we also removed upgrade from old version. But we still get asked about how to get upgraded from old version occasionally.

It will be there, just remove the current legacy content to reduce noise for Claude.