chore: update dependencies

[mincong-h]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
demo-github-server	Ignored	Preview		Dec 3, 2025 5:07pm

[vertesia-code-review]

Changes

This pull request updates the github-agent application, focusing on dependency updates and code adjustments to align with the latest @vertesia/common and @dglabs/* packages. The key changes involve updating dependencies in package.json, adapting activity definitions to use new Vertesia common types, and updating references to SecretProviderKind to @dglabs/server-common. These updates ensure compatibility with the latest Vertesia and DGLabs services and improve code maintainability.

Here is a breakdown of the changes:

Path	Description
apps/github-agent/package.json	Updated dependencies for @dglabs/cloud, @dglabs/worker, @temporalio/*, and @vertesia/*. Also, the rimraf package has been removed, replaced by rm -rf in the clean script. These updates ensure the project uses the latest versions of these libraries.
apps/github-agent/src/activities.ts	Modified the createChangeEntry activity to use CreateContentObjectPayload from @vertesia/common instead of UploadContentObjectPayload from @vertesia/client. This change aligns with the updated Vertesia API and ensures correct payload structure for creating change entries.
apps/github-agent/src/activities/github.ts	Updated the import path for SecretProviderKind from @dglabs/cloud to @dglabs/server-common. This change reflects the relocation of the SecretProviderKind type within the DGLabs libraries.
apps/github-agent/src/activities/vertesia.ts	Updated the import path for SecretProviderKind from @dglabs/cloud to @dglabs/server-common. Also, added type assertion for Vertesia API responses to ensure correct type handling.
package.json	Updated and added package overrides to use the latest versions of @vertesia/* and @llumiverse/common, as well as other packages to resolve dependency conflicts.
pnpm-lock.yaml	Updated the lock file to reflect the new dependency versions and overrides.

Purpose

The motivation for this pull request is to ensure the project is using the latest versions of its dependencies. Updating dependencies can bring several benefits, including bug fixes, performance improvements, new features, and enhanced security. By keeping dependencies up-to-date, the project can benefit from the ongoing work of the open-source community and reduce the risk of using outdated and potentially vulnerable code.

The context of this pull request is a general maintenance task aimed at keeping the project's dependencies current. Without specific issues or feature requests driving the update, it's likely a proactive measure to maintain the health and stability of the project. Regular dependency updates are a good practice to avoid technical debt and ensure compatibility with other libraries and tools in the ecosystem.

Related issues: N/A

Code Review

You can start a code review by adding a comment: "Vertesia, please review".

Note that the motivation and context are rated as moderate (3/5), you can improve the motivation and the problem statement to clarify the purpose of the pull request. You can provide information in the pull request description or link this pull request to a GitHub issue.