@cline/shared
A shared-module npm package of the Cline project that carries core common logic and type definitions for reuse by its editor plugin, command-line tool and other submodules.
Core Facts
@cline/shared is the shared module package of the Cline project, carrying core common logic and type definitions for reuse by submodules such as editor plugins and command-line tools.
Cline's shared package typically carries type definitions, utility functions, and protocol conventions reused across components
Timeline (last 90 days)
This @cline/shared 0.2.0 release information does not disclose specific API changes, new features, or breaking changes.
Publishing the shared package independently to a package registry (such as npm) means that external developers can import these shared logics like an ordinary dependency, without having to copy code or depend on the entire main repository.
The release page of @cline/shared 0.2.0 contains 2 asset files.
@cline/shared 0.2.0 was tagged by the github-actions automated pipeline at 03:33 on October 26, with the corresponding commit hash dab4823.
Projects depending on 0.x version packages cannot assume that minor version upgrades are backward compatible, and interface changes should be carefully checked when upgrading to 0.2.0.
For projects that depend on @cline/shared in production, thorough testing should be conducted before upgrading to 0.2.0.
The @cline/shared package added three functions, withHubLauncherIdentity, claimHubLauncherIdentity and readHubLauncherIdentity, and added a traces_exporter field to the telemetry self-check report.
Version 0.0.95 will not bring visible functional changes to end users who use the Cline product directly.
This tag was automatically created by github-actions on 17 Oct 02:59.
The content captured by this RSS fetch did not include a complete CHANGELOG or commit list, and only presented the tag creation time and the number of assets.
17 more timeline events
All Facts (20)
@cline/shared is the shared module package of the Cline project, carrying core common logic and type definitions for reuse by submodules such as editor plugins and command-line tools.
75%VerifiedCline's shared package typically carries type definitions, utility functions, and protocol conventions reused across components
75%UnverifiedFor projects that depend on @cline/shared in production, thorough testing should be conducted before upgrading to 0.2.0.
50%UnverifiedThis @cline/shared 0.2.0 release information does not disclose specific API changes, new features, or breaking changes.
50%UnverifiedPublishing the shared package independently to a package registry (such as npm) means that external developers can import these shared logics like an ordinary dependency, without having to copy code or depend on the entire main repository.
50%UnverifiedThe release page of @cline/shared 0.2.0 contains 2 asset files.
50%UnverifiedProjects depending on 0.x version packages cannot assume that minor version upgrades are backward compatible, and interface changes should be carefully checked when upgrading to 0.2.0.
50%UnverifiedThe @cline/shared package added three functions, withHubLauncherIdentity, claimHubLauncherIdentity and readHubLauncherIdentity, and added a traces_exporter field to the telemetry self-check report.
50%UnverifiedVersion 0.0.95 will not bring visible functional changes to end users who use the Cline product directly.
50%UnverifiedCline uses three-part 0.0.x version management, with the shared package decoupled from the main product version.
50%UnverifiedThe content captured by this RSS fetch did not include a complete CHANGELOG or commit list, and only presented the tag creation time and the number of assets.
50%UnverifiedFor production-environment integrators, it is recommended to manually compare the diff between adjacent tags before upgrading, rather than judging upgrade risk solely by version number.
50%UnverifiedA new buildTelemetrySelfcheckReport export has been added to @cline/shared.
50%UnverifiedIn 0.0.94, both the major and minor version numbers are 0, meaning the project makes almost no commitment to API stability.
50%UnverifiedThird-party developers can build tools relying only on @cline/shared without binding themselves to the complete Cline application implementation.
50%UnverifiedChanges to @cline/shared usually have a broader impact than a single subpackage, so the cost of upgrade verification is higher.
50%UnverifiedFor teams using 0.x version dependencies, it is recommended to pin specific versions and verify in a test environment before upgrading the production environment, while paying attention to release notes and commits marked as breaking change in the commit history.
50%Unverified@cline/shared is the shared dependency module of the Cline project.
50%UnverifiedFor @cline/shared in the 0.0.x stage, it is recommended to use exact version numbers in package.json rather than ^ or ~ range specifiers to prevent automatic upgrades from triggering compatibility issues
50%UnverifiedThe Release comes with 2 Assets (build artifacts).
50%