Skip to content

Allow forced license categories publishing - #192

Merged
ljones140 merged 1 commit into
mainfrom
force-license-categories-publish
Nov 16, 2026
Merged

ljones140 merged 1 commit into
mainfrom
force-license-categories-publish

Conversation

Copilot AI commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Allow manual publishing of license categories without comparing the generated data.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues block the opt-in manual publication change.

No open issues 🎉

What changed in this PR

This PR adds an opt-in way to manually publish the license-categories package without comparing its generated data with the latest npm publication.

Changes:

  • Adds a force_publish input, defaulting to false, that skips comparison and permits publication on manual dispatch.
  • Updates workflow assertions to cover the forced-publication conditions.
  • Documents the option, unchanged publication safeguards, and version-bumping requirements.
File Description
packages/​license-categories/​test/​comparison.test.mjs Updates assertions for the manual input and comparison/publishing conditions.
packages/​license-categories/​docs/​operations.md Explains forced publishing, safeguards, and version requirements.
.github/​workflows/​publish-license-categories.yaml Adds the input and conditional comparison bypass for manual publishing.

Review effort: Balanced (dynamic)

@ljones140
ljones140 marked this pull request as ready for review November 16, 2026 09:53
@ljones140
ljones140 merged commit 2022b3f into main Nov 16, 2026
9 checks passed
@ljones140
ljones140 deleted the force-license-categories-publish branch November 16, 2026 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants