Auto-updater is back to v8.7.1.

@donho ,
It worked for me, just fine, with the Multiline enabled. Loaded all the files twice, closing all from the right first, and then reloading and closing all from the left…and it works just fine. Thanks to you from those that use that many tabs…of which I’m not one. :-)

FYI, due to 1 critical crash bug (of new Pin Tab feature), & 1 regression (of redundant dialog as opening a folder) Notepad++ v8.7.3 will be out in the weekend. There won’t be RC for v8.7.3.

Small comment to the change.log:
Shouldn’t it show “Notepad++ v8.7.2 new features & bug-fixes:”?
I’m missing the “s” at feature (features & fixes)?

@Luigi-C said in Notepad++ release 8.7.1:

When shifting, left or right, more text rows contemporary in column mode by pressing the TAB key…

English-speaking forum readers may like to know that “contemporary” is used here as in Italian contemporanea‍mente: literally, “at the same time”

@rddim
I will make as large as possible for some checkbox (without enlarging the dialog width) in the next release. Please find other shorter words or the abbreviation for the translation.

@donho Thank you. Yes. Sorry for the confusion. I meant the CVE-2024-7264 present in updater/libcurl.dll. When is it possible to get v8.7.1 released?

@Joshua-Philipo that mean that the person who hacked your account knows your login details

@Madhav-Vasanth ,

See https://github.com/notepad-plus-plus/wingup/issues/73 - the fix will be in the next rev.

@donho since you are so well versed on this codebase whats your opinion on this ai generated documentation?

@abitawoods1 said in Notepad++ release 8.6.9:

The DLG box for consent ends up underneath the in-progress dialog. The in-progress reaches 100% and then churns.

Both problems should have already been fixed.
So it should be ok from the next version onward (probably a v8.7).
More e.g. here: GitHub issue #15507 .

To translators: in the project Wingup, there is a
new file you can translate and whose Notepad++ use

@Darius-Gricius

GitHub issue #15324.
Fix is already in progress, it should be included in the upcoming next N++ version.