chore(deps): bump @framers/* deps to latest published versions#5
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 652e71d0a2
ℹ️ 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".
| "@fastify/swagger": "^9.6.1", | ||
| "@fastify/swagger-ui": "^5.2.3", | ||
| "@framers/agentos": "^0.9.135", | ||
| "@framers/agentos": "^0.9.164", |
There was a problem hiding this comment.
Regenerate the backend lockfile for this bump
This new backend dependency range is incompatible with the committed backend/package-lock.json, which still records the root dependency as ^0.9.135 and locks node_modules/@framers/agentos to 0.9.138 (backend/package-lock.json:19, :836). For any standalone backend install/deploy that uses npm ci, npm documents that it exits when package-lock dependencies do not match package.json (https://docs.npmjs.com/cli/v8/commands/npm-ci), so the clean install will fail or keep the backend from being reproducibly installed at the bumped version. Please regenerate and commit backend/package-lock.json with this package bump.
Useful? React with 👍 / 👎.
jddunn
left a comment
There was a problem hiding this comment.
Dep bump verified: pure @framers/agentos ^0.9.135→^0.9.164, 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.