jbat opened a new issue, #34643: URL: https://github.com/apache/superset/issues/34643
### Bug description The bug is that following the Quickstart guide installs 4.1.3, not 5.0.0 as expected. [Quickstart guide](https://superset.apache.org/docs/quickstart#2-start-the-latest-official-release-of-superset) Had to set the TAG env var to 5.0.0 to get the latest image As per https://github.com/apache/superset/blob/master/docker-compose-image-tag.yml#L27 the emage pulled will either be TAG or latest-dev ``` x-superset-image: &superset-image apachesuperset.docker.scarf.sh/apache/superset:${TAG:-latest-dev} ``` Seems currently the latest-dev is pointing to 4.1.3 .. potentially as that is the latest release pushed as per [#release-announcements](https://apache-superset.slack.com/archives/CH307T4JG) latest posts Started with a clean slate, removed all prior images ```shell # no TAG env var set echo $TAG nil # no docker images docker image ls REPOSITORY TAG IMAGE ID CREATED SIZE superset git:(master) git pull superset git:(master) git checkout tags/5.0.0 superset git:(5.0.0) docker compose -f docker-compose-image-tag.yml up superset git:(5.0.0) docker image ls REPOSITORY TAG IMAGE ID CREATED SIZE apachesuperset.docker.scarf.sh/apache/superset latest-dev a78d442cb598 4 weeks ago 4.71GB redis 7 49061c0de571 4 weeks ago 195MB postgres 15 5ab68e212eab 2 months ago 628MB superset git:(5.0.0) docker exec -it superset_app superset version -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Superset 4.1.3 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ``` Setting TAG env var to 5.0.0 results in the correct install ``` superset git:(5.0.0) export TAG=5.0.0 superset git:(5.0.0) echo $TAG 5.0.0 superset git:(5.0.0) docker compose -f docker-compose-image-tag.yml up superset git:(5.0.0) docker image ls REPOSITORY TAG IMAGE ID CREATED SIZE apachesuperset.docker.scarf.sh/apache/superset latest-dev a78d442cb598 4 weeks ago 4.71GB redis 7 49061c0de571 4 weeks ago 195MB apachesuperset.docker.scarf.sh/apache/superset 5.0.0 270e7ee9577b 6 weeks ago 3.57GB postgres 15 5ab68e212eab 2 months ago 628MB superset git:(5.0.0) docker exec -it superset_app superset version -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Superset 5.0.0 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ``` ### Potential Solution As per suggestion by @sfirke in [slack](https://apache-superset.slack.com/archives/C06AQP5CCQG/p1754918640344109?thread_ts=1754698761.581059&cid=C06AQP5CCQG) - Someone with our Docker Hub credentials should manually tag 5.0.0-dev as latest-dev - We should see if anything needs to be fixed in the release process logic so that if the current version associated with latest is semantically greater than the one being released, it doesn't overwrite the tag ### Screenshots/recordings _No response_ ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### Browser Chrome ### Additional context _No response_ ### Checklist - [ ] I have searched Superset docs and Slack and didn't find a solution to my problem. - [ ] I have searched the GitHub issue tracker and didn't find a similar bug report. - [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
