Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Superset
  3. Superset - Package Updates

Superset - Package Updates

Scheduled Pinned Locked Moved Superset
32 Posts 3 Posters 4.8k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • nebulonN Offline
    nebulonN Offline
    nebulon
    Staff
    wrote on last edited by
    #23

    [1.6.3]

    • Update Superset to 4.0.2
    • Full changelog
    1 Reply Last reply
    0
    • girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #24

      [1.6.4]

      • Fix warnings
      • Fix redis configuration
      1 Reply Last reply
      0
      • girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #25

        Superset has some strange versioning going on. We opened https://github.com/apache/superset/discussions/30191

        1 Reply Last reply
        0
        • Package UpdatesP Offline
          Package UpdatesP Offline
          Package Updates
          App Dev
          wrote on last edited by
          #26

          [1.7.0]

          • Update apache-superset to 4.1.0
          • Full Changelog
          1 Reply Last reply
          0
          • Package UpdatesP Offline
            Package UpdatesP Offline
            Package Updates
            App Dev
            wrote on last edited by
            #27

            [1.7.1]

            • Update apache-superset to 4.1.1
            • Full Changelog
            1 Reply Last reply
            0
            • Package UpdatesP Offline
              Package UpdatesP Offline
              Package Updates
              App Dev
              wrote on last edited by
              #28

              [1.7.2]

              • Fix Snowflake Connector
              1 Reply Last reply
              0
              • Package UpdatesP Offline
                Package UpdatesP Offline
                Package Updates
                App Dev
                wrote on last edited by
                #29

                [1.8.0]

                • set HOME
                1 Reply Last reply
                0
                • Package UpdatesP Offline
                  Package UpdatesP Offline
                  Package Updates
                  App Dev
                  wrote on last edited by
                  #30

                  [1.8.1]

                  • Update apache-superset to 4.1.2
                  • Full Changelog
                  1 Reply Last reply
                  0
                  • Package UpdatesP Offline
                    Package UpdatesP Offline
                    Package Updates
                    App Dev
                    wrote on last edited by
                    #31

                    [1.9.0]

                    • Update base image to 5.0.0
                    1 Reply Last reply
                    0
                    • Package UpdatesP Offline
                      Package UpdatesP Offline
                      Package Updates
                      App Dev
                      wrote last edited by
                      #32

                      [1.10.0]

                      • Update superset to v5
                      • Full changelog
                      • 31976 Removed the DISABLE_LEGACY_DATASOURCE_EDITOR feature flag. The previous value of the feature flag was True and now the feature is permanently removed.
                      • 31959 Removes CSV_UPLOAD_MAX_SIZE config, use your web server to control file upload size.
                      • 31959 Removes the following endpoints from data uploads: /api/v1/database/<id>/<file type>_upload and /api/v1/database/<file type>_metadata, in favour of new one (Details on the PR). And simplifies permissions.
                      • 31844 The ALERT_REPORTS_EXECUTE_AS and THUMBNAILS_EXECUTE_AS config parameters have been renamed to ALERT_REPORTS_EXECUTORS and THUMBNAILS_EXECUTORS respectively. A new config flag CACHE_WARMUP_EXECUTORS has also been introduced to be able to control which user is used to execute cache warmup tasks. Finally, the config flag THUMBNAILS_SELENIUM_USER has been removed. To use a fixed executor for async tasks, use the new FixedExecutor class. See the config and docs for more info on setting up different executor profiles.
                      • 31894 Domain sharding is deprecated in favor of HTTP2. The SUPERSET_WEBSERVER_DOMAINS configuration will be removed in the next major version (6.0)
                      • 31794 Removed the previously deprecated DASHBOARD_CROSS_FILTERS feature flag
                      • 31774: Fixes the spelling of the USE-ANALAGOUS-COLORS feature flag. Please update any scripts/configuration item to use the new/corrected USE-ANALOGOUS-COLORS flag spelling.
                      • 31582 Removed the legacy Area, Bar, Event Flow, Heatmap, Histogram, Line, Sankey, and Sankey Loop charts. They were all automatically migrated to their ECharts counterparts with the exception of the Event Flow and Sankey Loop charts which were removed as they were not actively maintained and not widely used. If you were using the Event Flow or Sankey Loop charts, you will need to find an alternative solution.
                      • 31198 Disallows by default the use of the following ClickHouse functions: "version", "currentDatabase", "hostName".
                      • 29798 Since 3.1.0, the intial schedule for an alert or report was mistakenly offset by the specified timezone's relation to UTC. The initial schedule should now begin at the correct time.
                      1 Reply Last reply
                      0
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Bookmarks
                      • Search