Skip to content

chore: track pnpm-lock.yaml - #30

Closed
contextablemark wants to merge 1 commit into
mainfrom
chore/add-pnpm-lockfile
Closed

chore: track pnpm-lock.yaml#30
contextablemark wants to merge 1 commit into
mainfrom
chore/add-pnpm-lockfile

Conversation

@contextablemark

Copy link
Copy Markdown
Owner

Summary

  • Adds pnpm-lock.yaml to the repo so contributors and CI install the exact same dependency tree.
  • Generated against current main package.json (@ag-ui/core ^0.0.43, @ag-ui/encoder ^0.0.43, openclaw file:../openclaw) with pnpm 10.28.0.
  • No source or package.json changes.

Why split out

PR #26 originally bundled this lockfile addition (7241 lines in the diff). Splitting it lets the reasoning/step-events change land as a focused, reviewable diff and keeps the lockfile-policy decision explicit.

Order of merging

If this lands first, PR #26 will see a small lockfile delta on rebase (regenerating against @ag-ui ^0.0.52). If PR #26 lands first, this PR will need to be regenerated on top.

Test plan

  • pnpm install --frozen-lockfile resolves cleanly (verified locally during generation).
  • Confirm CI/contributors run pnpm install --frozen-lockfile going forward.

🤖 Generated with Claude Code

Adds pnpm-lock.yaml so dependency installs are reproducible across
contributors and CI. Generated against current main package.json
(@ag-ui/core ^0.0.43, @ag-ui/encoder ^0.0.43, openclaw file:../openclaw)
with pnpm 10.28.0.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@contextablemark

Copy link
Copy Markdown
Owner Author

Closing per discussion — for a published library with no CI and a file:../openclaw workspace dep, tracking the lockfile is more friction than benefit (consumers don't see it, file: paths aren't portable, @ag-ui/* 0.0.x range will churn under Renovate). Will instead add pnpm-lock.yaml to .gitignore so a stray pnpm install doesn't sneak it back into a future PR.

@contextablemark
contextablemark deleted the chore/add-pnpm-lockfile branch April 26, 2026 03:32
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