Repository navigation
Conversation
Replace main-push publication with release: released, retain manual dispatch and skip GitHub-marked prereleases. Allow release tag refs without changing checkout or publication behavior. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
Tying public npm publication to stable go-spdx releases while bypassing the default-branch check requires maintainer policy approval and validation through a real release.
No open issues 🎉
What changed in this PR
Moves license-category npm publication from package-path pushes to stable GitHub releases while retaining manual publishing.
Changes:
- Trigger publication on stable releases, including prerelease promotions, and skip GitHub-marked prereleases.
- Preserve the publication enablement gate and default-branch restriction for manual dispatches; release runs use the tagged commit.
- Update publication documentation without changing build, test, or publish commands.
| File | Description |
|---|---|
packages/license-categories/docs/operations.md |
Documents release-triggered publishing and revised maintainer steps. |
.github/workflows/publish-license-categories.yaml |
Replaces the push trigger with release events and adjusts event guards. |
Review effort: Max (auto)
ljones140
approved these changes
Nov 12, 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.
Summary
First minimal upper layer above #175: change publication triggers only.
release: released, covering initial stable releases and prereleases promoted to stable.workflow_dispatch, the existing publication enablement gate, and the default-branch restriction for dispatches. Skip GitHub-marked prereleases and let release runs check out the event's tag commit using the unchanged checkout step.Provenance, generated-data comparison, generator/Makefile behavior, concurrency, OIDC, Node/npm versions, package tests, and publication commands are unchanged. Existing PRs remain open; this is a fresh PR.
Validation
Parsed the workflow YAML and checked seven focused scenarios: stable release, promotion, prerelease skip, default-branch dispatch, other-branch rejection, and disabled release/dispatch.