diff --git a/CHANGELOG.md b/CHANGELOG.md
index d25d3fff4f..b2c2daab18 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -25,7 +25,7 @@ This project adheres to [Semantic Versioning](http://semver.org/).
     - `rgb()`/`rgba()` strings with decimal 0–1 fractions are no longer supported
     - `hsv()` color strings are no longer supported
     - Strings with invalid syntax such as `hsl(120, 50% 50%)` are no longer supported
-    - New supported formats: `'#ff0000aa'`, `'#f00a'`, `'rgb(255 0 0)'`, `'rgba(255 0 0 / 0.5)'`, `'hsl(0 100% 50% / 0.5)'`, `'hsla(0, 100%, 50%, 0.5)'`, `'hwb(0, 0%, 0%)'`, `lab()`, `lch()`, `oklab()`, `oklch()`, `color()`, `hsl(0.5turn 60% 40%)`, `hsl(none 60% 40%)`
+    - New supported formats: `'#ff0000aa'`, `'#f00a'`, `'rgb(255 0 0)'`, `'rgba(255 0 0 / 0.5)'`, `'hsl(0 100% 50% / 0.5)'`, `'hsla(0, 100%, 50%, 0.5)'`, `'hwb(0 0% 0%)'`, `lab()`, `lch()`, `oklab()`, `oklch()`, `color()`, `hsl(0.5turn 60% 40%)`, `hsl(none 60% 40%)`
   - Replace `country-regex` with `country-iso-search` to search for country names in choropleth, scattergeo traces [[#7856](https://github.com/plotly/plotly.js/pull/7856)]. Most country names are handled exactly the same; a small number of legacy entries have been removed.
   - Change `layout.geo.fitbounds` default from `false` to `'locations'` [[#7895](https://github.com/plotly/plotly.js/pull/7895)]. `geo` subplots will now auto-fit the initial view to the trace data by default.
   - Dynamically compute `center` and `zoom` values for `scattermap` and `densitymap` traces. The initial map view will now auto-fit to the trace data by default. Add `layout.map.fitbounds` attribute (default `'locations'`) to enable or disable auto-fitting behavior [[#7884](https://github.com/plotly/plotly.js/pull/7884), [#7913](https://github.com/plotly/plotly.js/pull/7913)]
diff --git a/doc/apidoc/conf.py b/doc/apidoc/conf.py
index 05d3e097b9..9edfc8cef1 100644
--- a/doc/apidoc/conf.py
+++ b/doc/apidoc/conf.py
@@ -24,7 +24,7 @@
 # The short X.Y version
 version = ""
 # The full version, including alpha/beta/rc tags
-release = "6.6.0"
+release = "7.0.0"
 
 
 # -- General configuration ---------------------------------------------------
diff --git a/doc/python/LaTeX.md b/doc/python/LaTeX.md
index 744ff3f2ae..8a47c44663 100644
--- a/doc/python/LaTeX.md
+++ b/doc/python/LaTeX.md
@@ -35,7 +35,7 @@ jupyter:
 
 #### LaTeX Typesetting
 
-Figure titles, axis labels and annotations all accept LaTeX directives for rendering mathematical formulas and notation, when the entire label is surrounded by dollar signs `$...$`. This rendering is handled by the [MathJax library](https://www.npmjs.com/package/mathjax?activeTab=versions), which must be loaded in the environment where figures are being rendered. MathJax is included by default in Jupyter-like environments. When embedding Plotly figures in other contexts it may be required to ensure that MathJax is separately loaded, for example via a `<script>` tag pointing to a content-delivery network (CDN). Versions 2 and 3 are supported.
+Figure titles, axis labels and annotations all accept LaTeX directives for rendering mathematical formulas and notation, when the entire label is surrounded by dollar signs `$...$`. This rendering is handled by the [MathJax library](https://www.npmjs.com/package/mathjax?activeTab=versions), which must be loaded in the environment where figures are being rendered. MathJax is included by default in Jupyter-like environments. When embedding Plotly figures in other contexts it may be required to ensure that MathJax is separately loaded, for example via a `<script>` tag pointing to a content-delivery network (CDN). Plotly.py v7 and above supports MathJax versions 3 and 4. Earlier Plotly.py versions support MathJax versions 2 and 3.
 
 ```python
 import plotly.express as px
diff --git a/doc/python/axes.md b/doc/python/axes.md
index 39c73ee4f5..9d5f154e10 100644
--- a/doc/python/axes.md
+++ b/doc/python/axes.md
@@ -28,7 +28,7 @@ jupyter:
     language: python
     layout: base
     name: Axes
-    order: 14
+    order: 15
     permalink: python/axes/
     thumbnail: thumbnail/axes.png
 ---
diff --git a/doc/python/builtin-colorscales.md b/doc/python/builtin-colorscales.md
index 280671f3fe..01fc9ec8e1 100644
--- a/doc/python/builtin-colorscales.md
+++ b/doc/python/builtin-colorscales.md
@@ -30,7 +30,7 @@ jupyter:
     language: python
     layout: base
     name: Built-in Continuous Color Scales
-    order: 28
+    order: 29
     permalink: python/builtin-colorscales/
     thumbnail: thumbnail/heatmap_colorscale.jpg
     v4upgrade: true
diff --git a/doc/python/colorscales.md b/doc/python/colorscales.md
index 016ded1125..aadef07600 100644
--- a/doc/python/colorscales.md
+++ b/doc/python/colorscales.md
@@ -30,7 +30,7 @@ jupyter:
     language: python
     layout: base
     name: Continuous Color Scales and Color Bars
-    order: 21
+    order: 22
     permalink: python/colorscales/
     redirect_from: python/logarithmic-color-scale/
     thumbnail: thumbnail/heatmap_colorscale.jpg
diff --git a/doc/python/configuration-options.md b/doc/python/configuration-options.md
index 537e247911..92986aa636 100644
--- a/doc/python/configuration-options.md
+++ b/doc/python/configuration-options.md
@@ -28,7 +28,7 @@ jupyter:
     language: python
     layout: base
     name: Configuration
-    order: 10
+    order: 11
     page_type: u-guide
     permalink: python/configuration-options/
     thumbnail: thumbnail/modebar-icons.png
@@ -209,10 +209,14 @@ To delete buttons from the modebar, pass an array of strings containing the name
   - **High-level**: `zoom`, `pan`, `select`, `zoomIn`, `zoomOut`, `autoScale`, `resetScale`
   - **2D**: `zoom2d`, `pan2d`, `select2d`, `lasso2d`, `zoomIn2d`, `zoomOut2d`, `autoScale2d`, `resetScale2d`, `v1hovermode`
   - **2D Shape Drawing**: `drawline`, `drawopenpath`, `drawclosedpath`, `drawcircle`, `drawrect`, `eraseshape`
-  - **3D**: `zoom3d`, `pan3d`, `orbitRotation`, `tableRotation`, `handleDrag3d`, `resetCameraDefault3d`, `resetCameraLastSave3d`, `hoverClosest3d`
+  - **3D**: `zoom3d`, `pan3d`, `orbitRotation`, `tableRotation`, `resetCameraDefault3d`, `resetCameraLastSave3d`, `hoverClosest3d`
   - **Cartesian**: `hoverClosestCartesian`, `hoverCompareCartesian`
   - **Geo**: `zoomInGeo`, `zoomOutGeo`, `resetGeo`, `hoverClosestGeo`
-  - **Other**: `hoverClosestGl2d`, `hoverClosestPie`, `toggleHover`, `resetViews`, `toImage`, `sendDataToCloud`, `toggleSpikelines`, `resetViewMap`
+  - **Tile maps**: `zoomInMap`, `zoomOutMap`, `resetViewMap`
+  - **Sankey**: `resetSankeyGroup`
+  - **Other**: `hoverClosestPie`, `toggleHover`, `resetViews`, `toImage`, `sendChartToCloud`, `toggleSpikelines`
+
+*Changed in 7.0*: `handleDrag3d` and `hoverClosestGl2d` no longer exist, and `sendDataToCloud` is now named `sendChartToCloud`.
 
 ```python
 import plotly.graph_objects as go
diff --git a/doc/python/discrete-color.md b/doc/python/discrete-color.md
index 0535d16d14..fd4de49201 100644
--- a/doc/python/discrete-color.md
+++ b/doc/python/discrete-color.md
@@ -30,7 +30,7 @@ jupyter:
     language: python
     layout: base
     name: Discrete Colors
-    order: 29
+    order: 30
     permalink: python/discrete-color/
     thumbnail: thumbnail/heatmap_colorscale.jpg
     v4upgrade: true
diff --git a/doc/python/figure-factories.md b/doc/python/figure-factories.md
index b03086b632..199d6ac98f 100644
--- a/doc/python/figure-factories.md
+++ b/doc/python/figure-factories.md
@@ -28,7 +28,7 @@ jupyter:
     language: python
     layout: base
     name: Figure Factories
-    order: 33
+    order: 34
     permalink: python/figure-factories/
     thumbnail: thumbnail/streamline.jpg
 ---
@@ -41,7 +41,7 @@ The following plot types can be created with Figure Factory:
 
   * [Dendrograms](/python/dendrogram/)
   * [Hexagonal Binning Tile Map](/python/hexbin-map/)
-  * [Quiver Plots](/python/quiver-plots/)
+  * [Quiver Plots](/python/quiver-plots/) — since version 7.0, quiver plots are better made with the `go.Quiver` trace type. `create_quiver` remains available for its `angle` and `scaleratio` options.
   * [Streamline Plots](/python/streamline-plots/)
   * [Tables](/python/figure-factory-table/)
   * [Ternary Contour Plots](/python/ternary-contour/)
@@ -65,4 +65,3 @@ The following legacy Figure Factory functions have been replaced by Plotly Expre
 #### Reference
 
 For more information about the contents of `plotly.figure_factory`, please refer to our [API Reference documentation](https://plotly.com/python-api-reference/plotly.figure_factory.html).
-
diff --git a/doc/python/figure-introspection.md b/doc/python/figure-introspection.md
index 3e85bc85f2..b007fa2e8a 100644
--- a/doc/python/figure-introspection.md
+++ b/doc/python/figure-introspection.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Introspecting Figures
-    order: 36
+    order: 37
     page_type: u-guide
     permalink: python/figure-introspection/
     thumbnail: thumbnail/violin.jpg
diff --git a/doc/python/figure-labels.md b/doc/python/figure-labels.md
index 5cd49cb91d..1374188910 100644
--- a/doc/python/figure-labels.md
+++ b/doc/python/figure-labels.md
@@ -28,7 +28,7 @@ jupyter:
     language: python
     layout: base
     name: Setting the Font, Title, Legend Entries, and Axis Titles
-    order: 13
+    order: 14
     permalink: python/figure-labels/
     redirect_from: python/font/
     thumbnail: thumbnail/figure-labels.png
diff --git a/doc/python/graph-objects.md b/doc/python/graph-objects.md
index 878b36d6bf..92f34fdfb8 100644
--- a/doc/python/graph-objects.md
+++ b/doc/python/graph-objects.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Graph Objects
-    order: 35
+    order: 36
     page_type: u-guide
     permalink: python/graph-objects/
     thumbnail: thumbnail/horizontal-bar.jpg
diff --git a/doc/python/graphing-multiple-chart-types.md b/doc/python/graphing-multiple-chart-types.md
index 371776a561..a1f7fca1c7 100644
--- a/doc/python/graphing-multiple-chart-types.md
+++ b/doc/python/graphing-multiple-chart-types.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Multiple Chart Types
-    order: 18
+    order: 19
     page_type: u-guide
     permalink: python/graphing-multiple-chart-types/
     thumbnail: thumbnail/multiple-chart-type.jpg
diff --git a/doc/python/horizontal-vertical-shapes.md b/doc/python/horizontal-vertical-shapes.md
index 67417f2e46..d533904aac 100644
--- a/doc/python/horizontal-vertical-shapes.md
+++ b/doc/python/horizontal-vertical-shapes.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Horizontal and Vertical Lines and Rectangles
-    order: 37
+    order: 38
     permalink: python/horizontal-vertical-shapes/
     thumbnail: thumbnail/shape.jpg
 ---
diff --git a/doc/python/hover-text-and-formatting.md b/doc/python/hover-text-and-formatting.md
index c81f1f06f0..ccfefc85a7 100644
--- a/doc/python/hover-text-and-formatting.md
+++ b/doc/python/hover-text-and-formatting.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Hover Text and Formatting
-    order: 23
+    order: 24
     permalink: python/hover-text-and-formatting/
     thumbnail: thumbnail/hover-text.png
 ---
diff --git a/doc/python/images.md b/doc/python/images.md
index d69aa91c88..898a65898a 100644
--- a/doc/python/images.md
+++ b/doc/python/images.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Images
-    order: 24
+    order: 25
     permalink: python/images/
     thumbnail: thumbnail/images.png
     v4upgrade: true
diff --git a/doc/python/interactive-html-export.md b/doc/python/interactive-html-export.md
index dc5384f0bc..49871e5cb4 100644
--- a/doc/python/interactive-html-export.md
+++ b/doc/python/interactive-html-export.md
@@ -28,7 +28,7 @@ jupyter:
     language: python
     layout: base
     name: Interactive HTML Export
-    order: 31
+    order: 32
     page_type: u-guide
     permalink: python/interactive-html-export/
     thumbnail: thumbnail/static-image-export.png
diff --git a/doc/python/ipython-vs-python.md b/doc/python/ipython-vs-python.md
index 7ec3bb5b8e..3e630b8201 100644
--- a/doc/python/ipython-vs-python.md
+++ b/doc/python/ipython-vs-python.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: IPython vs Python
-    order: 26
+    order: 27
     permalink: python/ipython-vs-python/
     thumbnail: thumbnail/venn.jpg
 ---
diff --git a/doc/python/legend.md b/doc/python/legend.md
index 3f4f8fbd1b..6e883934f1 100644
--- a/doc/python/legend.md
+++ b/doc/python/legend.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Legends
-    order: 15
+    order: 16
     permalink: python/legend/
     redirect_from: python/horizontal-legend/
     thumbnail: thumbnail/legends.gif
diff --git a/doc/python/location-mode.md b/doc/python/location-mode.md
index 32d6ff26cd..7b041ee68d 100644
--- a/doc/python/location-mode.md
+++ b/doc/python/location-mode.md
@@ -461,17 +461,7 @@ fig = px.choropleth(
 fig.show()
 ```
 
-> How Plotly matches 'country names' will change in a future version. Matching will become stricter and some country names may no longer match. We recommend using `locationmode='ISO-3'` with ISO codes for `locations` to ensure consistent behavior across versions.
-
-```python
-import plotly.express as px
-
-fig = px.choropleth(
-    locations=['USA', 'CAN', 'GBR'],
-    locationmode='ISO-3'
-)
-fig.show()
-```
+*Changed in 7.0*: country names are matched by a different library, which accepts more forms and rejects some names that matched by accident before. See [Changes in Version 7](/python/v7-migration/#Country-Names) for details. To get identical results across versions, use [`locationmode='ISO-3'`](#locationmode='ISO-3') with ISO codes for `locations`.
 
 ## Using Different Data Types with `locations`
 
diff --git a/doc/python/map-configuration.md b/doc/python/map-configuration.md
index 353ea3d4ac..da5929cdd1 100644
--- a/doc/python/map-configuration.md
+++ b/doc/python/map-configuration.md
@@ -171,7 +171,9 @@ fig.show()
 
 ### Automatic Zooming or Bounds Fitting
 
-The `layout.geo.fitbounds` attribute can be set to `locations` to automatically set the center and latitude and longitude range according to the data being plotted. See the [choropleth maps](/python/choropleth-maps/) documentation for more information.
+The `layout.geo.fitbounds` attribute set to `locations` automatically sets the center and the latitude and longitude range according to the data being plotted. See the [choropleth maps](/python/choropleth-maps/) documentation for more information.
+
+*Changed in 7.0*: `fitbounds` defaults to `"locations"`, so a `geo` subplot fits its data without any configuration. Set `fitbounds=False` for the world view that earlier versions showed by default. Setting your own `center` or `projection.scale` also turns auto-fitting off.
 
 ```python
 import plotly.express as px
@@ -182,6 +184,21 @@ fig.update_layout(height=300, margin={"r":0,"t":0,"l":0,"b":0})
 fig.show()
 ```
 
+### Limiting the Zoom Range
+
+*New in 7.0*
+
+`projection.minscale` and `projection.maxscale` clamp how far a user can zoom the map in or out. The two attributes are multipliers of `projection.scale`, so `minscale=0.5` allows zooming out to half the initial view and `maxscale=4` allows zooming in to four times it.
+
+```python
+import plotly.express as px
+
+fig = px.line_geo(lat=[0,15,20,35], lon=[5,10,25,30])
+fig.update_geos(projection=dict(scale=1, minscale=0.5, maxscale=4))
+fig.update_layout(height=300, margin={"r":0,"t":0,"l":0,"b":0})
+fig.show()
+```
+
 ### Named Map Scopes and Country Sub-Units
 
 In addition, the named "scope" of a map defines a sub-set of the earth's surface to draw. Each scope has a _default projection type, center and roll, as well as bounds_, and certain scopes contain country sub-unit cultural layers certain resolutions, such as `scope="north america"` at `resolution=50` which contains US state and Canadian province boundaries.
diff --git a/doc/python/marker-style.md b/doc/python/marker-style.md
index b719b94471..6a75ccbd48 100644
--- a/doc/python/marker-style.md
+++ b/doc/python/marker-style.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Styling Markers
-    order: 20
+    order: 21
     permalink: python/marker-style/
     thumbnail: thumbnail/marker-style.gif
 ---
diff --git a/doc/python/migrate-to-maplibre.md b/doc/python/migrate-to-maplibre.md
index 4466165e50..3df744dcbb 100644
--- a/doc/python/migrate-to-maplibre.md
+++ b/doc/python/migrate-to-maplibre.md
@@ -36,7 +36,7 @@ jupyter:
 
 ## Migrating from Mapbox traces to MapLibre traces
 
-With the release of Plotly.py v5.24.0, we are introducing a new set of trace types for maps with tile underlays, including from Plotly Express:
+Plotly.py v5.24.0 introduced a set of trace types for maps with tile underlays, including from Plotly Express:
 - `px.scatter_map`
 - `px.line_map`
 - `px.choropleth_map`
@@ -47,7 +47,9 @@ as well as Plotly Graph Objects:
 - `go.Scattermap`
 - `go.Densitymap`
 
-These traces replace the existing Mapbox traces, `px.scatter_mapbox`, `px.line_mapbox`, etc., but use [MapLibre](https://maplibre.org) as the map renderer rather than Mapbox.
+These traces replaced the Mapbox traces, `px.scatter_mapbox`, `px.line_mapbox`, and the rest, and use [MapLibre](https://maplibre.org) as the map renderer rather than Mapbox.
+
+**The Mapbox traces, the `layout.mapbox` subplot, and the `mapboxAccessToken` configuration option were removed in Plotly.py 7.** If you are upgrading to version 7, follow the steps below, then see [Changes in Version 7](/python/v7-migration/) for the rest of the upgrade.
 
 When switching to the new traces, keep an eye out for improved rendering performance, WebGL2 support, and over time, improved features in the Plotly map traces inherited from the MapLibre renderer, including projection support, globe views, terrain support, and support for modern mapping standards.
 
diff --git a/doc/python/multiple-axes.md b/doc/python/multiple-axes.md
index e792797c2d..96e2f19b16 100644
--- a/doc/python/multiple-axes.md
+++ b/doc/python/multiple-axes.md
@@ -28,7 +28,7 @@ jupyter:
     language: python
     layout: base
     name: Multiple Axes
-    order: 16
+    order: 17
     permalink: python/multiple-axes/
     thumbnail: thumbnail/multiple-axes.jpg
 ---
@@ -383,7 +383,9 @@ fig.show()
 
 *New in 5.13*
 
-With overlayed axes, each axis by default has its own number of ticks. You can sync the number of ticks on a cartesian axis with another one it overlays by setting `tickmode="sync"`. In this example, we sync the ticks on the `"Total bill amount"` axis with the `"Total number of diners"` axis that it overlays.
+Set `tickmode="sync"` on an overlaying cartesian axis to draw its ticks and gridlines at the positions of the axis it overlays, labeled from its own range. The two axes then share one grid. In this example, the `"Total bill amount"` axis syncs its ticks with the `"Total number of diners"` axis that it overlays.
+
+*Changed in 7.0*: `tickmode` defaults to `"sync"` on an overlaying axis. Earlier versions gave each axis its own independent grid. Set `tickmode="auto"` on the overlaying axis for that behavior.
 
 ```python
 import plotly.graph_objects as go
diff --git a/doc/python/orca-management.md b/doc/python/orca-management.md
index 0d96fadb9a..a87a5df52a 100644
--- a/doc/python/orca-management.md
+++ b/doc/python/orca-management.md
@@ -28,7 +28,7 @@ jupyter:
     language: python
     layout: base
     name: Orca Management
-    order: 9
+    order: 10
     permalink: python/orca-management/
     thumbnail: thumbnail/orca-management.png
 ---
diff --git a/doc/python/pandas-backend.md b/doc/python/pandas-backend.md
index 2ee2876285..e3ce5e28a7 100644
--- a/doc/python/pandas-backend.md
+++ b/doc/python/pandas-backend.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Pandas Plotting Backend
-    order: 32
+    order: 33
     permalink: python/pandas-backend/
     redirect_from: python/cufflinks/
     thumbnail: thumbnail/plotly-express.png
diff --git a/doc/python/performance.md b/doc/python/performance.md
index 0d413935bb..842b21dd76 100644
--- a/doc/python/performance.md
+++ b/doc/python/performance.md
@@ -140,7 +140,7 @@ Each `plotly` trace type is rendered with either SVG or WebGL. The following tra
 WebGL is a powerful technology for accelerating rendering but comes with some strict limitations:
 
 1. GPU requirement: WebGL is a GPU (graphics card) technology and therefore requires specific hardware which is available in most but not all cases and is supported by most but not all browsers.
-2. Rasterization: WebGL-rendered data is drawn as a grid of pixels rather than as individual shapes, so can appear pixelated or fuzz in certain cases, and when exported to static file formats will appear pixelated on zoom. In addition, text rendering will differ between SVG and WebGL-powered traces.
+2. Rasterization: WebGL-rendered data is drawn as a grid of pixels rather than as individual shapes, so can appear pixelated or fuzzy in certain cases. This also applies to static export: when a figure with WebGL traces is exported to a *vector* format such as SVG or PDF, the WebGL traces are embedded as an encapsulated raster (a bitmap) rather than as true vectors, so those parts will appear pixelated on zoom. To force fully-vector output, use `render_mode="svg"` to supported Plotly Express functions (see [WebGL with Plotly Express](#webgl-with-plotly-express) below). In addition, text rendering will differ between SVG and WebGL-powered traces.
 3. Context limits: browsers impose a strict limit on the number of WebGL "contexts" that any given web document can access. WebGL-powered traces in `plotly` can use multiple contexts in some cases but as a general rule, **it may not be possible to render more than 8 WebGL-involving figures on the same page at the same time.** See the following section, Multiple WebGL Contexts, for more details.
 4. Size limits: browsers impose hardware-dependent limits on the height and width of figures using WebGL which users may encounter with extremely large plots (e.g. tens of thousands of pixels of height).
 
@@ -181,7 +181,7 @@ it is also possible to use [datashader](/python/datashader/).
 
 The `render_mode` argument to supported Plotly Express functions (e.g. `scatter` and `scatter_polar`) can be used to enable WebGL rendering.
 
-> **Note** The default `render_mode` is `"auto"`, in which case Plotly Express will automatically set `render_mode="webgl"` if the input data is more than 1,000 rows long. In this case, WebGL can be disabled by setting `render_mode=svg`.
+> **Note** The default `render_mode` is `"auto"`, in which case Plotly Express will automatically set `render_mode="webgl"` if the input data is more than 1,000 rows long. In this case, WebGL can be disabled by setting `render_mode="svg"`. Because WebGL traces are embedded as rasters rather than vectors when [exported to a static vector format](/python/static-image-export/) such as SVG or PDF, set `render_mode="svg"` if you need fully-vector output from a large scatter figure.
 
 Here is an example that creates a 100,000 point scatter plot using Plotly Express with WebGL rendering explicitly enabled.
 
diff --git a/doc/python/px-arguments.md b/doc/python/px-arguments.md
index 308a8d02bd..d0346292e5 100644
--- a/doc/python/px-arguments.md
+++ b/doc/python/px-arguments.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Plotly Express Arguments
-    order: 19
+    order: 20
     page_type: u-guide
     permalink: python/px-arguments/
     thumbnail: thumbnail/plotly-express.png
diff --git a/doc/python/quiver-plots.md b/doc/python/quiver-plots.md
index 530c305e47..956eb8c56f 100644
--- a/doc/python/quiver-plots.md
+++ b/doc/python/quiver-plots.md
@@ -22,8 +22,8 @@ jupyter:
     pygments_lexer: ipython3
     version: 3.7.3
   plotly:
-    description: How to make a quiver plot in Python. A quiver plot displays velocity
-      vectors a arrows.
+    description: How to make a quiver plot in Python. A quiver plot displays a 2D vector
+      field as an array of arrows.
     display_as: scientific
     language: python
     layout: base
@@ -33,56 +33,185 @@ jupyter:
     thumbnail: thumbnail/quiver-plot.jpg
 ---
 
-Quiver plots can be made using a [figure factory](/python/figure-factories/) as detailed in this page.
+A quiver plot displays a 2D vector field as an array of arrows. Since version 7.0, Plotly has a `Quiver` trace type, which is the recommended way to make quiver plots. Earlier versions relied on the `create_quiver` [figure factory](/python/figure-factories/), which is still available and is described at the end of this page.
+
+A `Quiver` trace takes four arrays of the same length: `x` and `y` give the position of each arrow, and `u` and `v` give the vector components at that position. Arrow direction and length come from `(u, v)`.
 
 #### Basic Quiver Plot
 
 ```python
-import plotly.figure_factory as ff
+import plotly.graph_objects as go
+import numpy as np
+
+x, y = np.meshgrid(np.arange(0, 2, .2), np.arange(0, 2, .2))
+u = np.cos(x) * y
+v = np.sin(x) * y
+
+fig = go.Figure(go.Quiver(x=x.flatten(), y=y.flatten(),
+                          u=u.flatten(), v=v.flatten()))
+
+fig.show()
+```
 
+#### Arrow Anchor and Length
+
+`anchor` sets which part of the arrow sits at its `(x, y)` position: `"tail"` (the default), `"tip"`, or `"center"`.
+
+Arrow length is controlled by `lengthmode` and `lengthfactor`. With `lengthmode="scaled"` (the default), lengths are normalized against the longest vector in the field and the density of points, so a dense grid stays readable whatever the underlying values are. `lengthmode="raw"` draws each arrow at its specified magnitude determined by `u` and `v`. `lengthfactor` is a multiplier applied on top: values below 1 shorten every arrow, above 1 lengthen them.
+
+```python
+import plotly.graph_objects as go
 import numpy as np
 
-x,y = np.meshgrid(np.arange(0, 2, .2), np.arange(0, 2, .2))
-u = np.cos(x)*y
-v = np.sin(x)*y
+x, y = np.meshgrid(np.arange(-2, 3), np.arange(-2, 3))
+u, v = -y, x  # rotational field
 
-fig = ff.create_quiver(x, y, u, v)
+fig = go.Figure(go.Quiver(x=x.flatten(), y=y.flatten(),
+                          u=u.flatten(), v=v.flatten(),
+                          anchor="center", lengthfactor=0.8))
+
+fig.update_layout(title_text="Rotational field, arrows centered on each point",
+                  yaxis_scaleanchor="x")
 fig.show()
 ```
 
-#### Quiver Plot with Points
+#### Setting Arrow Reference
+
+The `arrowref` property controls how the `u` and `v` vector components are interpreted, and how the vector arrows respond to zooming along a single axis.
+
+By default, `arrowref="data"`, meaning that `u` and `v` are interpreted as data values. This means that the angle of the vectors depends on the relative scale of the two axes, and the apparent angle will change when zooming along one axis. This is the appropriate behavior when `u` and `v` represent data-space values, such as when illustrating a magnetic field.
+
+To instead interpret `u` and `v` in pixel values, set `arrowref="paper"`, which will always draw vectors at the same angle regardless of the axis scales. This is the correct behavior when the vectors correspond to abstract values which are not linked to the data space.
+
+Note that `arrowref="paper"` always scales arrow lengths, so `lengthmode="raw"` is ignored when you set it.
+
+The difference is clearest on axes with different scales. Both panels below plot the same vectors, `u=1` and `v=0.1`, on a grid where x spans 10 units and y spans 1.
 
 ```python
-import plotly.figure_factory as ff
 import plotly.graph_objects as go
+from plotly.subplots import make_subplots
+import numpy as np
+
+x = np.linspace(0, 10, 6)
+y = np.full_like(x, 0.5)
+u = np.ones_like(x)
+v = np.full_like(x, 0.1)
 
+fig = make_subplots(rows=1, cols=2,
+                    subplot_titles=['arrowref="data"', 'arrowref="paper"'])
+fig.add_trace(go.Quiver(x=x, y=y, u=u, v=v, arrowref="data"), row=1, col=1)
+fig.add_trace(go.Quiver(x=x, y=y, u=u, v=v, arrowref="paper"), row=1, col=2)
+
+fig.update_xaxes(range=[-1, 11])
+fig.update_yaxes(range=[0, 1])
+fig.update_layout(showlegend=False)
+fig.show()
+```
+
+With `"data"`, `v=0.1` covers a tenth of the y-axis while `u=1` covers a tenth of the x-axis, so the arrows tilt noticeably. With `"paper"`, the same components are 1 pixel across and 0.1 pixels up, so the arrows stay nearly flat whatever the axis ranges are.
+
+#### Coloring Arrows by a Scalar Field
+
+Pass `marker.color` an array with one value per arrow, together with the usual colorscale attributes, to color each arrow by that value. If you enable a colorscale without supplying a `marker.color` array, arrows are colored by their vector magnitude. A single (non-array) `marker.color` paints the whole field one color.
+
+```python
+import plotly.graph_objects as go
 import numpy as np
 
-x,y = np.meshgrid(np.arange(-2, 2, .2),
-                  np.arange(-2, 2, .25))
-z = x*np.exp(-x**2 - y**2)
+x, y = np.meshgrid(np.arange(-2, 2, .2), np.arange(-2, 2, .25))
+z = x * np.exp(-x**2 - y**2)
 v, u = np.gradient(z, .2, .2)
+speed = np.sqrt(u**2 + v**2)
 
-# Create quiver figure
-fig = ff.create_quiver(x, y, u, v,
-                       scale=.25,
-                       arrow_scale=.4,
-                       name='quiver',
-                       line_width=1)
+fig = go.Figure(go.Quiver(x=x.flatten(), y=y.flatten(),
+                          u=u.flatten(), v=v.flatten(),
+                          marker=dict(color=speed.flatten(),
+                                      colorscale="Viridis",
+                                      showscale=True,
+                                      colorbar_title_text="speed")))
 
-# Add points to figure
-fig.add_trace(go.Scatter(x=[-.7, .75], y=[0,0],
-                    mode='markers',
-                    marker_size=12,
-                    name='points'))
+fig.show()
+```
+
+#### Styling Arrows
+
+`marker.line.width` and `marker.line.dash` style the arrow shafts, and `marker.arrowsize` scales the arrowhead relative to the shaft width — the default of `1` draws a head about three times as wide as the shaft.
+
+```python
+import plotly.graph_objects as go
+import numpy as np
+
+x, y = np.meshgrid(np.arange(0, 6), np.arange(0, 6))
+u_model = np.ones_like(x, dtype=float)
+v_model = 0.15 * (y - 2.5)
+u_measured = 0.9 * u_model
+v_measured = v_model + 0.25 * np.cos(x)
+
+fig = go.Figure([
+    go.Quiver(x=x.flatten(), y=y.flatten(),
+              u=u_model.flatten(), v=v_model.flatten(),
+              name="model",
+              marker=dict(color="#7f7f7f", arrowsize=0.8,
+                          line=dict(width=2, dash="dot"))),
+    go.Quiver(x=x.flatten(), y=y.flatten(),
+              u=u_measured.flatten(), v=v_measured.flatten(),
+              name="measured",
+              marker=dict(color="#d62728", arrowsize=1.2,
+                          line=dict(width=3))),
+])
+
+fig.update_layout(title_text="Modelled and measured fields", showlegend=True)
+fig.show()
+```
+
+#### Quiver Plot with Points
+
+A `Quiver` trace is a cartesian trace, so it can be combined with other cartesian traces in the same figure.
+
+```python
+import plotly.graph_objects as go
+import numpy as np
+
+x, y = np.meshgrid(np.arange(-2, 2, .2), np.arange(-2, 2, .25))
+z = x * np.exp(-x**2 - y**2)
+v, u = np.gradient(z, .2, .2)
+
+fig = go.Figure(go.Quiver(x=x.flatten(), y=y.flatten(),
+                          u=u.flatten(), v=v.flatten(),
+                          name="quiver",
+                          marker=dict(line_width=1)))
+
+fig.add_trace(go.Scatter(x=[-.7, .75], y=[0, 0],
+                         mode="markers",
+                         marker_size=12,
+                         name="points"))
 
 fig.show()
 ```
 
+#### Quiver Plots with Figure Factory
+
+`create_quiver` builds a quiver plot out of `Scatter` traces rather than using the `Quiver` trace type. It remains available, and offers two options the trace type does not: `angle` sets the arrowhead angle in radians, and `scaleratio` fixes the ratio between the y-axis and x-axis scales.
+
+```python
+import plotly.figure_factory as ff
+import numpy as np
+
+x, y = np.meshgrid(np.arange(0, 2, .2), np.arange(0, 2, .2))
+u = np.cos(x) * y
+v = np.sin(x) * y
+
+fig = ff.create_quiver(x, y, u, v)
+
+fig.show()
+```
+
+Because the result is made of `Scatter` traces, the arrows cannot be colored individually by a scalar field, and the trace-level attributes described above (`anchor`, `lengthmode`, `marker.arrowsize`) do not apply.
+
 #### See also
 
 [Cone plot](/python/cone-plot) for the 3D equivalent of quiver plots.
 
 #### Reference
 
-For more info on `ff.create_quiver()`, see the [full function reference](https://plotly.com/python-api-reference/generated/plotly.figure_factory.create_quiver.html)
\ No newline at end of file
+See the [Quiver trace reference](https://plotly.com/python/reference/quiver/) for the full list of attributes, or the [`create_quiver` function reference](https://plotly.com/python-api-reference/generated/plotly.figure_factory.create_quiver.html) for the figure factory.
diff --git a/doc/python/sankey-diagram.md b/doc/python/sankey-diagram.md
index 7531c332ae..f35e17932f 100644
--- a/doc/python/sankey-diagram.md
+++ b/doc/python/sankey-diagram.md
@@ -318,6 +318,49 @@ fig = go.Figure(go.Sankey(
 fig.show()
 ```
 
+### Node and Link Order
+
+*New in 7.0*
+
+By default, the layout reorders nodes within a column, and links within a node, to reduce the number of crossings. Set `node.sort="input"` and `link.sort="input"` to keep the order you provide instead: nodes appear in the order given in `node.label`, and links in the order given in `link.source` and `link.target`. Use this when the order carries meaning, such as a ranking, or when you need a layout that stays the same across renders.
+
+```python
+import plotly.graph_objects as go
+
+labels = ["Gold", "Silver", "Bronze", "Q1", "Q2", "Q3"]
+
+fig = go.Figure(go.Sankey(
+    node=dict(label=labels, pad=15, thickness=20, sort="input"),
+    link=dict(
+        source=[0, 0, 0, 1, 1, 1, 2, 2, 2],
+        target=[3, 4, 5, 3, 4, 5, 3, 4, 5],
+        value=[8, 4, 2, 5, 6, 3, 2, 3, 7],
+        sort="input"
+    )
+))
+
+fig.update_layout(title_text="Medals by quarter, categories in ranked order")
+fig.show()
+```
+
+### Flow Direction
+
+*New in 7.0*
+
+`direction` sets which way flows run along the `orientation` axis. With the default `"forward"`, sources are on the left for a horizontal diagram and at the top for a vertical one. With `"reversed"`, sources are on the right or at the bottom.
+
+```python
+import plotly.graph_objects as go
+
+fig = go.Figure(go.Sankey(
+    direction="reversed",
+    node=dict(label=["A", "B", "Total"], pad=15, thickness=20),
+    link=dict(source=[0, 1], target=[2, 2], value=[8, 4])
+))
+
+fig.show()
+```
+
 ### Reference
 
 See [https://plotly.com/python/reference/sankey](https://plotly.com/python/reference/sankey/) for more information and options!
diff --git a/doc/python/selections.md b/doc/python/selections.md
index 573ba08a82..bc2c96d0d6 100644
--- a/doc/python/selections.md
+++ b/doc/python/selections.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Selections
-    order: 38
+    order: 39
     permalink: python/selections/
     thumbnail: thumbnail/ml_apps.png
 ---
diff --git a/doc/python/setting-graph-size.md b/doc/python/setting-graph-size.md
index cfdf8e1f7e..ea28db23fa 100644
--- a/doc/python/setting-graph-size.md
+++ b/doc/python/setting-graph-size.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Setting Graph Size
-    order: 11
+    order: 12
     permalink: python/setting-graph-size/
     thumbnail: thumbnail/sizing.png
 ---
diff --git a/doc/python/shapes.md b/doc/python/shapes.md
index 25ec7f65a9..78beaad9a9 100644
--- a/doc/python/shapes.md
+++ b/doc/python/shapes.md
@@ -28,7 +28,7 @@ jupyter:
     language: python
     layout: base
     name: Shapes
-    order: 25
+    order: 26
     permalink: python/shapes/
     thumbnail: thumbnail/shape.jpg
 ---
diff --git a/doc/python/splom.md b/doc/python/splom.md
index 41a1d0950f..8de2f9799c 100644
--- a/doc/python/splom.md
+++ b/doc/python/splom.md
@@ -336,6 +336,33 @@ fig.show()
 
 ```
 
+#### Linked Axes
+
+*Changed in 7.0*
+
+`dimensions[].axis.matches` links the x-axis and the y-axis generated by a dimension, so every subplot in the same row and column pans and zooms together. It now defaults to `True`. Plotly Express already set it on the figures it generated, so `px.scatter_matrix` is unaffected. Set it to `False` on a dimension to zoom that dimension's row and column independently.
+
+```python
+import plotly.graph_objects as go
+import pandas as pd
+
+df = pd.read_csv(
+    "https://raw.githubusercontent.com/plotly/datasets/master/iris-data.csv"
+)
+
+fig = go.Figure(go.Splom(
+    dimensions=[
+        dict(label="sepal length", values=df["sepal length"], axis=dict(matches=False)),
+        dict(label="sepal width", values=df["sepal width"], axis=dict(matches=False)),
+        dict(label="petal length", values=df["petal length"], axis=dict(matches=False)),
+    ],
+    marker=dict(size=4),
+))
+
+fig.update_layout(title=dict(text="Unlinked axes"), width=600, height=600)
+fig.show()
+```
+
 #### Reference
 
 See [function reference for `px.scatter_matrix()`](https://plotly.com/python-api-reference/generated/plotly.express.scatter_matrix) or https://plotly.com/python/reference/splom/ for more information and chart attribute options!
diff --git a/doc/python/static-image-export.md b/doc/python/static-image-export.md
index 3c5440e12f..045512a0f1 100644
--- a/doc/python/static-image-export.md
+++ b/doc/python/static-image-export.md
@@ -122,7 +122,9 @@ fig.write_image("images/fig1.svg")
 fig.write_image("images/fig1.pdf")
 ~~~
 
-**Note:** Figures containing WebGL traces (i.e. of type `scattergl`, `contourgl`, `scatter3d`, `surface`, `mesh3d`, `scatterpolargl`, `cone`, `streamtube`, `splom`, or `parcoords`) that are exported in a vector format will include encapsulated rasters, instead of vectors, for some parts of the image.
+**Note:** Figures containing WebGL traces (i.e. of type `scattergl`, `scatter3d`, `surface`, `mesh3d`, `scatterpolargl`, `cone`, `streamtube`, `splom`, or `parcoords`) that are exported in a vector format will include encapsulated rasters, instead of vectors, for some parts of the image. This is a fundamental limitation of WebGL, which renders to a grid of pixels rather than to individual shapes.
+
+Note that Plotly Express automatically uses WebGL for scatter-type figures with more than 1,000 data points: the default `render_mode="auto"` switches from `scatter` to `scattergl` above this threshold. If your exported SVG or PDF unexpectedly contains rasterized markers, this is likely why. To force fully-vector output, pass `render_mode="svg"` to the Plotly Express function, or use `go.Scatter` instead of `go.Scattergl` with graph objects. Note that fully-vector rendering can be slow for figures with many points, which is the reason WebGL is used by default above 1,000 points. See [WebGL Rendering](/python/webgl-vs-svg/) for more on this tradeoff.
 
 
 ### Specify a Format
diff --git a/doc/python/static-image-generation-migration.md b/doc/python/static-image-generation-migration.md
index 63b5872ba4..1ce6e8cdbb 100644
--- a/doc/python/static-image-generation-migration.md
+++ b/doc/python/static-image-generation-migration.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Static Image Generation Changes in Plotly.py 6.1
-    order: 40
+    order: 41
     page_type: u-guide
     permalink: python/static-image-generation-changes/
     thumbnail: thumbnail/static-image-export.png
@@ -38,7 +38,7 @@ jupyter:
 
 Plotly.py 6.1 introduces support for Kaleido v1, which [improves static image generation](https://plotly.com/blog/kaleido-the-next-generation/) for Plotly figures.
 
-While adding support for Kaleido v1, we are deprecating support for earlier versions of Kaleido and support for [Orca](/python/orca-management/). Support for Orca and earlier versions of Kaleido will be removed after September 2025, and we recommend updating to the latest Kaleido. This page documents how to migrate your Plotly code to Kaleido v1 and outlines the changes in functionality.
+Plotly.py 7.0 removed support for earlier versions of Kaleido and support for [Orca](/python/orca-management/). If you still use Orca or Kaleido v0, update to the latest Kaleido. This page documents how to migrate your Plotly code to Kaleido v1 and outlines the changes in functionality.
 
 To migrate from either Orca or Kaleido v0, first install the latest Kaleido with:
 
diff --git a/doc/python/styling-plotly-express.md b/doc/python/styling-plotly-express.md
index 60c4a3a30d..ab8e62df8e 100644
--- a/doc/python/styling-plotly-express.md
+++ b/doc/python/styling-plotly-express.md
@@ -29,7 +29,7 @@ jupyter:
     language: python
     layout: base
     name: Styling Plotly Express Figures
-    order: 30
+    order: 31
     page_type: u-guide
     permalink: python/styling-plotly-express/
     thumbnail: thumbnail/plotly-express.png
diff --git a/doc/python/subplots.md b/doc/python/subplots.md
index dd05d3baf9..d63e928ceb 100644
--- a/doc/python/subplots.md
+++ b/doc/python/subplots.md
@@ -28,7 +28,7 @@ jupyter:
     language: python
     layout: base
     name: Subplots
-    order: 17
+    order: 18
     page_type: u-guide
     permalink: python/subplots/
     redirect_from: ipython-notebooks/subplots/
diff --git a/doc/python/supported-colors.md b/doc/python/supported-colors.md
index 3e190f081c..c558eb2b1c 100644
--- a/doc/python/supported-colors.md
+++ b/doc/python/supported-colors.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Supported CSS Colors
-    order: 41
+    order: 42
     page_type: example_index
     permalink: python/css-colors/
     thumbnail: thumbnail/shape.jpg
@@ -140,3 +140,20 @@ fig.update_layout(
 
 fig.show()
 ```
+
+## Other Color Formats
+
+*Changed in 7.0*
+
+As well as named colors, color properties accept color strings in the formats defined by the [CSS Color 4 specification](https://www.w3.org/TR/css-color-4/), including `rgb()`, `rgba()`, `hsl()`, `hsla()`, `hwb()`, `lab()`, `lch()`, `oklab()`, `oklch()`, `color()`, and hexadecimal notation with a leading `#`.
+
+Version 7 parses these strings according to that specification. Four formats that earlier versions accepted no longer give the same result. A string that cannot be parsed at all falls back to the property's default:
+
+| No longer works | Example | Use instead |
+|---|---|---|
+| The `hsv()` color function | `"hsv(200, 80%, 80%)"` | `"hsl(200, 67%, 47%)"`, `"hwb()"`, hexadecimal, or `"rgb()"` |
+| Comma separated saturation and lightness values without percent units | `"hsl(0, 100, 40)"` | `"hsl(0, 100%, 40%)"`, or the space separated `"hsl(0 100 40)"` |
+| Channel values given as fractions of 1 | `"rgb(0.5, 0.5, 0.5)"` (now renders as near black) | `"rgb(128, 128, 128)"` |
+| Hexadecimal values without a leading `#` | `"fff"` | `"#fff"` |
+
+These rules apply to color strings only. Numeric arrays used with a [colorscale](/python/colorscales/) are unaffected.
diff --git a/doc/python/text-and-annotations.md b/doc/python/text-and-annotations.md
index 7d9570d5f5..5b7992168a 100644
--- a/doc/python/text-and-annotations.md
+++ b/doc/python/text-and-annotations.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Text and Annotations
-    order: 22
+    order: 23
     permalink: python/text-and-annotations/
     thumbnail: thumbnail/text-and-annotations.png
 ---
diff --git a/doc/python/tick-formatting.md b/doc/python/tick-formatting.md
index d1f2d0c1a1..7c7ce34248 100644
--- a/doc/python/tick-formatting.md
+++ b/doc/python/tick-formatting.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Formatting Ticks
-    order: 12
+    order: 13
     permalink: python/tick-formatting/
     thumbnail: thumbnail/tick-formatting.gif
 ---
diff --git a/doc/python/troubleshooting.md b/doc/python/troubleshooting.md
index c79a3727e5..2452d9e02a 100644
--- a/doc/python/troubleshooting.md
+++ b/doc/python/troubleshooting.md
@@ -28,7 +28,7 @@ jupyter:
     language: python
     layout: base
     name: Troubleshooting
-    order: 27
+    order: 28
     page_type: u-guide
     permalink: python/troubleshooting/
     thumbnail: thumbnail/modebar-icons.png
diff --git a/doc/python/v4-migration.md b/doc/python/v4-migration.md
index b6b25de461..1035feb51f 100644
--- a/doc/python/v4-migration.md
+++ b/doc/python/v4-migration.md
@@ -27,7 +27,7 @@ jupyter:
     language: python
     layout: base
     name: Version 4 Migration Guide
-    order: 39
+    order: 40
     page_type: example_index
     permalink: python/v4-migration/
     thumbnail: thumbnail/v4-migration.png
diff --git a/doc/python/v6-changes.md b/doc/python/v6-changes.md
index 65ff611df8..87c33827e8 100644
--- a/doc/python/v6-changes.md
+++ b/doc/python/v6-changes.md
@@ -34,7 +34,7 @@ jupyter:
     thumbnail: thumbnail/v4-migration.png
 ---
 
-This page outlines the changes in Plotly.py version 6 and cases where you may need to update your charts or tools that you use for working with Plotly.py.
+This page outlines the changes in Plotly.py version 6 and cases where you may need to update your charts or tools that you use for working with Plotly.py. For the next release, see [Changes in Version 7](/python/v7-migration/).
 
 <!-- #region -->
 ## Jupyter Notebook Support
diff --git a/doc/python/v7-changes.md b/doc/python/v7-changes.md
new file mode 100644
index 0000000000..46dbe05a79
--- /dev/null
+++ b/doc/python/v7-changes.md
@@ -0,0 +1,206 @@
+---
+jupyter:
+  jupytext:
+    notebook_metadata_filter: all
+    text_representation:
+      extension: .md
+      format_name: markdown
+      format_version: '1.3'
+      jupytext_version: 1.16.4
+  kernelspec:
+    display_name: Python 3 (ipykernel)
+    language: python
+    name: python3
+  language_info:
+    codemirror_mode:
+      name: ipython
+      version: 3
+    file_extension: .py
+    mimetype: text/x-python
+    name: python
+    nbconvert_exporter: python
+    pygments_lexer: ipython3
+    version: 3.11.10
+  plotly:
+    description: Guide to changes in version 7 of Plotly.py and how to migrate from
+      version 6
+    display_as: file_settings
+    language: python
+    layout: base
+    name: Changes in Version 7
+    order: 9
+    page_type: example_index
+    permalink: python/v7-migration/
+    thumbnail: thumbnail/v4-migration.png
+---
+
+This page outlines the changes in Plotly.py version 7 and cases where you may need to update your charts or the tools you use for working with Plotly.py.
+
+Version 7 upgrades the bundled Plotly.js from version 3 to version 4, so it includes the Plotly.js changes as well as the Plotly.py ones. Most figures render without any changes. The sections below cover the cases where you need to update your code.
+
+## Removed Traces
+
+The Mapbox-based traces were deprecated in version 6 and have been removed in version 7. Use the MapLibre-based traces instead, which have the same attributes.
+
+| Removed | Use instead |
+|---|---|
+| `go.Scattermapbox` | `go.Scattermap` |
+| `go.Choroplethmapbox` | `go.Choroplethmap` |
+| `go.Densitymapbox` | `go.Densitymap` |
+| `px.scatter_mapbox` | `px.scatter_map` |
+| `px.line_mapbox` | `px.line_map` |
+| `px.choropleth_mapbox` | `px.choropleth_map` |
+| `px.density_mapbox` | `px.density_map` |
+
+```python
+import plotly.graph_objects as go
+
+fig = go.Figure(go.Scattermap(
+    lon=[-73.57, -79.38, -123.12],
+    lat=[45.50, 43.65, 49.28],
+    mode="markers",
+    marker=dict(size=12),
+))
+
+fig.show()
+```
+
+See [Migrate to MapLibre](/python/mapbox-to-maplibre/) for the full list of changes when moving from the Mapbox traces.
+
+## Removed Attributes
+
+### `layout.mapbox`
+
+The `mapbox` subplot has been removed. Use `layout.map`, which takes the same attributes. In Plotly Express, `mapbox_style` becomes `map_style`.
+
+### `stream`
+
+The `stream` attribute has been removed from all traces. It configured the Chart Studio streaming service, which is no longer available.
+
+### `*src` attributes
+
+Attributes ending in `src` (`xsrc`, `ysrc`, `textsrc`, `marker.colorsrc`, and so on) have been removed, along with `layout.hidesources`. They referenced data sources in Chart Studio.
+
+### Chart Studio configuration options
+
+The `showLink`, `link_text`, `sendData`, `showSources`, and `showEditInChartStudio` configuration options have been removed. To let users share a chart, use `showSendToCloud`, which is enabled by default in version 7 and adds a "Share chart…" button to the mode bar.
+
+## Removed Figure Factories
+
+The deprecated figure factories `create_2d_density`, `create_annotated_heatmap`, `create_bullet`, `create_candlestick`, `create_choropleth`, `create_distplot`, `create_facet_grid`, `create_gantt`, `create_hexbin_mapbox`, `create_ohlc`, `create_scatterplotmatrix`, and `create_violin` have been removed. [Figure Factories](/python/figure-factories/) lists the recommended alternative for each one.
+
+## Static Image Export
+
+Support for Kaleido versions earlier than 1.0.0 has been removed, along with support for Orca. The `engine` argument has been removed from `fig.write_image()`, `fig.to_image()`, `pio.write_image()`, `pio.write_images()`, `pio.to_image()`, `pio.full_figure_for_development()`, and from renderer constructors. See [Static Image Export](/python/static-image-export/).
+
+## Changed Defaults
+
+### Maps fit to your data
+
+`geo` subplots (used by `go.Scattergeo` and `go.Choropleth`) now fit their initial view to the locations they plot: `layout.geo.fitbounds` defaults to `"locations"` instead of `False`. Tile-based `map` subplots do the same, through a new `layout.map.fitbounds` attribute that also defaults to `"locations"`.
+
+Figures that already set a view render unchanged. To get the previous world view, set `fitbounds=False`:
+
+```python
+import plotly.graph_objects as go
+
+fig = go.Figure(go.Choropleth(locations=["CAN", "MEX"], z=[1, 2], showscale=False))
+
+fig.update_layout(geo=dict(fitbounds=False))
+
+fig.show()
+```
+
+Setting your own view attributes also turns auto-fitting off. On a `geo` subplot, `center` and `projection.scale` always do this, and `projection.rotation`, `lonaxis.range`, and `lataxis.range` do except on a scoped subplot with a clipped projection. On a `map` subplot, `center` or `zoom` does it.
+
+### Overlaying axes share tick positions
+
+An axis that overlays another (`yaxis2.overlaying="y"`) now defaults `tickmode` to `"sync"`: it draws ticks and gridlines at the base axis's positions, labeled from its own range, so the two axes share one grid. Set `tickmode="auto"` on the overlaying axis for the previous behavior of two independent grids.
+
+### Scatter plot matrix axes are linked
+
+`go.Splom` now defaults `axis.matches` to `True`, so axes in the same row and column are linked and pan and zoom together. Plotly Express already set this on the figures it generated. Set `matches=False` on the relevant axes for the previous behavior.
+
+## Color Parsing
+
+Plotly.js now parses colors according to the CSS Color 4 specification. Four color string formats that previously worked no longer produce the same color, and an unparseable color falls back to the attribute's default:
+
+| No longer works | Example | Use instead |
+|---|---|---|
+| The `hsv()` color function | `"hsv(200, 80%, 80%)"` | `"hsl(200, 67%, 47%)"`, `"hwb()"`, hexadecimal, or `"rgb()"` |
+| Comma separated saturation and lightness values without percent units | `"hsl(0, 100, 40)"` | `"hsl(0, 100%, 40%)"`, or the space separated `"hsl(0 100 40)"` |
+| Channel values given as fractions of 1 | `"rgb(0.5, 0.5, 0.5)"` (now renders as near black) | `"rgb(128, 128, 128)"` |
+| Hexadecimal values without a leading `#` | `"fff"` | `"#fff"` |
+
+These rules apply to color *strings* only. Numeric arrays used with a colorscale are unaffected. Automatically computed contrast colors, such as text on heatmap cells, can also shift slightly around mid-luminance backgrounds.
+
+Separately, `plotly.colors.hex_to_rgb` now parses 3-digit shorthand hexadecimal colors such as `#FFF` correctly.
+
+## Country Names
+
+`locationmode="country names"` is now resolved by [country-iso-search](https://github.com/plotly/country-iso-search) rather than a set of regular expressions. It accepts more forms — ISO-3166 codes, UN M49 numeric codes, flag emoji, historical and native names such as `"Burma"` and `"Türkiye"` — and ignores case, accents, and punctuation. It rejects partial phrases that previously matched by accident. Unrecognized names are logged and their locations are skipped. Use `locationmode="ISO-3"` with ISO codes if you need certainty.
+
+## Tile Map Rendering
+
+Three rendering details changed for `go.Scattermap`:
+
+- Marker icons are tinted with `marker.color`. Previously they were always black. Pass `marker=dict(color="black")` for the previous appearance.
+- The Maki icon set was updated from version 2.1 to 8.2. A few icon names were removed between those versions.
+- Legend swatches always draw a circle, regardless of `marker.symbol`.
+
+## Sankey Layout
+
+The Sankey layout algorithm was updated (`@plotly/d3-sankey` 0.7.2 to 0.12.3). Node positions and link paths shift slightly for the same data, with links tending to cross less.
+
+Two new Sankey attributes let you override the automatic ordering: `node.sort` and `link.sort`.
+
+For both attributes, the default value `"auto"` reorders nodes within a column, and links within a node, to reduce crossings. `"input"` keeps the order given in `node.label` and in `link.source` / `link.target`, which is useful when the order carries meaning or you need a layout that is stable across renders.
+
+```python
+import plotly.graph_objects as go
+
+fig = go.Figure(go.Sankey(
+    node=dict(label=["A", "B", "C", "D", "Z", "Y", "X", "W"], pad=15, thickness=20,
+              sort="input"),
+    link=dict(source=[0, 1, 2, 3], target=[4, 5, 6, 7], value=[4, 3, 2, 1],
+              sort="input"),
+))
+
+fig.show()
+```
+A third attribute, `direction`, controls the flow along the `orientation` axis. The default value of `"forward"` results in a chart which flows from left to right horizontally, or top to bottom vertically. Set it to `"reversed"` to create a chart which flows from right to left or bottom to top. See [Sankey Diagram](/python/sankey-diagram/).
+
+## New Traces and Attributes
+
+### `go.Quiver`
+
+Version 7 adds a `Quiver` trace type for 2D vector fields, which supercedes the `create_quiver` figure factory as the recommended approach for creating quiver plots. See [Quiver Plots](/python/quiver-plots/) for more detail.
+
+```python
+import plotly.graph_objects as go
+
+fig = go.Figure(go.Quiver(x=[0, 1, 2, 0, 1, 2], y=[0, 0, 0, 1, 1, 1],
+                          u=[1, 0.5, 0, 0.5, 0, -0.5], v=[0, 0.5, 1, 0.5, 1, 0.5]))
+
+fig.show()
+```
+
+### Geo zoom limits
+
+New attributes `layout.geo.projection.minscale` and `maxscale` clamp how far users can zoom a `geo` subplot. Both are multipliers of `projection.scale`:
+
+```python
+import plotly.graph_objects as go
+
+fig = go.Figure(go.Scattergeo(lon=[2.35, 13.4, 12.5, -3.7], lat=[48.86, 52.52, 41.9, 40.42],
+                              mode="markers"))
+
+fig.update_layout(geo=dict(scope="europe",
+                           projection=dict(scale=1, minscale=0.5, maxscale=4)))
+
+fig.show()
+```
+
+## MathJax
+
+Plotly.js now supports MathJax version 3 and version 4 for rendering LaTeX, and support for MathJax version 2 has been removed. If you render figures in an environment that loads MathJax itself, such as a notebook or a custom HTML page, make sure it loads version 3 or later.
diff --git a/doc/python/wide-form.md b/doc/python/wide-form.md
index 0f49aed028..b48aad418f 100644
--- a/doc/python/wide-form.md
+++ b/doc/python/wide-form.md
@@ -28,7 +28,7 @@ jupyter:
     language: python
     layout: base
     name: Plotly Express Wide-Form Support
-    order: 34
+    order: 35
     page_type: u-guide
     permalink: python/wide-form/
     thumbnail: thumbnail/plotly-express.png
diff --git a/doc/requirements.txt b/doc/requirements.txt
index f80b22e528..ce5701ef0c 100644
--- a/doc/requirements.txt
+++ b/doc/requirements.txt
@@ -1,4 +1,4 @@
-plotly==6.7.0
+plotly==7.0.0
 anywidget
 cufflinks==0.17.3
 dash-bio