You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "devmdr (via GitHub)" <gi...@apache.org> on 2025/08/06 14:48:52 UTC
[D] Update from 5.0.0rc2 to 5.0.0 using pip [superset]
GitHub user devmdr created a discussion: Update from 5.0.0rc2 to 5.0.0 using pip
Hi,
I have installed version 5.0.0rc2 using pip and I want to upgrade to the latest keeping the dashboards, charts, users etc.
How to do it correctly and safely? Are the following steps sufficient?
```
01. # full backup
02. # activate venv
03. pip install --upgrade apache-superset==5.0.0rc3
04. superset db upgrade
05. superset init
06. pip install --upgrade apache-superset==5.0.0rc4
07. superset db upgrade
08. superset init
09. pip install --upgrade apache-superset==5.0.0
10. superset db upgrade
11. superset init
12. superset assets build # finally, once
```
GitHub link: https://github.com/apache/superset/discussions/34579
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Update from 5.0.0rc2 to 5.0.0 using pip [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Update from 5.0.0rc2 to 5.0.0 using pip
<!-- Answer -->
Your steps are almost correct, but there's a key migration issue between 5.0.0rc2 and later versions: two migration scripts present in rc2 were removed in rc3 and beyond. If you already ran migrations with rc2, upgrading to rc3 or 5.0.0 will likely fail with an error like "Can't locate revision identified by '32bf93dfe2a4'" unless you manually downgrade your metadata database to revision `74ad1125881c` before proceeding. This is a known issue and not automatically patched in the final 5.0.0 release [[details]](https://github.com/apache/superset/issues/33739).
The safest upgrade path is:
1. Full backup of your metadata database.
2. Activate your venv.
3. Upgrade directly to the target version:
`pip install --upgrade apache-superset==5.0.0`
4. If you see a migration error about missing revisions, run:
`superset db downgrade 74ad1125881c`
5. Then run:
`superset db upgrade`
6. `superset init`
7. `superset assets build` (if you build frontend assets)
You do not need to upgrade through every release candidate; upgrading directly to 5.0.0 and running the migration commands is the recommended approach [[docs]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/installation/upgrading-superset.mdx). Backing up first is essential to preserve dashboards, charts, and users. If you already hit the migration error, the manual downgrade step above will resolve it.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=e33f8bba-9084-4358-942d-90c7c2c8f48d) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/34579#discussioncomment-14022036
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Update from 5.0.0rc2 to 5.0.0 using pip [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Update from 5.0.0rc2 to 5.0.0 using pip
<!-- Answer -->
Your steps are almost correct, but there's a key migration issue between 5.0.0rc2 and later versions: two migration scripts present in rc2 were removed in rc3 and beyond. If you already ran migrations with rc2, upgrading to rc3 or 5.0.0 will likely fail with an error like "Can't locate revision identified by '32bf93dfe2a4'" unless you manually downgrade your metadata database to revision `74ad1125881c` before proceeding. This is a known issue and not automatically patched in the final 5.0.0 release [[details]](https://github.com/apache/superset/issues/33739).
The safest upgrade path is:
1. Full backup of your metadata database.
2. Activate your venv.
3. Upgrade directly to the target version:
`pip install --upgrade apache-superset==5.0.0`
4. If you see a migration error about missing revisions, run:
`superset db downgrade 74ad1125881c`
5. Then run:
`superset db upgrade`
6. `superset init`
7. `superset assets build` (if you build frontend assets)
You do not need to upgrade through every release candidate; upgrading directly to 5.0.0 and running the migration commands is the recommended approach [[docs]](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/installation/upgrading-superset.mdx). Backing up first is essential to preserve dashboards, charts, and users. If you already hit the migration error, the manual downgrade step above will resolve it.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/e33f8bba-9084-4358-942d-90c7c2c8f48d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e33f8bba-9084-4358-942d-90c7c2c8f48d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e33f8bba-9084-4358-942d-90c7c2c8f48d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e33f8bba-9084-4358-942d-90c7c2c8f48d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e33f8bba-9084-4358-942d-90c7c2c8f48d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e33f8bba-9084-4358-942d-90c7c2c8f48d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e33f8bba-9084-4358-942d-90c7c2c8f48d?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34579)
GitHub link: https://github.com/apache/superset/discussions/34579#discussioncomment-14022036
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org