Skip to content

v0.3.0: testing and generalized dependency intelligence #595

Description

@leynos

Goal

Track the Netsuke v0.3.0 feature set, centred on first-class Netsukefile testing and a broader dependency model.

Release scope

Release intent

v0.3.0 should make Netsuke substantially better at answering two questions before or without blindly executing a build:

  1. Does this Netsukefile behave as intended? The test framework provides hermetic, declarative verification of manifest logic through the production compiler pipeline.
  2. What does this work actually depend on? External dependency importers and non-file providers broaden the graph beyond hand-authored local file edges.

The three strands should share compiler/IR infrastructure where it is genuinely common, but they should not be collapsed into one abstraction. Test doubles model controlled observations; importers consume dependency knowledge; providers define dependency identity and freshness.

Acceptance criteria

  • All three tracked capability areas have usable documented surfaces by v0.3.0 final.
  • Their IR/compiler boundaries compose rather than bypass one another.
  • Structured output, non-interactive behaviour, localization, and diagnostics follow the canonical CLI contracts established by v0.2.0.
  • Security and reproducibility boundaries are explicit for external tool invocation and network-backed dependencies.
  • Netsuke dogfoods the testing framework and representative dependency import/provider cases before release.
  • Full repository quality and release gates pass on the exact release commit.

Deferred

A broader semantic Netsukefile linter is targeted at v0.4.0 in #592, where it can consume the structured recipes, change-detection data, test semantics, and richer dependency graph delivered by earlier releases.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    RoadmapA pull request originating from a roadmap itemdocumentationImprovements or additions to documentationenhancementNew feature or requesttestingTest coverage, test infrastructure, and verification tooling work.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions