We have SSIS project with Target version

We need to use this target version if someone need to load some data or for develop packages. We are using VS 2017 with latest patches. If someone try to change some package of project and deploy only this package into SSISDB then next opening of project in VS will show that now target server version 2019. All developers use VS 2017 only (double checked this). Why target version changing to 2019 ? We can't run this with target version 2019 because few times saw such problems like not full loading of data despite on green mark check after package completion and this happenig only with target version 2019 , everything is good when we changing target version back to 2017 and running the same packages. But this is difficult to control everyone to change target server version back to 2017 every time when someone just need to make some minor changes to some of package of the project.

Here are versions of our services

Microsoft SQL Server 2017 (RTM-CU22-GDR) (KB4583457) - 14.0.3370.1 (X64) Nov 6 2020 18:19:52 Copyright (C) 2017 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2019 Datacenter 10.0 (Build 17763: ) (Hypervisor)

Integration Services 14.0

Visual Studio Proffessional 2017 15.9.46

Just step by step what i'm doing :

Open my project in Visual Studio 2017 and check target server version

It is not comfortable for us due to strange behavior of Visual Studio when loading some data

Then im changing Target Server Version and Visual Studio Starts to modify every of my packages inside this project ( to translate this to English it says "converting of packages in progress" )

Now project has target version 2017 ( and per picture above every package got some changes due this target version changing ) I deploy this back to SSISDB

I open this project again in visual studio ( load from SSISDB everything that i deployed earlier ) and see

Then I open any of packages and just do minor changing inside , save this to current opened project in VS ( target server version still 2017 )

Then I deploy package to SSISDB (exacly package not project ) and i'm sure that this package was made with target version 2017.

Then I open my project again from SSISDB and now I see