Repository navigation
Conversation
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
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.
Add a public composite Action that packages any publisher's completed manifest and prebuilt payload using the standard mpack container format.
The Action builds its bundled packager as a standalone locked Cargo project, or accepts an existing trusted mpack path. It returns the unsigned package path, SHA-256 and checksum-file path. It neither changes package capabilities/provenance nor signs, uploads or publishes software. Application compilation and release approval remain caller workflow steps.
Validation: 9 local tests, including actual mpack creation, literal shell-like filenames, output/manifest/payload boundaries and symlink refusal. The workflow also builds the bundled tool without the OS/AppCore workspace and exercises the composite Action itself.
The branch initially inherited the existing AppCore diagnostics commit; a follow-up removes those code changes from this PR without rewriting history. Its existing Cargo.lock update is retained under the workspace lockfile policy; the Action uses its own standalone tool.Cargo.lock.