Update 0.6.0 release notes with more complete highlights and more PRs #665

jni · 2025-04-10T14:46:53Z

No description provided.

TimMonko

I didn't finish reviewing, and this is certainly not blocking release, but I think it's worth highlighting the fit to view addition and toggling ndisplay not resetting the camera

TimMonko · 2025-04-10T14:56:08Z

docs/release/release_0_6_0.md

+
+⚠️ *In 0.6.0a1 and earlier, this only works when installing
+PartSegCore-compiled-backend and toggling the "use compiled triangulation"
+option in the advanced preferences. In 0.6.0 it will work wiht all


Suggested change

option in the advanced preferences. In 0.6.0 it will work wiht all

option in the advanced preferences. In 0.6.0 it will work with all

TimMonko · 2025-04-10T15:03:44Z

docs/release/release_0_6_0.md

+During the 0.6.x series, if some plugin functionality is broken by the
+automatic conversion, you can turn off this conversion in the plugin
+preferences. However, this option will go away in 0.7.0, which we anticipate to
+happen sometime in July. Therefore, if you encounter conversion issues in a


This date genuinely seems too optimistic. Is the goal for plugins to update quickly? Make us panic a bit? Maybe I just don't know the 0.7 roadmap enough

psobolewskiPhD · 2025-04-10T17:02:44Z

docs/release/release_0_6_0.md

