[slaskawi]

Description

Use Zarf's shared model and parser in Legacy and Next. Preserve package schemas and Next public APIs.

Related Issue

CLI-363

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide Steps followed

Commit override

BEGIN_COMMIT_OVERRIDE
feat!: support Zarf beta schemas in both CLI modes

BREAKING CHANGE: Legacy Go integrations must use Zarf's api.Package and api.Component types for package readers and fetchers. CLI commands and Next public APIs remain compatible.

Zarf package migration guide: https://docs.zarf.dev/best-practices/v1alpha1-to-v1beta1/
END_COMMIT_OVERRIDE

[slaskawi]

@codex review

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-29T06:42:02.819352Z	7d9f569	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 👍

Reviewed commit: 7d9f569708

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[slaskawi]

@greptileai review

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The changes reviewed appear safe to merge.

Summary

Legacy now uses Zarf’s shared package model and parser, preserving beta fields during reads, filtering, and deployment. Next keeps its public APIs unchanged.

• Legacy bundle flows carry alpha and beta package fields through to package operations.
• Next reads package names from Zarf’s shared definition.
• A task checklist records the work and remaining steps for CLI-363.

No new actionable issues were found in the changes since the previous review.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Alpha or beta package] --> B[Zarf shared parser and model]
  B --> C[Legacy metadata and component filters]
  B --> D[Next package layout]
  C --> E[Zarf deployment]
  D --> E

Loading

_{Reviews (2) · Last reviewed commit: "comments addressed" · Reviewed by Greptile}

[joelmccoy]

Mostly looking good. Just would like to see @eoghanriley 's comments addressed. They are similar things I noticed and commented on as well.

[slaskawi]

Thanks for the review @joelmccoy and @eoghanriley !

All the comments addressed and the test suite has been slightly adjusted to the Pyramid Shape (following the ADR 27)