Repository navigation
Conversation
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 #562 +/- ##
=========================================
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:
|
Signed-off-by: Emilien Escalle <emilien.escalle@escemi.com>
neilime
force-pushed
the
feat/release-orchestration
branch
from
November 3, 2026 12:40
65ffd4f to
05023e6
Compare
This branch has not been deployed
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 the common release path for one public npm package through reusable prepare → CI → release workflows. Callers own manual and scheduled triggers; HoverKraft owns Conventional Commit version planning, GitHub release notes, optional AI summaries and publication. No consumer release scripts or Release Please are required.
actions/github-script; the only shared JavaScript helper handles artifact identity and retry integrity.prepare-package-release.ymlapplies the exact HoverKraft plan with npm, updates the manifest and lockfile, atomically pushes the version commit and tag, then dispatches the caller at that tag. Reject unsupported layouts before preparing a version.CHANGELOG.mdand uses no internal changelog-rendering helper. Existing changelog files are preserved.ci-github-publish/release/create, packages without installing or rebuilding, checks the tarball and publishes it. Finalization usesrelease/updatefor assets and publication..node-version, fixture symlinks and scheduled/manual Renovate updates remain shared maintenance.Workspace selection, pnpm workspace packing, fixed/independent Lerna, per-package notes and matrix recovery are moved to #563, based on this branch. Merge #562 first, then retarget #563 to
main. The common release suite has no external dependencies. The dedicated__test-release.ymlworkflow runs it through shared CI.Validation:
make lint, Actionlint (excluding unsupported native$/references), 31 local interfaces, 18 inline scripts, 61 documentation links andgit diff --checkpassed.Scope: stable public npm packages, npmjs.org, GitHub-hosted Ubuntu without a CI container, and CI artifacts from the same run and prepared commit. Consumers must configure a release identity, environment rules, npm trusted publishing and consistent release history. No live npm/GitHub release publication or AI generation was performed.