+
+  ![axis orientation dialog](https://github.com/user-attachments/assets/f73898ec-9156-4f73-ab7f-ee2a7cc17fe1)
+
+3. If you want to use a specific axis orientation consistently, you can set the


Not a blocker of this alpha, but for the final release we should make clear what the settings were before 0.6.0 vs. the new default, so that a user who wants to go back to the old behavior can do so relatively easily.
See: napari/napari#7787 (comment)

willingc

No blockers.

willingc · 2025-04-10T17:28:22Z

docs/release/release_0_6_0.md

+### Summary
+
+- Updated viewer handedness ✋
+- Command pallette 🎨


Suggested change

- Command pallette 🎨

- Command palette 🎨

willingc · 2025-04-10T17:30:39Z

docs/release/release_0_6_0.md

+  See an example of this in action in
+  {ref}`sphx_glr_gallery_xarray-latlon-timeseries.py`.
+
+2. By right clicking on the dimension toggle in the viewer, and setting the


Suggested change

2. By right clicking on the dimension toggle in the viewer, and setting the

2. **Through the UI:** By right clicking on the dimension toggle in the viewer, and setting the

willingc · 2025-04-10T17:31:20Z

docs/release/release_0_6_0.md

+
+  ![axis orientation dialog](https://github.com/user-attachments/assets/f73898ec-9156-4f73-ab7f-ee2a7cc17fe1)
+
+3. If you want to use a specific axis orientation consistently, you can set the


Suggested change

3. If you want to use a specific axis orientation consistently, you can set the

3. **Through default startup settings:** If you want to use a specific axis orientation consistently, you can set the

willingc · 2025-04-10T17:35:40Z

docs/release/release_0_6_0.md

+preferences. However, this option will go away in 0.7.0, which we anticipate to
+happen sometime in July. Therefore, if you encounter conversion issues in a


Suggested change

preferences. However, this option will go away in 0.7.0, which we anticipate to

happen sometime in July. Therefore, if you encounter conversion issues in a

preferences. However, this plugin conversion preferences option will be removed in 0.7.0, which we anticipate to

happen sometime in the second half of 2025. If you encounter conversion issues in a

willingc · 2025-04-10T17:41:08Z

docs/release/release_0_6_0.md

+- Update roadmap index to highlight global roadmap  ([docs#651](https://github.com/napari/docs/pull/651))
+- Add missing magicgui imports ([docs#655](https://github.com/napari/docs/pull/655))
+- Surface plugin best practices ([docs#656](https://github.com/napari/docs/pull/656))
+- Add Tim Monko to core developers list ([docs#662](https://github.com/napari/docs/pull/662))


🎉 🙌🏼 💐

DragaDoncila

Left some minor comments, no blockers!

DragaDoncila · 2025-04-11T03:43:26Z

docs/release/release_0_6_0.md



+*Thu, Apr 10, 2025*


I'm not sure why there's the two dates here?

Oh! Because it's autogenerated from two different files and only one of them is supposed to have the date but I forgot this 😅

DragaDoncila · 2025-04-11T03:45:11Z

docs/release/release_0_6_0.md

+  ![napari settings panel with axis orientation options highlighted](https://github.com/user-attachments/assets/f5032320-8b03-4ff7-9cb7-8b182ab232af)
+
+  To restore the orientation from napari 0.5.6 and earlier, change the Depth
+  axis setting to "away" (ie depth axis points away from you).


Suggested change

axis setting to "away" (ie depth axis points away from you).

axis setting to "away" (i.e. depth axis points away from you).

DragaDoncila · 2025-04-11T03:47:17Z

docs/release/release_0_6_0.md

+
+During the 0.6.x series, if some plugin functionality is broken by the
+automatic conversion, you can turn off this conversion in the plugin
+preferences. However, the option to turn not convert npe1 plugins will be


Suggested change

preferences. However, the option to turn not convert npe1 plugins will be

preferences. However, the option to turn off conversion of npe1 plugins will be

DragaDoncila · 2025-04-11T03:50:20Z

docs/release/release_0_6_0.md

+If you encounter conversion issues in a plugin you rely on, please contact the
+plugin authors to encourage them to migrate their plugin to the npe2 system.
+
+If you are a plugin author and your plugin is not yet npe2-compatible, please


I would add a link to the more detailed guide here e.g.

Suggested change

If you are a plugin author and your plugin is not yet npe2-compatible, please

For more detail on this change and how it affects plugins, see the [detailed guide](adapted-plugin-guide). If you are a plugin author and your plugin is not yet npe2-compatible, please

DragaDoncila · 2025-04-11T03:51:22Z

docs/release/release_0_6_0.md

+For developers: napari now depends on Python 3.10+ and Pydantic v2.2.
+
+We've supported both pydantic 1 and 2 since 0.4.19, but we're now ready to take
+advantage of performance and API improvements of Pydantic 2. If your library


Suggested change

advantage of performance and API improvements of Pydantic 2. If your library

advantage of the performance and API improvements of Pydantic 2. If your library

DragaDoncila · 2025-04-11T03:52:42Z

docs/release/release_0_6_0.md


 (+) denotes first-time contributors 🥳

- [Andrew Sweet](https://github.com/napari/napari/commits?author=andy-sweet) - @andy-sweet
+- [andrew sweet](https://github.com/napari/napari/commits?author=andy-sweet) - @andy-sweet


Why did Andy and Clement lose their capital letters 😅

🤔 something weird about their GH profiles. As far as I remember, this is obtained from the GH API... But their profile pages are correct... 🤔 Anyway, will manually fix for now.

* Add draft notes * Add intro similar to python * Update highlights for 0.6.0 * Fix codespell-spotted typos * Address comments from reviews in napari/docs#665 * Address more review comments * Generate date in italics * Use 3-letter day-of-week in release notes * Further changes since 0.6.0a1 * Add pre-commit to release env, needed to commit here * Fix markdown escape character * Remove pre-release warning --------- Co-authored-by: Juan Nunez-Iglesias <jni@fastmail.com>

Update 0.6.0 release notes with more complete highlights and more PRs

614735d

github-actions bot assigned jni Apr 10, 2025

github-actions bot added the documentation Improvements or additions to documentation label Apr 10, 2025

TimMonko reviewed Apr 10, 2025

View reviewed changes

psobolewskiPhD reviewed Apr 10, 2025

View reviewed changes

willingc approved these changes Apr 10, 2025

View reviewed changes

jni added this to the 0.6.0 milestone Apr 11, 2025

jni added 4 commits April 11, 2025 11:54

Fix codespell-spotted typos

51e58e1

Address review comments

cacfff9

Add this PR

23119f9

Add PR updating tooltips

3c33113

DragaDoncila approved these changes Apr 11, 2025

View reviewed changes

jni added 2 commits April 11, 2025 14:59

Address more review comments

85698d4

Missed review comment

dee93ac

jni added a commit to willingc/napari-release-tools that referenced this pull request Apr 11, 2025

Address comments from reviews in napari/docs#665

60784b4

jni added the ready to merge label Apr 11, 2025

jni merged commit aab55ad into napari:main Apr 11, 2025
9 checks passed

github-actions bot removed the ready to merge label Apr 11, 2025

jni deleted the relnotes060-2 branch April 11, 2025 07:10

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update 0.6.0 release notes with more complete highlights and more PRs #665

Update 0.6.0 release notes with more complete highlights and more PRs #665

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

	option in the advanced preferences. In 0.6.0 it will work wiht all
	option in the advanced preferences. In 0.6.0 it will work with all


		![axis orientation dialog](https://github.com/user-attachments/assets/f73898ec-9156-4f73-ab7f-ee2a7cc17fe1)

		3. If you want to use a specific axis orientation consistently, you can set the

	2. By right clicking on the dimension toggle in the viewer, and setting the
	2. Through the UI: By right clicking on the dimension toggle in the viewer, and setting the

	3. If you want to use a specific axis orientation consistently, you can set the
	3. Through default startup settings: If you want to use a specific axis orientation consistently, you can set the

		preferences. However, this option will go away in 0.7.0, which we anticipate to
		happen sometime in July. Therefore, if you encounter conversion issues in a

	axis setting to "away" (ie depth axis points away from you).
	axis setting to "away" (i.e. depth axis points away from you).

	preferences. However, the option to turn not convert npe1 plugins will be
	preferences. However, the option to turn off conversion of npe1 plugins will be

	If you are a plugin author and your plugin is not yet npe2-compatible, please
	For more detail on this change and how it affects plugins, see the [detailed guide](adapted-plugin-guide). If you are a plugin author and your plugin is not yet npe2-compatible, please

	advantage of performance and API improvements of Pydantic 2. If your library
	advantage of the performance and API improvements of Pydantic 2. If your library

Update 0.6.0 release notes with more complete highlights and more PRs #665

Update 0.6.0 release notes with more complete highlights and more PRs #665

Uh oh!

Conversation

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!