ci: share artifact workflow for dev packages#274
Merged
Conversation
3a1ffc3 to
133ae10
Compare
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.
Summary
Unify dev and release artifact packaging on the same reusable artifact build path.
build-release-artifacts.ymltobuild-artifacts.yml.scripts/build-release-artifact.shtoscripts/build-artifact.sh.Dev Artifactscall the same reusable workflow as release/prerelease builds.Dev Packagejobs and their separate target matrix.build-kind.This makes dev and release packaging use one path for native archives and VSIX artifacts, including Alpine x64/arm64.
Verification
node --check .github/scripts/ci-plan.mjsbash -n scripts/build-artifact.shbuild-release-artifact,Dev Package, andrun_dev_packagenamescargo-dist plan --tag v1.3.0-beta.1 --output-format=json