semantic-version-parsing-comparison
License: restricted — no clear open-source license detected for the underlying tool; verify licensing before commercial use or redistribution.
Summary
Parse and compare software package version strings against minimum semantic versioning requirements to validate pipeline dependencies before execution. This skill ensures that all critical packages meet or exceed specified thresholds, preventing downstream failures caused by incompatible or outdated libraries.
When to use
Before executing a bioinformatics pipeline that depends on multiple R packages with strict version constraints (e.g., DaDIA, which requires R ≥4.0, XCMS ≥3.11.4, and metaMS =1.25.1). Apply this skill when you need to programmatically validate environment readiness rather than relying on manual checks or runtime errors.
When NOT to use
- Input is a conda/pip lock file or container image manifest — use dedicated dependency managers instead.
- Packages are version-agnostic or have no documented minimum requirements.
- Runtime version mismatches are acceptable (e.g., for exploratory or backward-compatible workflows).
Inputs
- R environment with loaded packages (R, XCMS, metaMS)
- Minimum version specification document (e.g., README or configuration file)
Outputs
- Structured validation report (JSON or text format) with per-dependency pass/fail status
- Overall pipeline-ready boolean flag
- Semantic version tuples (major, minor, patch) for each dependency
How to apply
Extract the installed version string from each required package using language-specific introspection (e.g., version$major and version$minor in R, or packageVersion() for packages). Parse version strings using semantic versioning rules (major.minor.patch), then compare each parsed version against the documented minimum requirement using tuple comparison (e.g., (4, 0, 0) ≥ (3, 11, 4)). For packages with exact version pins (e.g., metaMS 1.25.1), flag any mismatch as a validation failure. Aggregate results into a structured report (JSON or text) with pass/fail status for each dependency and an overall pipeline-ready boolean flag. Reject pipeline execution if any critical dependency fails validation.
Related tools
- R (Runtime environment; provides version introspection via version$major and version$minor; host for package version extraction)
- XCMS (Mass spectrometry data processing package; requires Development Version ≥3.11.4 for DaDIA compatibility) — github.com/HuanLab/DaDIA
- metaMS (Metabolomics peak annotation package; requires exact or compatible version match to 1.25.1) — github.com/HuanLab/DaDIA
Examples
# R command to validate DaDIA dependencies
if(as.numeric(R.version$major) >= 4 && packageVersion('XCMS') >= '3.11.4' && packageVersion('metaMS') == '1.25.1') { pipeline_ready <- TRUE } else { stop('Dependency validation failed') }
Evaluation signals
- All parsed version tuples satisfy their respective minimum/exact requirements without raising exceptions.
- Overall pipeline-ready flag is TRUE only when all three dependencies (R, XCMS, metaMS) pass validation.
- Version comparison logic correctly handles semantic versioning rules (e.g., 3.11.4 > 3.9.0 even though string '3.9.0' > '3.11.4' lexically).
- Validation report is generated in valid JSON (if format selected) and includes timestamp and environment metadata.
- Pipeline execution is blocked or warned if any dependency fails, with clear messaging indicating which package and threshold were violated.
Limitations
- Exact version pins (e.g., metaMS 1.25.1) do not account for compatible patch releases or maintenance updates; may reject valid installations.
- Version strings with non-standard formats (e.g., 'devel', 'nightly', Git commit hashes) may not parse correctly using simple semantic versioning rules.
- Does not validate transitive dependencies (e.g., XCMS's own R package dependencies); only checks direct requirements.
- Assumes all packages are available in the current R library path; does not verify package installation completeness.
Evidence
- [intro] DaDIA requires R Version 4.0 or above, XCMS Development Version 3.11.4 or above, and metaMS Version 1.25.1, with all other packages updated to the newest available version.: "DaDIA requires R Version 4.0 or above, XCMS Development Version 3.11.4 or above, and metaMS Version 1.25.1, with all other packages updated to the newest available version."
- [other] Query the installed R version using version$major and version$minor; verify that the major version is ≥4 and reject execution if not.: "Query the installed R version using version$major and version$minor; verify that the major version is ≥4 and reject execution if not."
- [other] Load the XCMS package and extract its version string; parse and compare against the minimum requirement (≥3.11.4) using semantic versioning rules; fail if below threshold.: "Load the XCMS package and extract its version string; parse and compare against the minimum requirement (≥3.11.4) using semantic versioning rules; fail if below threshold."
- [other] Generate a structured validation report (JSON or text format) summarizing all three version checks with pass/fail status for each dependency and an overall pipeline-ready boolean flag.: "Generate a structured validation report (JSON or text format) summarizing all three version checks with pass/fail status for each dependency and an overall pipeline-ready boolean flag."
- [readme] R Version 4.0 or above, XCMS Development Version 3.11.4 or above, and metaMS Version 1.25.1 are required; all other packages should be updated to the newest available version.: "R Version 4.0 or above, XCMS Development Version 3.11.4 or above, and metaMS Version 1.25.1 are required; all other packages should be updated to the newest available version."
1---2name: semantic-version-parsing-comparison3description: Use when before executing a bioinformatics pipeline that depends on multiple R packages with strict version constraints (e.g., DaDIA, which requires R ≥4.0, XCMS ≥3.11.4, and metaMS =1.25.1).4license: CC-BY-4.05---67# semantic-version-parsing-comparison89> **License: restricted** — no clear open-source license detected for the underlying tool; verify licensing before commercial use or redistribution. <!-- asb-license-banner -->10## Summary1112Parse and compare software package version strings against minimum semantic versioning requirements to validate pipeline dependencies before execution. This skill ensures that all critical packages meet or exceed specified thresholds, preventing downstream failures caused by incompatible or outdated libraries.1314## When to use1516Before executing a bioinformatics pipeline that depends on multiple R packages with strict version constraints (e.g., DaDIA, which requires R ≥4.0, XCMS ≥3.11.4, and metaMS =1.25.1). Apply this skill when you need to programmatically validate environment readiness rather than relying on manual checks or runtime errors.1718## When NOT to use1920- Input is a conda/pip lock file or container image manifest — use dedicated dependency managers instead.21- Packages are version-agnostic or have no documented minimum requirements.22- Runtime version mismatches are acceptable (e.g., for exploratory or backward-compatible workflows).2324## Inputs2526- R environment with loaded packages (R, XCMS, metaMS)27- Minimum version specification document (e.g., README or configuration file)2829## Outputs3031- Structured validation report (JSON or text format) with per-dependency pass/fail status32- Overall pipeline-ready boolean flag33- Semantic version tuples (major, minor, patch) for each dependency3435## How to apply3637Extract the installed version string from each required package using language-specific introspection (e.g., `version$major` and `version$minor` in R, or `packageVersion()` for packages). Parse version strings using semantic versioning rules (major.minor.patch), then compare each parsed version against the documented minimum requirement using tuple comparison (e.g., (4, 0, 0) ≥ (3, 11, 4)). For packages with exact version pins (e.g., metaMS 1.25.1), flag any mismatch as a validation failure. Aggregate results into a structured report (JSON or text) with pass/fail status for each dependency and an overall pipeline-ready boolean flag. Reject pipeline execution if any critical dependency fails validation.3839## Related tools4041- **R** (Runtime environment; provides version introspection via version$major and version$minor; host for package version extraction)42- **XCMS** (Mass spectrometry data processing package; requires Development Version ≥3.11.4 for DaDIA compatibility) — github.com/HuanLab/DaDIA43- **metaMS** (Metabolomics peak annotation package; requires exact or compatible version match to 1.25.1) — github.com/HuanLab/DaDIA4445## Examples4647```48# R command to validate DaDIA dependencies49if(as.numeric(R.version$major) >= 4 && packageVersion('XCMS') >= '3.11.4' && packageVersion('metaMS') == '1.25.1') { pipeline_ready <- TRUE } else { stop('Dependency validation failed') }50```5152## Evaluation signals5354- All parsed version tuples satisfy their respective minimum/exact requirements without raising exceptions.55- Overall pipeline-ready flag is TRUE only when all three dependencies (R, XCMS, metaMS) pass validation.56- Version comparison logic correctly handles semantic versioning rules (e.g., 3.11.4 > 3.9.0 even though string '3.9.0' > '3.11.4' lexically).57- Validation report is generated in valid JSON (if format selected) and includes timestamp and environment metadata.58- Pipeline execution is blocked or warned if any dependency fails, with clear messaging indicating which package and threshold were violated.5960## Limitations6162- Exact version pins (e.g., metaMS 1.25.1) do not account for compatible patch releases or maintenance updates; may reject valid installations.63- Version strings with non-standard formats (e.g., 'devel', 'nightly', Git commit hashes) may not parse correctly using simple semantic versioning rules.64- Does not validate transitive dependencies (e.g., XCMS's own R package dependencies); only checks direct requirements.65- Assumes all packages are available in the current R library path; does not verify package installation completeness.6667## Evidence6869- [intro] DaDIA requires R Version 4.0 or above, XCMS Development Version 3.11.4 or above, and metaMS Version 1.25.1, with all other packages updated to the newest available version.: "DaDIA requires R Version 4.0 or above, XCMS Development Version 3.11.4 or above, and metaMS Version 1.25.1, with all other packages updated to the newest available version."70- [other] Query the installed R version using version$major and version$minor; verify that the major version is ≥4 and reject execution if not.: "Query the installed R version using version$major and version$minor; verify that the major version is ≥4 and reject execution if not."71- [other] Load the XCMS package and extract its version string; parse and compare against the minimum requirement (≥3.11.4) using semantic versioning rules; fail if below threshold.: "Load the XCMS package and extract its version string; parse and compare against the minimum requirement (≥3.11.4) using semantic versioning rules; fail if below threshold."72- [other] Generate a structured validation report (JSON or text format) summarizing all three version checks with pass/fail status for each dependency and an overall pipeline-ready boolean flag.: "Generate a structured validation report (JSON or text format) summarizing all three version checks with pass/fail status for each dependency and an overall pipeline-ready boolean flag."73- [readme] R Version 4.0 or above, XCMS Development Version 3.11.4 or above, and metaMS Version 1.25.1 are required; all other packages should be updated to the newest available version.: "R Version 4.0 or above, XCMS Development Version 3.11.4 or above, and metaMS Version 1.25.1 are required; all other packages should be updated to the newest available version."
HolobiomicsLab