@lunarisdigitalsolutions/lunapack 1.2.0 → 1.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +266 -0
- package/package.json +8 -7
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,266 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
This file records externally observable changes for Luna CLI consumers. Exclude
|
|
4
|
+
pack-package, documentation, CI, build, test, and release-process changes.
|
|
5
|
+
|
|
6
|
+
## Unreleased
|
|
7
|
+
|
|
8
|
+
Update this section before creating a release tag.
|
|
9
|
+
|
|
10
|
+
## Version 1.3.0 - 2026-08-31
|
|
11
|
+
|
|
12
|
+
### Completions
|
|
13
|
+
|
|
14
|
+
- `luna completions script` now generates native Bash, Fish, Nushell,
|
|
15
|
+
PowerShell, and Zsh Tab-completion registration without an external tool.
|
|
16
|
+
Pass `--install` to preview and append registration to the shell's user
|
|
17
|
+
configuration after an explicit confirmation that defaults to No.
|
|
18
|
+
Completion includes commands, options, valid finite values, available and
|
|
19
|
+
installed pack or link IDs, and configured source, link, and variable IDs.
|
|
20
|
+
- Shell completion now handles cursor positions beyond a shell's rendered
|
|
21
|
+
command line when trailing whitespace was stripped. Argument-taking commands
|
|
22
|
+
return value candidates, while command containers return no candidates.
|
|
23
|
+
- Nushell completion installation now uses `XDG_DATA_HOME` when configured and
|
|
24
|
+
the native macOS application data directory by default.
|
|
25
|
+
|
|
26
|
+
### Changed
|
|
27
|
+
|
|
28
|
+
- `luna install --save-remap` now stores mappings on the installed pack's
|
|
29
|
+
`lunapack.yml` entry. Locked effective targets override pack remapping; pack
|
|
30
|
+
remapping overrides top-level project remapping.
|
|
31
|
+
- Install, update, and their dry runs now identify whether each reported
|
|
32
|
+
managed-target remapping came from command-line input, pack configuration,
|
|
33
|
+
top-level project configuration, or `lunapack-lock.yml`.
|
|
34
|
+
|
|
35
|
+
- Install and update dry runs now group source, managed-file, and lifecycle
|
|
36
|
+
actions under labeled sections with colored action prefixes. Successful
|
|
37
|
+
installs and updates list managed-file changes by default; use
|
|
38
|
+
`--no-file-change-output` to suppress that list.
|
|
39
|
+
- Install and update dry runs no longer list locked source identities under
|
|
40
|
+
lifecycle actions.
|
|
41
|
+
- CLI status and dry-run actions now use distinct ASCII markers for consistent
|
|
42
|
+
terminal rendering without relying on color to identify file operations.
|
|
43
|
+
Lifecycle dry runs group hook details by phase and report whether policy,
|
|
44
|
+
command arguments, persisted trust, or confirmation controls script consent.
|
|
45
|
+
|
|
46
|
+
## Version 1.2.0 - 2026-08-29
|
|
47
|
+
|
|
48
|
+
### Added
|
|
49
|
+
|
|
50
|
+
- Added persistent blanket lifecycle-script denial for portable project,
|
|
51
|
+
project-local user, and global-user scopes. Denial overrides `--scripts run`
|
|
52
|
+
and retained source or pack grants, reports every denying scope before
|
|
53
|
+
lifecycle work, and appears as `policy-denied` in dry runs. Trust commands can
|
|
54
|
+
list, set, and confirm reset of denial without deleting grants.
|
|
55
|
+
- `luna init` and `luna pack init` now generate minimal schema-valid YAML with
|
|
56
|
+
only required properties and values.
|
|
57
|
+
- `luna mv` now moves managed directories as atomic batches while preserving
|
|
58
|
+
descendant paths. `--save-remap` records file or directory moves as reusable
|
|
59
|
+
project mappings for future installs.
|
|
60
|
+
- `luna install --save-remap` now persists command-line file and directory
|
|
61
|
+
remappings after a successful pack or link installation.
|
|
62
|
+
- Managed-target remappings now accept `@ignore` to omit matching pack or link
|
|
63
|
+
files from installation, updates, and lock ownership. Newly ignored existing
|
|
64
|
+
files remain unchanged, and removing the mapping allows omitted files to be
|
|
65
|
+
installed later.
|
|
66
|
+
|
|
67
|
+
### Fixed
|
|
68
|
+
|
|
69
|
+
- External-source identifier conflicts can now be canceled by submitting the
|
|
70
|
+
empty value offered by the interactive prompt.
|
|
71
|
+
- Managed files expanded from pack directory and glob selectors now honor exact
|
|
72
|
+
file remappings from project configuration and install command options.
|
|
73
|
+
- Project remappings with trailing `/` or `\\` separators now match declared
|
|
74
|
+
targets and persist effective targets without trailing separators.
|
|
75
|
+
|
|
76
|
+
### Parameters
|
|
77
|
+
|
|
78
|
+
- Enum parameters can set `multiple: true` and resolve ordered, unique
|
|
79
|
+
selections from repeated CLI input, prompts, array defaults, project
|
|
80
|
+
variables, and composite bindings.
|
|
81
|
+
- Managed-file conditions support `"docker" in features`; Scriban templates,
|
|
82
|
+
lifecycle instructions, and script arguments support `features contains
|
|
83
|
+
"docker"`. Invalid, duplicate, or incompatible selections fail before
|
|
84
|
+
project mutation.
|
|
85
|
+
|
|
86
|
+
### Pack Templates
|
|
87
|
+
|
|
88
|
+
- Managed-file Scriban templates can use `files.path` to resolve a declared
|
|
89
|
+
managed target after consumer remapping and `files.relative_path` to render a
|
|
90
|
+
path relative to the current effective target. Paths use `/` on every platform.
|
|
91
|
+
- Missing, conditionally excluded, or ambiguous managed-file references warn and
|
|
92
|
+
preserve the supplied declared target during install, update, and dry-run.
|
|
93
|
+
|
|
94
|
+
## Version 1.1.0 - 2026-08-27
|
|
95
|
+
|
|
96
|
+
### Luna Links
|
|
97
|
+
|
|
98
|
+
- Luna `1.1.0` adds project-owned links that select exact files, directories,
|
|
99
|
+
and globs from configured local or Git sources without requiring `pack.yml`.
|
|
100
|
+
- `luna search <query>` now includes matching configured links with their
|
|
101
|
+
source, target, and installation status.
|
|
102
|
+
- `luna links add`, `list`, `show`, and `rm` manage link definitions. Install,
|
|
103
|
+
update, outdated, audit, uninstall, and forced removal use lock-backed
|
|
104
|
+
ownership, content digests, conflict checks, and transaction rollback.
|
|
105
|
+
- Link installation now honors `--remap-directory` and `--remap-file`, recording
|
|
106
|
+
declared and effective target paths in lock ownership.
|
|
107
|
+
- Git links resolve immutable commits, materialize only selected blobs, and use
|
|
108
|
+
a verified user cache. Project and lock files containing links require Luna
|
|
109
|
+
`1.1.0` or later; version-1 files without links remain compatible.
|
|
110
|
+
|
|
111
|
+
### Pack Authoring
|
|
112
|
+
|
|
113
|
+
- New `luna pack` commands initialize, inspect, validate, and incrementally
|
|
114
|
+
maintain managed content, composite references, ordered lifecycle hooks,
|
|
115
|
+
parameters, tags, and metadata in local `pack.yml`.
|
|
116
|
+
- `luna pack add hook`, `luna pack hooks`, and positioned `luna pack rm hook`
|
|
117
|
+
replace the former script-specific authoring commands. Hook lists and resolved
|
|
118
|
+
pack inspection now show ordered script and instruction details.
|
|
119
|
+
- Pack manifests require ID, semantic version, non-empty author, and non-empty
|
|
120
|
+
license. `luna pack init` accepts `--author` and `--license`, prompting for
|
|
121
|
+
missing values interactively. Discovery and search exclude manifests missing
|
|
122
|
+
either attribution value.
|
|
123
|
+
- Pack manifests support optional non-empty `name` and absolute HTTP or HTTPS
|
|
124
|
+
`homepage` metadata.
|
|
125
|
+
|
|
126
|
+
### CLI Workflow
|
|
127
|
+
|
|
128
|
+
- Packs can declare external Git source aliases and select files, directories,
|
|
129
|
+
or globs from immutable commits. Install and update reuse equivalent workspace
|
|
130
|
+
sources, request graph-wide consent for missing sources, support
|
|
131
|
+
`--accept-sources`, and commit source configuration, managed files, and lock
|
|
132
|
+
provenance transactionally. Dry runs, outdated checks, audit, update, and
|
|
133
|
+
uninstall now report or preserve external-source mappings and ownership.
|
|
134
|
+
- `luna sources rm <name>` is the canonical, concise configuration-removal
|
|
135
|
+
command, with `remove` retained as a compatibility alias; it now refuses to
|
|
136
|
+
remove a source still used by an installed pack or its external content,
|
|
137
|
+
and otherwise clears source configuration and bound project trust while
|
|
138
|
+
retaining installed pack state, provenance, and managed files.
|
|
139
|
+
- `luna sources add git` and `luna sources add github` resolve a supplied
|
|
140
|
+
short branch or tag name to its complete ref through `git ls-remote`,
|
|
141
|
+
reject an ambiguous short name, and reject a repository that canonicalizes
|
|
142
|
+
to an already-configured source under a different name, URL form, or
|
|
143
|
+
casing.
|
|
144
|
+
- `luna sources add github` now requires `--ref`.
|
|
145
|
+
- `luna sources rename <current-id> <new-id>` renames a configured source and
|
|
146
|
+
atomically updates its bound trust and lock-file references.
|
|
147
|
+
- Running `luna` without a subcommand displays command help, summarizes
|
|
148
|
+
workspace maturity, and recommends the next setup, catalog, or lifecycle
|
|
149
|
+
commands.
|
|
150
|
+
- Successful core commands and recoverable missing-prerequisite or pack lookup
|
|
151
|
+
failures now include up to three contextual command recommendations.
|
|
152
|
+
- `luna --suppress-next-steps` suppresses contextual next-step recommendations for any
|
|
153
|
+
command.
|
|
154
|
+
- Successful actions, guidance, and lifecycle instructions now use semantic
|
|
155
|
+
terminal styling. Catalog and pack lifecycle summaries include duration, and
|
|
156
|
+
install and update success output includes selected versions.
|
|
157
|
+
- Pack parameters support typed defaults. Required prompts offer the default for
|
|
158
|
+
Enter acceptance; optional parameters bind it when no higher-precedence value exists.
|
|
159
|
+
|
|
160
|
+
### Lifecycle Hooks
|
|
161
|
+
|
|
162
|
+
- **Breaking:** Pack manifests replace the top-level `scripts` map with ordered
|
|
163
|
+
event arrays under `hooks`. Every declaration requires `type: script` or
|
|
164
|
+
`type: instruction`; legacy `scripts` manifests are rejected.
|
|
165
|
+
- Lifecycle events can interleave multiple scripts and Markdown instructions in
|
|
166
|
+
declaration order. Script trust remains executable-only, while instructions
|
|
167
|
+
display one H2/H3 step at a time interactively or print completely in
|
|
168
|
+
noninteractive sessions.
|
|
169
|
+
- `luna install` and every `luna update` form accept `--skip-instructions`
|
|
170
|
+
independently of `--scripts`. Dry runs validate instructions and report their
|
|
171
|
+
file, templating state, and step count without guided display.
|
|
172
|
+
- Declining an untrusted lifecycle hook now warns and skips the hook instead of
|
|
173
|
+
failing the pack operation.
|
|
174
|
+
- Windows lifecycle commands such as `npm` now resolve through `PATHEXT`,
|
|
175
|
+
avoiding invalid extensionless command shims.
|
|
176
|
+
- Interactive lifecycle hooks now inherit terminal input and output, allowing
|
|
177
|
+
commands such as `npm init` to display and handle their prompts.
|
|
178
|
+
- Untrusted script consent now shows a concise command summary and defaults to no.
|
|
179
|
+
- Packs can declare ordered `preUninstall` and `postUninstall` hooks. Uninstall
|
|
180
|
+
retrieves them from exact installed releases and warns but continues when the
|
|
181
|
+
source is unavailable.
|
|
182
|
+
- Install, update, and uninstall checkpoint managed ownership before post hooks,
|
|
183
|
+
preventing hard interruption from leaving applied files under stale lock state.
|
|
184
|
+
Handled post-hook failures still restore prior files and state.
|
|
185
|
+
Instructions display automatically with a preface, omit H1 titles, and format
|
|
186
|
+
headings, emphasis, code, and links.
|
|
187
|
+
|
|
188
|
+
## Version 1.0.0 - 2026-08-25
|
|
189
|
+
|
|
190
|
+
LunaPack 1.0.0 is the first public release for managing reusable, versioned
|
|
191
|
+
engineering packs in a consumer workspace.
|
|
192
|
+
|
|
193
|
+
### CLI And Catalog
|
|
194
|
+
|
|
195
|
+
- `luna init` creates version-1 `lunapack.yml` and `lunapack-lock.yml` files.
|
|
196
|
+
- `luna sources add local`, `luna sources add git`, and `luna sources list`
|
|
197
|
+
configure and inspect local or Git pack catalogs. Git sources support a ref
|
|
198
|
+
and a repository-relative pack path.
|
|
199
|
+
- `luna discover` and `luna search` show the latest release by default in
|
|
200
|
+
separate Pack and Version columns. Both accept `--versions` (`-v`) from one
|
|
201
|
+
through 10 to display recent distinct releases per pack.
|
|
202
|
+
- `luna validate <id>[@<version>]` reports manifest and selected-source-file
|
|
203
|
+
issues. `luna inspect <id>[@<version>]` shows selected pack metadata,
|
|
204
|
+
parameters, and references. Discovery and search isolate invalid candidates
|
|
205
|
+
in otherwise usable sources.
|
|
206
|
+
- `luna variables list`, `set <name> <value>`, and `rm <name>` manage project
|
|
207
|
+
variables. `luna remap list`, `set`, and `rm` manage target remapping.
|
|
208
|
+
- Every command supports `--workspace`; command options provide documented
|
|
209
|
+
shorthand aliases and completion.
|
|
210
|
+
- `--log-level` (`-ll`) selects lower-case Spectre.Console output levels.
|
|
211
|
+
Diagnostics use distinct prefixes, long operations show progress, and
|
|
212
|
+
interactive decisions use console prompts.
|
|
213
|
+
|
|
214
|
+
### Pack Lifecycle
|
|
215
|
+
|
|
216
|
+
- `luna install` resolves latest or exact pack releases. It supports multiple
|
|
217
|
+
ordered references, dry runs, project-relative destinations, parameters,
|
|
218
|
+
variables, conditions, templates, matching-file adoption, and composite
|
|
219
|
+
dependencies.
|
|
220
|
+
- Install warns and skips already-installed roots while continuing remaining
|
|
221
|
+
references. Missing explicit versions suggest the latest available version.
|
|
222
|
+
- `luna outdated` identifies roots with available updates. `luna update`
|
|
223
|
+
updates one root or all roots, supports dry runs, and can prompt for roots
|
|
224
|
+
during an all-pack update.
|
|
225
|
+
- `luna uninstall` conservatively removes unchanged, unshared managed content.
|
|
226
|
+
Missing targets warn without blocking ownership cleanup; line and JSON merge
|
|
227
|
+
targets remain in place.
|
|
228
|
+
- `luna mv` relocates one uniquely owned managed file and can rebind ownership
|
|
229
|
+
after a matching manual move. `luna audit` reports resolved packs, source
|
|
230
|
+
provenance, dependencies, and managed-file ownership.
|
|
231
|
+
- Pack manifests can declare `preInstall`, `postInstall`, `preUpdate`, and
|
|
232
|
+
`postUpdate` hooks. Install and update accept `--scripts prompt|run|skip`;
|
|
233
|
+
prompt mode requires source-specific trust or interactive consent, while run
|
|
234
|
+
mode explicitly authorizes hooks for that invocation.
|
|
235
|
+
- Lifecycle script arguments are strict Scriban templates over resolved pack
|
|
236
|
+
parameters. Luna renders each argument before dry-run output, authorization,
|
|
237
|
+
and execution while preserving one manifest item as one process argument.
|
|
238
|
+
- Lifecycle writes and Luna-managed project state are transactional. SHA-256
|
|
239
|
+
ownership checks protect consumer edits and immutable operation snapshots
|
|
240
|
+
protect approved script inputs.
|
|
241
|
+
|
|
242
|
+
### Pack Authoring And Formats
|
|
243
|
+
|
|
244
|
+
- Version-1 schemas define project configuration, complete resolved lock state,
|
|
245
|
+
and pack manifests. Paths accept either separator at input boundaries and
|
|
246
|
+
persist with forward slashes.
|
|
247
|
+
- Lock files record exact dependency graphs, configured source identities,
|
|
248
|
+
immutable source provenance, declared and effective targets, parameters,
|
|
249
|
+
strategies, and installed-content digests.
|
|
250
|
+
- Packs support exact-version dependencies, composites, referenced-parameter
|
|
251
|
+
bindings, source files, directories, globs, conditions, UTF-8 Scriban
|
|
252
|
+
templates, and string, Boolean, or enum parameters.
|
|
253
|
+
- Managed files support copy, line merge, section merge, and JSON merge
|
|
254
|
+
strategies. Shared targets require compatible merge strategies.
|
|
255
|
+
- Pack manifests require non-empty license and author attribution, accept up to
|
|
256
|
+
15 searchable tags, and require `template: true` before Scriban rendering.
|
|
257
|
+
|
|
258
|
+
### Distribution
|
|
259
|
+
|
|
260
|
+
- Luna ships self-contained Native AOT archives for Windows x64, Linux x64,
|
|
261
|
+
Linux Arm64, macOS x64, and macOS Arm64; the
|
|
262
|
+
`@lunarisdigitalsolutions/lunapack` npm launcher with matching platform
|
|
263
|
+
packages; the `Lunaris.Lunapack.Luna` .NET tool package; and a Linux x64 OCI
|
|
264
|
+
image.
|
|
265
|
+
- Distribution packages expose the `luna` executable. Archive checksums and
|
|
266
|
+
package provenance support artifact verification.
|
package/package.json
CHANGED
|
@@ -1,20 +1,21 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lunarisdigitalsolutions/lunapack",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.3.0",
|
|
4
4
|
"description": "Luna CLI.",
|
|
5
5
|
"bin": {
|
|
6
6
|
"luna": "run-luna.mjs"
|
|
7
7
|
},
|
|
8
8
|
"optionalDependencies": {
|
|
9
|
-
"@lunarisdigitalsolutions/lunapack-win64": "1.
|
|
10
|
-
"@lunarisdigitalsolutions/lunapack-linux-x64": "1.
|
|
11
|
-
"@lunarisdigitalsolutions/lunapack-linux-arm64": "1.
|
|
12
|
-
"@lunarisdigitalsolutions/lunapack-macos-x64": "1.
|
|
13
|
-
"@lunarisdigitalsolutions/lunapack-macos-arm64": "1.
|
|
9
|
+
"@lunarisdigitalsolutions/lunapack-win64": "1.3.0",
|
|
10
|
+
"@lunarisdigitalsolutions/lunapack-linux-x64": "1.3.0",
|
|
11
|
+
"@lunarisdigitalsolutions/lunapack-linux-arm64": "1.3.0",
|
|
12
|
+
"@lunarisdigitalsolutions/lunapack-macos-x64": "1.3.0",
|
|
13
|
+
"@lunarisdigitalsolutions/lunapack-macos-arm64": "1.3.0"
|
|
14
14
|
},
|
|
15
15
|
"files": [
|
|
16
16
|
"run-luna.mjs",
|
|
17
|
-
"README.md"
|
|
17
|
+
"README.md",
|
|
18
|
+
"CHANGELOG.md"
|
|
18
19
|
],
|
|
19
20
|
"license": "MIT",
|
|
20
21
|
"repository": "github:lunarisdigitalsolutions/lunapack"
|