Bump WebAPI version

[glassez]

#13995 was supposed to be included in the release along with other API changes, so both PRs had a version change to 2.7.0. However, it ended up in another release, and I forgot to upgrade the version again.

Unfortunately, it is unlikely to fix a problem like #14266, but at least it will fix it for users of intermediate/test builds.
@qbittorrent/bug-handlers, what do you think?

[masterwishx]

OK :-) , so we need to wait next version 4.3.4 ?
for rename folder in WEBUI #13995 ?

[glassez]

OK :-) , so we need to wait next version 4.3.4 ?
for rename folder in WEBUI #13995 ?

"rename folder in WEBUI" is in v4.3.3.
The problem is that I forgot to increase the web API version number. This affects third-party web clients.

[masterwishx]

OK :-) , so we need to wait next version 4.3.4 ?
for rename folder in WEBUI #13995 ?

"rename folder in WEBUI" is in v4.3.3.
The problem is that I forgot to increase the web API version number. This affects third-party web clients.

so its cant be used even its avalible in code of 4.3.3 and we need to wait next release 4.3.4 with fixed web API , thats what i meaned, right?

[glassez]

so its cant be used even its avalible in code of 4.3.3 and we need to wait next release 4.3.4 with fixed web API , thats what i meaned, right?

No.
You can use it. But you can't tell if it's available based on the API version alone. The following situation is obtained:

1. qBittorrent v4.3.2 provides API v2.7 that has no such feature
2. qBittorrent v4.3.3 has this feature but API version is still 2.7 (still my apologies)

[masterwishx]

i didnt finded this option - rename folder (right mouse click) in binhex/arch-qbittorrentvpn based on 4.3.3 after updated from 4.3.2 docker yestuday.
Now i tried and SURPRISE -> this option avalible on the same Docker version that i tried yestuday... how it can be possible ?!?
Any way Thanks a lot for your hard and Amazing for work.
im glad that switched from uTorrent to qBittorrent Docker...

[glassez]

how it can be possible ?!?

Probably due to cached js scripts.

[masterwishx]

Ah OK,Thanks again