You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Instructions (remove this section before submitting report)
10
+
11
+
Thanks for your interest in plotly.py!
12
+
13
+
- Before submitting a new bug report, please search for existing and closed issues. If your bug is not addressed yet, fill out the sections below and submit a new issue.
14
+
- Implementation questions ("How do I do ...?") should be asked on our [Community Forum](https://community.plotly.com/c/plotly-python/5) or on [Stack Overflow](https://stackoverflow.com/questions/tagged/plotly) (tagged 'plotly').
15
+
- Comments should add content to the discussions. Approbation comments such as *+1* or *I would like this feature to be implemented as well* will be deleted by the maintainers. Please use [GitHub reactions](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments) instead.
16
+
17
+
### Description
18
+
19
+
_Add a clear description of the issue that you're having._
20
+
21
+
### Screenshots/Video
22
+
23
+
_Add screenshots or a video of the issue._
24
+
25
+
### Steps to reproduce
26
+
27
+
_Reports **must** include steps to reproduce the issue. Please use the [latest version](https://github.com/plotly/plotly.py/releases) of plotly.py in your report unless not applicable._
28
+
29
+
- Go to '...'
30
+
- Click on X
31
+
- Note the issue with Y
32
+
33
+
### Notes
34
+
35
+
_Add info here that doesn't fit in the other sections._
### Instructions (remove this section before submitting an issue)
10
+
11
+
Thanks for your interest in plotly.py!
12
+
13
+
- Before submitting a new feature request, please search for existing and closed requests. If your request is novel, fill out the sections below and submit a new request.
14
+
- Comments should add content to the discussions. Approbation comments such as *+1* or *I would like this feature to be implemented as well* will be deleted by the maintainers. Please use [GitHub reactions](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments) instead.
15
+
16
+
### Description
17
+
18
+
_Add a clear description of the feature that you're requesting._
19
+
20
+
21
+
### Why should this feature be added?
22
+
23
+
_Provide an argument for why this feature should be added. We can't add everything, so this will help us determine what gets worked on. Please also consider creating a PR and adding the feature yourself. Help is always appreciated._
24
+
25
+
### Mocks/Designs
26
+
27
+
_Please add any mocks or designs you might have for the feature._
28
+
29
+
### Notes
30
+
31
+
_Add info here that doesn't fit in the other sections._
Copy file name to clipboardExpand all lines: CHANGELOG.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,16 @@ This project adheres to [Semantic Versioning](http://semver.org/).
4
4
5
5
## Unreleased
6
6
7
+
## [6.5.1] - 2025-11-17
8
+
9
+
### Fixed
10
+
- Fix issue where Plotly Express ignored trace-specific color sequences defined in templates via `template.data.<trace_type>`[[#5437](https://github.com/plotly/plotly.py/pull/5437)], with thanks to @antonymilne for the contribution!
11
+
12
+
### Updated
13
+
- Speed up `validate_gantt` function [[#5386](https://github.com/plotly/plotly.py/pull/5386)], with thanks to @misrasaurabh1 for the contribution!
14
+
- Update plotly.js from version 3.3.0 to version 3.3.1. See the plotly.js [release notes](https://github.com/plotly/plotly.js/releases/tag/v3.3.1) for more information. [[#5456](https://github.com/plotly/plotly.py/pull/5456)]. Notable changes include:
15
+
- Add support for arrays for the pie properties `showlegend` and `legend`, so that these can be configured per slice. [[#7580](https://github.com/plotly/plotly.js/pull/7580)]
0 commit comments