Skip to content

Add manual publish workflow for luxprog program package#26

Merged
sclaiborne merged 1 commit into
mainfrom
add-luxprog-publish
May 1, 2026
Merged

Add manual publish workflow for luxprog program package#26
sclaiborne merged 1 commit into
mainfrom
add-luxprog-publish

Conversation

@sclaiborne

Copy link
Copy Markdown
Member

Summary

  • Adds dedicated build-publish-luxprog.yml (workflow_dispatch only) so the @loupeteam/luxprog program package can publish on its own cadence, independent of the OMJSON library's tag-driven release. Mirrors the piperprog (Piper PR LUX Program Package Update. #15) and errorprog (ErrorLib PR Case-insensitivity for Sec-WebSocket-Key header #6) precedent.
  • Bumps src/Ar/Lux/package.json 0.2.1 -> 1.0.0 with AS6-compatible dep ranges (@loupeteam/omjson >=2.0.0 to match the v2.0.0 lib release, @loupeteam/hammers >=1.0.0), adds publishConfig -> GitHub Packages, normalizes the repo URL to git+https://github.com/loupeteam/OMJSON.git, and adds the homepage field per LoupeDocs convention.
  • CHANGELOG entry for 1.0.0.

Test plan

  • Merge to main.
  • Manually dispatch Build and Publish luxprog with version v1.0.0.
  • Confirm @loupeteam/luxprog@1.0.0 lands on GitHub Packages and that the artifact contains the LuxProg source (no binary export).

Adds dedicated `build-publish-luxprog.yml` (workflow_dispatch only) so the
luxprog program package can publish on its own cadence, independent of the
OMJSON library's tag-driven release. Follows the piperprog/errorprog pattern.

Bumps src/Ar/Lux/package.json to 1.0.0 with AS6-compatible deps
(@loupeteam/omjson >=2.0.0, @loupeteam/hammers >=1.0.0), adds publishConfig
pointing at GitHub Packages, and normalizes the repo URL to git+https form.
@sclaiborne sclaiborne merged commit 6dd95d4 into main May 1, 2026
1 check passed
@sclaiborne sclaiborne deleted the add-luxprog-publish branch May 1, 2026 14:24
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.

1 participant