Wrong error code in both operations in version v0.2

[fernandopradocabrillo]

Problem description
There is a typo in the test plan for both operations where the indicated error is not present in the API spec.

Test @check_device_swap_8_NoDeviceSwapPhoneNumberNeverConnected -> Indicates 422 NOT_SUPPORTED.
Test @retrieve_device_swap_date_5_not_activated -> Indicates 422 NOT_SUPPORTED.

In versión v1.0.0 is already solved but for Spring25 is still unresolved and should be fixed so GSMA can based their tests in a valid test plan.

Expected action

Fixed the issue and creatye a patch release for the Spring25 version

[bigludo7]

Hello Fernando
I'm not sure to get it :)
We have to craft a new release from r2.2 & removing here these 2 test cases as not relevant. And then we release a r2.3?

I'm afraid to be enough expert on GitHub to do it... could you manage this?

[hdamker]

Hi @fernandopradocabrillo, @tanjadegroot mentioned in the ReleaseManagement call that you are planning a maintenance release of r2.3 with v0.2.1 of device-swap and she asked me to have a look.

My observations:

• the branch maintenance-r2 branch is set up correctly for the previous manual release process (under which r2.2 was created), branched from the release tag.
• an automated release is not possible for two reasons: the Release Automation does not yet support maintenance branches and if it would, the validation goes only back to Fall25 Commonalities, not earlier (r2.2 is Spring25)

The general question is if we want to support initial versions (here 0.2.0) still with maintenance releases if already a stable version is available for more than half a year (Fall25 release with v1.0.0 which includes the fix).

If the team decides to do the maintenance release it should be possible on the maintenance branch with reasonable manual effort.

[hdamker]

@fernandopradocabrillo As #91 is closed I suggest that this issue should be "Close as not planned"?