Updating r7 from 7.14.0

[Paebbels]

New Features

• CleanupArtifacts.yml gained condition and condition2. Two boolean inputs, defaulting to true, placed between each JSON dictionary and its id list:

  json → condition → artifact-json-ids	first set
  json2 → condition2 → artifact-json-ids2	second set

  Each is wired into the if: of both its compute and its delete step, so a disabled set neither resolves names nor deletes anything. Existing callers are unaffected — the default preserves today's behaviour.

Bug Fixes

• The package artifact could be deleted while PublishOnPyPI was using it. In CompletePipeline.yml, ArtifactCleanUp listed package_all in the unconditional set, while its needs: has # - PublishOnPyPI commented out — so on a release-tag run the cleanup and the upload ran concurrently, and the wheel could vanish from under the publish job.

  package_all now moves to the guarded second set:

        condition2: ${{ ! startsWith(github.ref, 'refs/tags') }}
        artifact-json-ids2: >-
          package_all

  which is the same guard ArtifactCleanUp.yml has always had. On a tagged run PublishOnPyPI consumes the artifact and deletes it itself.

  The window is real and measured — pyTooling v8.19.0 (run 30612877620): cleanup ran 07:34:28→07:34:40, publish started 07:34:58. That release survived only because pyTooling/pyTooling doesn't use CompletePipeline.yml; it calls the older ArtifactCleanUp.yml, whose guard kept pyTooling-Packages out of the deleted list.

• VersionCheck rejected every prefixed tag. Prepare.outputs.version is derived from the tag and may carry a v/r prefix, while extractVersionInformation(...).Version is a plain str that never does — so the string comparison could never succeed for a repository tagging vX.Y.Z:

  expected:  v0.38.0
  from code: 0.38.0
  ##[error]Expected version (v0.38.0) doesn't match the version in Python code (0.38.0).
  

  Hit by VHDL/pyVHDLModel v0.38.0 and pyTooling/sphinx-reports v0.11.2, and not workaroundable by a consumer. Both sides are now parsed with SemanticVersion, which ignores the prefix; a parse failure is reported as an error instead of crashing the step.

Changes

• ArtifactCleanUp.yml now emits a deprecation warning. A ::warning annotation plus a migration note in the job log: package → json2 + artifact-json-ids2 guarded by condition2; remaining → json + artifact-json-ids, or others for literal names. Slated for removal in r8.

  The message deliberately avoids literal ${{ }} braces — Actions substitutes those inside run: blocks before the shell sees them, so an example containing them would be evaluated rather than printed.

Unit Tests

• _Checking_CleanupArtifacts.yml moves package_all into the guarded second set, exercising condition2.
• _Checking_JobTemplates.yml already binds both sets to two different name dictionaries (UnitTestingParams and PlatformTestingParams), so there was no free slot. The package artifact gets its own PackageArtifactCleanUp job using condition, which exercises the first-set guard and removes the same race from that pipeline — it has a PublishOnPyPI job too.

Verification

Version comparison, checked on pyTooling 8.17.0 and 8.19.0 — both the cases that must pass and the cases that must still fail:

expected (from tag)	in code	equal	wanted
v0.11.2	0.11.2	✔	✔
v0.38.0	0.38.0	✔	✔
v8.19.0	8.19.0	✔	✔
r7.13.1	7.13.1	✔	✔
0.11.2	0.11.2	✔	✔
v0.11.2	0.11.1	✘	✘
v1.0.0	0.11.2	✘	✘

All five changed workflows parse as YAML with balanced ${{ }} expressions, and the deprecation script was executed to confirm its rendered output.

---

Related Issues and Pull-Requests

• Also in this release: Add application testing to job template verification and reduce matrices #238 — application testing in the job template verification, reduced matrices.
• Downstream reports: the VersionCheck failure blocked VHDL/pyVHDLModel#167 (v0.38.0) and pyTooling/sphinx-reports#99 (v0.11.2).

Note

The documentation is not updated in this release. CleanupArtifacts.yml has no documentation page at all — the documented ArtifactCleanup.rst covers the deprecated workflow — and the instantiation examples are still on @r6. Tracked separately; it needs a rework rather than a patch.

---

Related Issues and Pull-Requests

• v7.14.0 #240

[codacy-production]

Not up to standards ⛔

🟢 Coverage 100.00% diff coverage · +0.00% coverage variation

Metric	Results
Coverage variation	✅ +0.00% coverage variation
Diff coverage	✅ 100.00% diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (c9e2bb7)	45	41	91.11%
Head commit (473db0b)	45 (+0)	41 (+0)	91.11% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#241)	1	1	100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.22%. Comparing base (c9e2bb7) to head (473db0b).
⚠️ Report is 80 commits behind head on r7.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##               r7     #241   +/-   ##
=======================================
  Coverage   82.22%   82.22%           
=======================================
  Files           1        1           
  Lines          45       45           
  Branches        9        9           
=======================================
  Hits           37       37           
  Misses          4        4           
  Partials        4        4           

Flag	Coverage Δ
unittests	82.22% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.