chore(deps): bump @framers/* deps to latest published versions#34
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1845de722c
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "license": "MIT", | ||
| "peerDependencies": { | ||
| "@framers/agentos": ">=0.7.0" | ||
| "@framers/agentos": "^0.9.156" |
There was a problem hiding this comment.
Add a changeset for the dependency bump
For already-published curated packages, changing this peer range only in package.json does not update the npm package metadata unless Changesets also bumps and republishes the package. I checked .changeset/ and this commit adds no changeset or package version bump, while the release workflow publishes through changesets/action, so the ^0.9.156 requirement will remain only in git until each affected package happens to be versioned for some other change.
Useful? React with 👍 / 👎.
jddunn
left a comment
There was a problem hiding this comment.
Dep bump verified: 116 package.json files, pure @framers/* version bumps, no other content. CI green.
Automated weekly bump of all
@framers/*dependencies to theirlatest npm-published versions.
Includes (when applicable):
package.jsonexplicit-pin updates (caret semver of latest)pnpm-lock.yamlrefreshWorkspace
workspace:*pins are not touched. Review the difffor any unexpected major-version jumps before merging.