satellite.psd1
|
@{ RootModule = 'satellite.psm1' ModuleVersion = '0.3.2' GUID = 'b2c3d4e5-f6a7-8901-bcde-f12345678901' Author = 'Delta-Code Team' CompanyName = 'DeltaCode' Copyright = '(c) 2026 DeltaCode. All rights reserved.' Description = 'Satellite module for Delta-Code - discovery, registration, validation, execution of extension satellites. Requires the delta-code module.' PowerShellVersion = '5.1' FunctionsToExport = @( 'Get-DeltaCodeSatellite' 'Get-DeltaCodeSatellites' 'Register-DeltaCodeSatellite' 'Test-DeltaCodeSatellite' 'Invoke-DeltaCodeSatellite' 'Initialize-DeltaCodeSatellites' 'Unregister-DeltaCodeSatellite' 'Reset-DeltaCodeSatelliteRegistry' ) PrivateData = @{ PSData = @{ ProjectUri = 'https://github.com/suniltnngl-gm/delta-code' LicenseUri = 'https://github.com/suniltnngl-gm/delta-code/blob/master/LICENSE' ReleaseNotes = 'Initial release: diff engine, satellites, workspaces, workflows, automation profiles and the health command. Validated on Windows PowerShell 5.1 and PowerShell 7.x.' } } # Injected at publish time. A Gallery consumer installing this package on # its own must also receive the modules it imports. The source manifests # omit this on purpose: the repo and flat-install layouts resolve the same # dependencies by sibling path or by name. ## Plain names, deliberately not @{ ModuleName = ...; ModuleVersion = ... }. ## Windows PowerShell 5.1 reads the hashtable form far more strictly than ## PowerShell 7: when one module requires both a module and that module's own ## dependency, 5.1 rejects it at manifest load with "points to a cyclic ## dependency", even though the graph is acyclic. `entry` requires both ## `workspace` and `satellite`, so every 5.1 consumer of `entry` failed to ## import. The name form loads the same graph on both engines; the cost is ## that the dependency version is not pinned. RequiredModules = @( 'delta-code' ) } |