Skip to content

YLPlugin v0.1.3 — experimental

Latest

Choose a tag to compare

@github-actions github-actions released this 10 Nov 22:45

YLPlugin v0.1.3 — direct metadata discovery and bundled CLI

Publication status: GitHub, PyPI and Maven Central are published. npm 0.1.3 is
awaiting corrected token write permissions; its public latest remains 0.1.2.
The npm 0.1.3 install command below becomes available after that upload succeeds.
See the publication record.

Read public YLSpec metadata without scanning a plugin's index or payload, and
install the native core and command together through supported language packages.

Direct metadata discovery

  • New standalone C/C++ operations read only the 128-byte header and embedded
    YLSpec frame. They do not construct a Package or read TOC, payload or signature bytes.
  • Python exposes Library.read_metadata and a custom exact-range reader;
    JS/TS exposes readMetadata; Java/Kotlin exposes equivalent native operations.
  • ylplugin metadata FILE emits canonical TOML. --json labels discovery scope
    metadata-only and integrity UNVERIFIED.
  • Limits, malformed framing, corrupt-index independence and virtual 5 GiB range
    reads have regression coverage. Metadata discovery does not authenticate a publisher.

Install the core and CLI together

python -m pip install ylplugin==0.1.3
ylplugin --version
python -m ylplugin --help

npm install @younglionorganization/ylplugin@0.1.3
npx ylplugin --help

Python platform wheels contain the matching native runtime and executable;
pip registers ylplugin in the active environment's scripts directory. npm
registers its bin command and bundles the native executable. Java/Kotlin resolve
the native JAR transitively and can invoke xyz.younglion.ylplugin.Cli without
modifying the system PATH. No import-time core download is required.

Published native targets: Linux x86_64/ARM64, macOS x86_64/ARM64, Windows x86_64.
Python 3.11+, Node 20+ and JVM 11+ remain the language baselines. GNU Linux wheels
use the manylinux_2_39 policy. Use matching SDK/native versions.

The universal wheel among GitHub's source-release assets is facade-only;
use PyPI platform wheels for automatic core/CLI installation. Unsupported platforms
and source checkouts require an explicit native build.

Correctness and performance

  • Plaintext store validation streams the complete resource hash with at most
    1 MiB scratch instead of materializing the whole resource. Integrity checks
    still cover every byte on each call.
  • Slice cancellation covers empty resources and the final reader callback.
  • Node rejects lone UTF-16 surrogates before converting filesystem paths.
  • Windows CLI arguments and core diagnostics preserve valid Unicode paths.
  • VERSION changes automatically invalidate incremental CMake configuration.
  • PyPI description, author/maintainer metadata, classifiers, keywords and project
    links are expanded. SDK/CLI install tests exercise the actual built packages.

The recorded 32 MiB Linux comparison measured lower latency and peak process RSS;
see performance evidence and scope.
No universal speedup is claimed. Encrypted/compressed validation keeps its existing path.

Documentation and next milestone

The English Wiki, installation/API guides, CLI reference, troubleshooting and
roadmap now distinguish implemented metadata-only discovery from planned
presentation assets. Automatic icon/README/license/security discovery and
selective document reads are not implemented in 0.1.3. Track that work in the
roadmap.

Container/profile 1.0, C ABI version 1, permission semantics and LGPL-3.0-only
licensing remain unchanged. New C entry points are additive; no stable 1.x C++
ABI or production security audit is claimed. Signature verification and host
preflight remain separate from metadata inspection.

Verified release build

Commit: 584ceb1c2e8cb1336eeb0c3a69259ee15d82a688

All 7 CI jobs passed. Linux x86_64/ARM64, Windows, macOS, sanitizer, fuzz and packaging jobs succeeded. Native execution tests are intentionally skipped on Windows/macOS. See the workflow for precise results and the release manifest for asset hashes.