v1.4.1 release tag is wrong

[Tieqiong]

@sbillinge I just checked the recent v1.4.1 GitHub release, and it seems like it has it was tagged on the wrong branch. It has commits up to #34 (main branch) but we need to have commits up to #39 (windows branch).

Now we also have the new workflow, which only requires to push the tag and it will automatically GitHub release and generate sha256 in the release message.

[sbillinge]

thanks for letting me know. I will try and do that release again.....

[sbillinge]

OK, I pushed a new tag. It seemed to make the new release on GH automatically. Please could you check it?

[Tieqiong]

@sbillinge Thanks! I think it's correct now.

[sbillinge]

At what point do we want to merge windows into main?

[Tieqiong]

@sbillinge I think we are probably safe to merge it now. Or maybe we want someone to test the new diffpy.srreal release backend by this new libdiffpy? I'll make the full conda-forge release recipe update now

[sbillinge]

Let's have Caden see if he can get srreal to pass tests now. Then let me know and I will merge to main and redo the release. The release bundle will be the same, but it may be confusing if metadata about some weird windows branch is hanging around.