ci(publish): single-package option to publish @saga-ed/soa-rum-util#110
Merged
Conversation
Adds an optional 'single_package' workflow_dispatch input. When set to a package path (e.g. packages/web/rum-util), the test, version-bump and publish jobs all scope to that one package instead of the standard coordinated multi-package release. Empty input preserves existing behavior exactly. Unblocks publishing @saga-ed/soa-rum-util (on main but never wired into the hardcoded publishable list) to CodeArtifact without bumping/republishing the ~15 unrelated node packages.
✅ Test Results
Package Results
Commits
LinksUpdated: 2026-06-01T23:37:11.406Z |
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
1 participant
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.
Why
@saga-ed/soa-rum-util(v0.1.0) is on `main` with a CodeArtifact `publishConfig`, but it was never wired into `publish-codeartifact.yml`'s hardcoded publishable list — so it has never been published (aws codeartifact list-package-versions … soa-rum-util→ `ResourceNotFoundException`). qboard (connectv3) and janus (login) are about to consume it, so it needs to land in CodeArtifact.Adding it to the existing hardcoded list would force a coordinated patch-bump + republish of all ~15 other node packages. Instead this adds a surgical single-package path.
What
New optional `single_package` `workflow_dispatch` input (a package path, e.g. `packages/web/rum-util`).
Input value is consumed via a workflow-level `SINGLE_PACKAGE` env var and referenced as `"$SINGLE_PACKAGE"` in shell (never inline `${{ }}`) per Actions injection-safety guidance.
Validation
After merge
Dispatch with `single_package=packages/web/rum-util`, `version=patch`, `publish_target=codeartifact` → publishes `@saga-ed/soa-rum-util@0.1.1` to CodeArtifact (`saga_js`).