fix: add version string checking

[JeffreyDallas]

Description

This pull request changes the following:

• Check for releaseTag version
• Show user message instead of throw error if cluster-ref connect is called twice

Related Issues

• Closes bug: for the release tag, if the user passes in a semantically correct version without the v prefix, it fails #2310
• Closes bug: cluster-ref connect should be idempotent #2311

Pull request (PR) checklist

• This PR added tests (unit, integration, and/or end-to-end)
• This PR updated documentation
• This PR added no TODOs or commented out code
• This PR has no breaking changes
• Any technical debt has been documented as a separate issue and linked to this PR
• Any package.json changes have been explained to and approved by a repository manager
• All related issues have been linked to this PR
• All changes in this PR are included in the description
• When this PR merges the commits will be squashed and the title will be used as the commit message, the 'commit message guidelines' below have been followed

Testing

• This PR added unit tests
• This PR added integration/end-to-end tests
• These changes required manual testing that is documented below
• Anything not tested is documented

The following manual testing was done:

• TBD

The following was not tested:

• TBD

Commit message guidelines

We use 'Conventional Commits' to ensure that our commit messages are easy to read, follow a consistent format, and for automated release note generation. Please follow the guidelines below when writing your commit messages:

1. BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type. NOTE: currently breaking changes will only bump the MAJOR version.
2. The title is prefixed with one of the following:

Prefix	Description	Semantic Version Update	Captured in Release Notes
feat:	a new feature	MINOR	Yes
fix:	a bug fix	PATCH	Yes
perf:	performance	PATCH	Yes
refactor:	code change that isn't feature or fix	none	No
test:	adding missing tests	none	No
docs:	changes to documentation	none	Yes
build:	changes to build process	none	No
ci:	changes to CI configuration	none	No
style:	formatting, missing semi-colons, etc	none	No
chore:	updating grunt tasks etc; no production code change	none	No

[Copilot]

Pull Request Overview

This pull request adds version string validation to ensure release tags are valid semantic versions. The changes focus on improving input validation and error handling for version strings used in the deployment process.

• Adds semver validation for release tags to prevent invalid version strings from being processed
• Automatically prefixes version strings with 'v' if not already present
• Includes a minor code style fix for quote consistency

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
src/commands/relay.ts	Minor quote style fix from backticks to single quotes
src/commands/node/tasks.ts	Adds version validation and automatic 'v' prefix for release tags
src/commands/node/configs.ts	Adds semver validation check for release tags

[github-actions]

Unit Test Results - Linux

32 tests  ±0   32 ✅ ±0   0s ⏱️ ±0s
16 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit fc7e0fe. ± Comparison against base commit 1e4484e.

♻️ This comment has been updated with latest results.

[github-actions]

Unit Test Results - Windows

  1 files  ±0  175 suites  ±0   2s ⏱️ ±0s
492 tests ±0  492 ✅ ±0  0 💤 ±0  0 ❌ ±0 
496 runs  ±0  496 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit fc7e0fe. ± Comparison against base commit 1e4484e.

♻️ This comment has been updated with latest results.

[github-actions]

E2E Test Report

 19 files  ±0  135 suites  ±0   1h 54m 43s ⏱️ + 1m 41s
360 tests  - 1  360 ✅  - 1  0 💤 ±0  0 ❌ ±0 
373 runs   - 1  373 ✅  - 1  0 💤 ±0  0 ❌ ±0 

Results for commit b8026a3. ± Comparison against base commit dac31bb.

This pull request removes 1 test.

cluster-ref connect should fail with cluster ref that already exists ‑ ClusterCommand cluster-ref connect should fail with cluster ref that already exists

[github-actions]

E2E Test Report

 20 files  + 1  138 suites  +5   2h 9m 32s ⏱️ - 7m 24s
377 tests +13  377 ✅ +14  0 💤 ±0  0 ❌  - 1 
390 runs  +13  390 ✅ +14  0 💤 ±0  0 ❌  - 1 

Results for commit fc7e0fe. ± Comparison against base commit 1e4484e.

This pull request removes 1 and adds 14 tests. Note that renamed tests count towards both.

cluster-ref connect should fail with cluster ref that already exists ‑ ClusterCommand cluster-ref connect should fail with cluster ref that already exists

Enable Envoy proxy port forwarding and create client from network config should succeed ‑ E2E Test Suite for 'account-cmd-e2e' account-cmd-e2e AccountCommand Test SDK create account and submit transaction Enable Envoy proxy port forwarding and create client from network config should succeed
Should be able to use the getSingleBlock Method to validate block node connectivity ‑ E2E Test Suite for 'block-node-cmd-e2e' block-node-cmd-e2e BlockNodeCommand Should be able to use the getSingleBlock Method to validate block node connectivity
Should fail with versions less than v0.62.3 ‑ E2E Test Suite for 'block-node-cmd-e2e' block-node-cmd-e2e BlockNodeCommand Should fail with versions less than v0.62.3
Should succeed deploying block node with 'add' command ‑ E2E Test Suite for 'block-node-cmd-e2e' block-node-cmd-e2e BlockNodeCommand Should succeed deploying block node with 'add' command
Should succeed with removing block node with 'destroy' command ‑ E2E Test Suite for 'block-node-cmd-e2e' block-node-cmd-e2e BlockNodeCommand Should succeed with removing block node with 'destroy' command
generate key files ‑ E2E Test Suite for 'block-node-cmd-e2e' Bootstrap network for test [release v0.62.3] generate key files
node log command should work ‑ E2E Test Suite for 'block-node-cmd-e2e' block-node-cmd-e2e BlockNodeCommand node log command should work
should cleanup previous deployment ‑ E2E Test Suite for 'block-node-cmd-e2e' Bootstrap network for test [release v0.62.3] should cleanup previous deployment
should succeed with 'deployment add-cluster' ‑ E2E Test Suite for 'block-node-cmd-e2e' Bootstrap network for test [release v0.62.3] should succeed with 'deployment add-cluster'
should succeed with deployment create ‑ E2E Test Suite for 'block-node-cmd-e2e' Bootstrap network for test [release v0.62.3] should succeed with deployment create
…

♻️ This comment has been updated with latest results.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +1.29% (target: -1.00%)	✅ 79.38%

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (1e4484e)	40861	34202	83.70%
Head commit (fc7e0fe)	40938 (+77)	34796 (+594)	85.00% (+1.29%)

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 (#2314)	97	77	79.38%

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%

See your quality gate settings    Change summary preferences

[jeromy-cannon]

we need to ensure that anytime a version is passed in by the user, that we either add or remove the 'v' as needed based on whether it is needed for a helm chart, image, or consensus node version.

I only see the CN version check. But, I expected to see a check for passing in the helm chart versions or docker image as well

[swirlds-automation]

🎉 This PR is included in version 0.42.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