Manual Upgrade from v0.25.2 to v0.28.0(latest)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
anyone know how upgrade from v0.25.2 to latest v0.28.0
- with a manual deployment like in portainer?
- i tried using the
docker-compose.yml&.envfrom download script - copied over previous plane volumes to a new directory, used same permissions on folders, and updated volume mounts in portainer/new plane stack
- used and updated to new .env
- set up custom docker networking
- expose plane-proxy with my own reverse proxy / traefik
it runs and i see the migrator applying changes then migrator shuts down (as expected)
Migrator logs look fine:
Applying db.0025_auto_20230331_0203... OK
Applying db.0026_alter_projectmember_view_props... OK
Applying db.0027_auto_20230409_0312... OK
Applying db.0028_auto_20230414_1703... OK
Applying db.0029_auto_20230502_0126... OK
Applying db.0030_alter_estimatepoint_unique_together... OK
Applying db.0031_analyticview... OK
Applying db.0032_auto_20230520_2015... OK
Applying db.0033_auto_20230618_2125... OK
Applying db.0034_auto_20230628_1046... OK
Applying db.0035_auto_20230704_2225... OK
Applying db.0036_alter_workspace_organization_size... OK
Applying db.0037_issue_archived_at_project_archive_in_and_more... OK
Applying db.0038_auto_20230720_1505... OK
Applying db.0039_auto_20230723_2203... OK
Applying db.0040_projectmember_preferences_user_cover_image_and_more... OK
Applying db.0041_cycle_sort_order_issuecomment_access_and_more... OK
Applying db.0042_alter_analyticview_created_by_and_more... OK
Applying db.0043_alter_analyticview_created_by_and_more... OK
Applying db.0044_auto_20230913_0709... OK
Applying db.0045_issueactivity_epoch_workspacemember_issue_props_and_more... OK
Applying db.0046_label_sort_order_alter_analyticview_created_by_and_more... OK
Applying db.0047_webhook_apitoken_description_apitoken_expired_at_and_more... OK
Applying db.0048_auto_20231116_0713... OK
Applying db.0049_auto_20231116_0713... OK
Applying db.0050_user_use_case_alter_workspace_organization_size... OK
Applying db.0051_cycle_external_id_cycle_external_source_and_more... OK
Applying db.0052_auto_20231220_1141... OK
Applying db.0053_auto_20240102_1315... OK
Applying db.0054_dashboard_widget_dashboardwidget... OK
Applying db.0055_auto_20240108_0648... OK
Applying db.0056_usernotificationpreference_emailnotificationlog... OK
Applying db.0057_auto_20240122_0901... OK
Applying db.0058_alter_moduleissue_issue_and_more... OK
Applying db.0059_auto_20240208_0957... OK
Applying db.0060_cycle_progress_snapshot... OK
Applying db.0061_project_logo_props... OK
Applying db.0062_cycle_archived_at_module_archived_at_and_more... OK
Applying db.0063_state_is_triage_alter_state_group... OK
Applying db.0064_auto_20240409_1134... OK
Applying db.0065_auto_20240415_0937... OK
Applying db.0066_account_id_token_cycle_logo_props_module_logo_props... OK
Applying db.0067_issue_estimate... OK
Applying db.0068_remove_pagelabel_project_remove_pagelog_project_and_more... OK
Applying db.0069_alter_account_provider_and_more... OK
Applying db.0070_apitoken_is_service_exporterhistory_filters_and_more... OK
Applying db.0071_rename_issueproperty_issueuserproperty_and_more... OK
Applying db.0072_issueattachment_external_id_and_more... OK
Applying db.0073_alter_commentreaction_unique_together_and_more... OK
Applying db.0074_deploy_board_and_project_issues... OK
Applying db.0075_alter_fileasset_asset... OK
Applying db.0076_alter_projectmember_role_and_more... OK
Applying db.0077_draftissue_cycle_user_timezone_project_user_timezone_and_more... OK
Applying db.0078_fileasset_comment_fileasset_entity_type_and_more... OK
Applying db.0079_auto_20241009_0619... OK
Applying db.0080_fileasset_draft_issue_alter_fileasset_entity_type... OK
Applying db.0081_remove_globalview_created_by_and_more... OK
Applying db.0082_alter_issue_managers_alter_cycleissue_issue_and_more... OK
Applying db.0083_device_workspace_timezone_and_more... OK
Applying db.0084_remove_label_label_unique_name_project_when_deleted_at_null_and_more... OK
Applying db.0085_intake_intakeissue_remove_inboxissue_created_by_and_more... OK
Applying db.0086_issueversion_alter_teampage_unique_together_and_more... OK
Applying db.0087_remove_issueversion_description_and_more... OK
Applying db.0088_sticky_sort_order_workspaceuserlink... OK
Applying db.0089_workspacehomepreference_and_more... OK
Applying db.0090_rename_dashboard_deprecateddashboard_and_more... OK
Applying db.0091_issuecomment_edited_at_and_more... OK
Applying db.0092_alter_deprecateddashboardwidget_unique_together_and_more... OK
Applying db.0093_page_moved_to_page_page_moved_to_project_and_more... OK
Applying db.0094_auto_20250425_0902... OK
Applying db.0095_page_external_id_page_external_source... OK
Applying db.0096_user_is_email_valid_user_masked_at... OK
Applying db.0097_project_external_id_project_external_source... OK
Applying db.0098_profile_is_app_rail_docked_and_more... OK
Applying django_celery_beat.0001_initial... OK
Applying django_celery_beat.0002_auto_20161118_0346... OK
Applying django_celery_beat.0003_auto_20161209_0049... OK
Applying django_celery_beat.0004_auto_20170221_0000... OK
Applying django_celery_beat.0005_add_solarschedule_events_choices... OK
Applying django_celery_beat.0006_auto_20180322_0932... OK
Applying django_celery_beat.0007_auto_20180521_0826... OK
Applying django_celery_beat.0008_auto_20180914_1922... OK
Applying django_celery_beat.0006_auto_20180210_1226... OK
Applying django_celery_beat.0006_periodictask_priority... OK
Applying django_celery_beat.0009_periodictask_headers... OK
Applying django_celery_beat.0010_auto_20190429_0326... OK
Applying django_celery_beat.0011_auto_20190508_0153... OK
Applying django_celery_beat.0012_periodictask_expire_seconds... OK
Applying django_celery_beat.0013_auto_20200609_0727... OK
Applying django_celery_beat.0014_remove_clockedschedule_enabled... OK
Applying django_celery_beat.0015_edit_solarschedule_events_choices... OK
Applying django_celery_beat.0016_alter_crontabschedule_timezone... OK
Applying django_celery_beat.0017_alter_crontabschedule_month_of_year... OK
Applying django_celery_beat.0018_improve_crontab_helptext... OK
Applying license.0001_initial... OK
Applying license.0002_rename_version_instance_current_version_and_more... OK
Applying license.0003_alter_changelog_title_alter_changelog_version_and_more... OK
Applying license.0004_changelog_deleted_at_instance_deleted_at_and_more... OK
Applying license.0005_rename_product_instance_edition_and_more... OK
Applying sessions.0001_initial... OK
but when i access the new plane instance it works as a brand new instance of plane vs. bringing over all my old projects, config, work items, etc
thanks in advance for any help 🙏🏻
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the docker-compose.yml and .env used for the new deployment, then compare the copied Plane volumes and their mounts in Portainer. Check how the migrator completed while the new instance remained empty. Done means the upgraded instance shows the previous projects, configuration, and work items.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100