(Pre-Publish Steps): update service package version to 2.3

[Blahpapto1]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

Pre-publish steps for releases/2.3.

Why should this Pull Request be merged?

Standard release procedure.

What testing has been done?

N/A - PR

[github-actions]

Test Results

    52 files  ±0      52 suites  ±0   1h 17m 48s ⏱️ + 1m 27s
   709 tests ±0     709 ✅ ±0      0 💤 ±0  0 ❌ ±0 
21 420 runs  ±0  20 344 ✅ ±0  1 076 💤 ±0  0 ❌ ±0 

Results for commit a679d06. ± Comparison against base commit 948e927.

♻️ This comment has been updated with latest results.

[Blahpapto1]

System Tests are failing because -

Because ni-measurement-plugin-sdk-generator depends on ni-measurement-plugin-sdk-service (^2.3.0) which doesn't match any versions, version solving failed.

For this, I can comment out the ni-measurement-plugin-sdk-service package to be used from ../... Will this be changed in the release branch once the packages are uploaded ? Post-publish steps ?

@bkeryan

Based on an earlier comment, it was not changed back after packages were published in releases/2.1 branch -

measurement-plugin-python/packages/generator/pyproject.toml

Line 40 in 8e8dfa8

ni-measurement-plugin-sdk-service = {path = "../../packages/service", develop = true}

[bkeryan]

System Tests are failing because -

Because ni-measurement-plugin-sdk-generator depends on ni-measurement-plugin-sdk-service (^2.3.0) which doesn't match any versions, version solving failed.

For this, I can comment out the ni-measurement-plugin-sdk-service package to be used from ../... Will this be changed in the release branch once the packages are uploaded ? Post-publish steps ?

@bkeryan

Based on an earlier comment, it was not changed back after packages were published in releases/2.1 branch -

measurement-plugin-python/packages/generator/pyproject.toml

Line 40 in 8e8dfa8

ni-measurement-plugin-sdk-service = {path = "../../packages/service", develop = true}

I added a note to the wiki page clarifying this:

[!NOTE] The reason we comment out the file dependencies is so that the examples in the distribution .zip file work without the rest of the Git repo. Do not comment out the file dependencies for projects in packages/ because this reason does not apply to them and their build/test workflow requires file dependencies.