SP-873: Add single package export command#378
Merged
Conversation
Add `config package export`, the counterpart of `config package import`, backed by the new single-package export API (pacman#1997). Exports a package's staging (draft) version in the package format: unzipped into a <packageKey> directory by default, or as a <packageKey>.zip file with --zip. Output is written to the current working directory. Includes-AI-Code: true Co-authored-by: Cursor <cursoragent@cursor.com>
3 tasks
Laberion Ajvazi (LaberionAjvazi)
previously approved these changes
Jun 16, 2026
Resolve modify/delete conflict in the configuration-management tests. SP-1089 (#374) deleted the per-module unit spec (tests/commands/configuration-management/module.spec.ts) in favor of an integration spec. Port the `config package export` handler tests into tests/integration/commands/configuration-management.spec.ts (driven via the CLI parser, so the unzipped default asserts zip=false) and accept the deletion of the old unit spec. Includes-AI-Code: true Co-authored-by: Cursor <cursoragent@cursor.com>
|
Kastriot Salihu (ksalihu)
approved these changes
Jun 18, 2026
Zgjim Haziri (ZgjimHaziri)
added a commit
that referenced
this pull request
Jun 18, 2026
Resolve conflicts after the base PR #378 (SP-873 single package export) was squash-merged into main. This branch is stacked on SP-873, so it already contained those changes plus the SP-992 Git capabilities on top. Every conflict was therefore resolved by keeping this branch's superset version (single-package-export.service.ts, module.ts, file-service.ts, the export/file-service unit specs, and config-commands.md). Also dropped a duplicate "config package export" describe block that the auto-merge re-added from main in the integration spec (it asserted the old 2-arg exportPackage signature). The resulting tree is identical to this branch's pre-merge HEAD; tsc and the full jest suite pass. Includes-AI-Code: true Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds
config package export, the counterpart ofconfig package import, backed by the new single-package export API (pacman#1997, SP-872).It exports a package's staging (draft) version in the plain package format (
package.json, an optionalvariables.json, and anodes/folder) — the same formatconfig package importconsumes, so a package round-trips between teams without conversion. Unliket2tc package export, it handles exactly one package and does not produce a batch artifact.<packageKey>directory in the current working directory.--zip: exports it as a single<packageKey>.zipfile instead.Relevant links
Checklist
Made with Cursor