-
-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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.
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
1.3.0-SNAPSHOT upgrading to the latest version need help? #5085
Comments
🤖 Hey there, @majinding! Nice to see you back in our issue threads. Hope you're doing well! Based on the changes between version 1.3.0-SNAPSHOT and the latest version 2.2.0 of Apollo, there are several significant updates and fixes. However, there doesn't seem to be any specific mention of data migration. The changes mostly revolve around bug fixes, feature enhancements, and version upgrades of dependencies. To upgrade from Apollo 1.3.0-SNAPSHOT to Apollo 2.2.0, you would need to follow the steps outlined in the Apollo Release Guide. This includes upgrading the version, writing release reports, version validation, version release, and release announcement. Please note that these steps assume that you have the necessary permissions and access to perform these operations. If you encounter any issues during the upgrade process, please provide specific details so I can assist you further. For a detailed list of changes, you can refer to the changes document for Apollo 2.2.0. SourcesThis response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. |
Numerous database schema modifications and data migration procedures are required. Please consult the release notes spanning versions 1.3.0 to 2.2.0. For detailed instructions, refer to the "How to Upgrade from xxx to xxx" section. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 7 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions. |
The company is still using 1.3.0-SNAPSHOT. Could you please tell me if upgrading to the latest version would involve significant data migration?
Are there any upgrade documents available?
The text was updated successfully, but these errors were encountered: