Release 14.0.0

[serge-sans-paille]

Contributors:

• AntoinePrv
• Chris Lu
• Clément Garnier
• emrys53
• Johan Mabille
• liangbin
• Marco Barbone
• Marian Klymov
• Markus Wick
• serge-sans-paille
• Sylvain Corlay
• Warren Weckesser

[serge-sans-paille]

@JohanMabille not to be merged, just to get the ball rolling. The changelog was dense so I started grouping it by themes.

Also major release because there's an API break

[AntoinePrv]

@serge-sans-paille there are two more improvements to swizzle that I would like to get in if possible.

• Add 8/16 bits AVX2 swizzle #1197 for 8/16 bits (WIP need to fix the errors);
• I have further improvement to the general case for batch_constant;

I can possibly have that within a week. Would that work?

I also have an idea for improving some specific cases on batch_constant but it's a longer shot (possibly very hard under C++11).

[JohanMabille]

THe initial "plan" was to release mid November, but we didn't fix any date, so I think releasing in one week is fine.

[serge-sans-paille]

On Mon, Nov 10, 2025 at 11:00:36AM -0800, Antoine Prouvost wrote: ●AntoinePrv left a comment [1](xtensor-stack/xsimd#1196) ***@***.*** there are two more improvements to swizzle that I would like to get in if possible. • [3]GH-1197 for 8/16 bits (WIP need to fix the errors); • I have further improvement to the general case for batch_constant; I also have an idea for improving some specific cases on batch_constant but it's a longer shot (possibly very hard under C++11).

Sure, I'll review those.

[DiamonDinoia]

I am also trying to get the masked_api done asap. I am just busy with deadlines at the moment.

[AntoinePrv]

@serge-sans-paille last thing before the release, I think we should investigate the issue I mentioned in below.
I believe this is a bug from the masked load PR. @DiamonDinoia did you have the opportunity to have a look?

#1212 (comment)

[DiamonDinoia]

I was travelling last week. I just got back I will try to have a look today.

[AntoinePrv]

Thanks a lot!

[serge-sans-paille]

Everything except #1226 has been merged, we're getting close!

[serge-sans-paille]

@JohanMabille I've updated the contributor list (in the commit message) and the Changelog with the latest commit, I think we're good to go. Do you want to do the release, or Should i handle this? It's fine for me to do this in ~4h

[JohanMabille]

I'm fine with both options, but I won't be able to do it before tomorrow morning.If you do it, can you squash and merge instead of merging (or directly push the commit on master but I think it's equivalent). Also we use annotated tags for release in the stack (but I can't remember why ^^).

[serge-sans-paille]

I'm fine with both options, but I won't be able to do it before tomorrow morning.If you do it, can you squash and merge instead of merging (or directly push the commit on master but I think it's equivalent). Also we use annotated tags for release in the stack (but I can't remember why ^^).

ok, I leave it to you then, don't want to mess up with your workflow ;-)

[JohanMabille]

Release done by cherry-picking the commit and pushing it to master, closing this one.