Repository navigation
feat(actions)!: simplify package tooling and dependency setup - #564
Merged
Merged
Conversation
Centralize native pack commands, package prepared files, and default installation lifecycle scripts to disabled. Group the existing package actions and configure Renovate for the shared runtime. BREAKING CHANGE: use actions/package/create and actions/package/publish. Callers prepare source, tooling and versions before packaging. Installation hooks require ignore-scripts: false.
Contributor
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Contributor
|
Code Coverage Report Coverage ResultsCoverage
Overall: 100.00% 🟢 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #564 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 3 3
=========================================
Hits 3 3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
neilime
added a commit
that referenced
this pull request
Nov 4, 2026
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.
Make the general Node.js actions independently usable before adding release automation in #562.
setup-nodeconfigure tooling without installing dependencies for packaging prepared build files or caller-managed installation. Normal build, lint and test jobs keep installation enabled.actions/package/createandactions/package/publish.get-package-manager.outputs.pack-commandfor native npm, pnpm and Yarn Classic packing with lifecycle scripts disabled. Package creation uses an isolated output directory and cleans it on failure.DEFAULT_PNPM_VERSION; a project'spackageManagerdeclaration takes precedence.Breaking changes: update the package action paths, remove the Package action's
versioninput, and prepare source/tooling/version/build output before calling it. Installation hooks now requireignore-scripts: false. Package creation always disables lifecycle scripts.The existing package example and generated references follow these APIs. The new preparation/release workflows, version commits, recovery behavior, release-specific actions, tests and consolidated ADR are delivered by #562.
Review and merge order: this PR → #562 (single-package release) → #563 (workspaces/Lerna).
Validation: