Skip to content

chore: publish gate — lockfile sync, 0.13.1 bump, prepublishOnly (AIT-177) - #19

Merged
ord669 merged 4 commits into
mainfrom
ait-177-publish-gate
Jul 14, 2026
Merged

chore: publish gate — lockfile sync, 0.13.1 bump, prepublishOnly (AIT-177)#19
ord669 merged 4 commits into
mainfrom
ait-177-publish-gate

Conversation

@ord669

@ord669 ord669 commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Syncs package-lock.json with package.json (version 0.13.0 + node >=20 had drifted — npm ci failed the publish audit).
  • Bumps to 0.13.1 so the already-merged fixes on main (AIT-164 billing manage --json, AIT-151 coded-403 surfacing) can ship to npm — published 0.13.0 predates them.
  • Adds prepublishOnly: npm run build && npm run test:unit so a stale dist/ or red unit suite can never be published.

Test plan

  • npm run test:unit — 937/937 pass
  • npm install --package-lock-only — lockfile diff is version fields only (no drift)
  • Built CLI: billing manage --json against a dead API emits pure JSON, no browser (AIT-164 verification)

Fixes AIT-177
Refs AIT-164 (fix already on main via #16; ships with this release)

Summary by CodeRabbit

  • New Features

    • Released CLI version 0.13.1.
  • Bug Fixes

    • Improved publish consistency by ensuring the project is rebuilt as part of the pre-publish flow and that unit tests run before publishing.

ord669 added 2 commits July 13, 2026 16:38
Lockfile on main lagged the 0.13.0 version bump; regenerated to match.
Publish-readiness gate for the next npm release: lockfile synced with
package.json (0.13.0/node>=20 drift), version bumped to 0.13.1 so the
already-merged AIT-164/AIT-151 fixes can ship, and prepublishOnly runs
build + unit tests so a stale dist or red suite can't be published.
@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1b34d9b3-c63e-458c-a2ad-b4e937527812

📥 Commits

Reviewing files that changed from the base of the PR and between ac0f8a2 and 1f10b15.

📒 Files selected for processing (1)
  • .github/workflows/publish.yml

📝 Walkthrough

Walkthrough

The CLI package version is updated to 0.13.1. Pre-publishing now builds and runs unit tests, while the npm publish workflow documents the rebuild and passes release environment variables through.

Changes

Package release configuration

Layer / File(s) Summary
Release metadata and publish workflow
package.json, .github/workflows/publish.yml
Updates the package version, adds unit tests to prepublishOnly, and passes release environment variables to npm publish while documenting the rebuild behavior.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

  • hookmyapp/cli#13: Previously updated the CLI package version from 0.12.12 to 0.13.0.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly reflects the main changes: lockfile sync, version bump, and adding a prepublishOnly publish gate.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ait-177-publish-gate
⚔️ Resolve merge conflicts
  • Resolve merge conflict in branch ait-177-publish-gate

Comment @coderabbitai help to get the list of available commands.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ac0f8a29b7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread package.json
@ord669

ord669 commented Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@ord669
ord669 merged commit 678cd4b into main Jul 14, 2026
1 of 2 checks passed
@ord669
ord669 deleted the ait-177-publish-gate branch July 14, 2026 10:04
@coderabbitai coderabbitai Bot mentioned this pull request Jul 15, 2026
1 task
This was referenced Jul 23, 2026
ord669 added a commit that referenced this pull request Aug 12, 2026
…-177) (#19)

* chore: sync package-lock.json with package.json (0.13.0, node >=20)

Lockfile on main lagged the 0.13.0 version bump; regenerated to match.

* chore: bump to 0.13.1 + prepublishOnly gate (AIT-177)

Publish-readiness gate for the next npm release: lockfile synced with
package.json (0.13.0/node>=20 drift), version bumped to 0.13.1 so the
already-merged AIT-164/AIT-151 fixes can ship, and prepublishOnly runs
build + unit tests so a stale dist or red suite can't be published.

* fix: pass release env to npm publish step so prepublishOnly rebuild keeps baked values (AIT-177)
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