Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: deepseek model for ai api #816

Merged
merged 4 commits into from
Jan 30, 2025
Merged

feat: deepseek model for ai api #816

merged 4 commits into from
Jan 30, 2025

Conversation

joelhooks
Copy link
Contributor

@joelhooks joelhooks commented Jan 23, 2025

Summary

I wanted to use the deepseek api for it's reasoner as a planner network https://x.com/skirano/status/1881854481304047656

I didn't do the stuff below, wanted to see if there is interest in the PR first ;)

Checklist

  • Added a docs PR that references this PR N/A
  • Added unit/integration tests N/A for AI yet
  • Added changesets if applicable

Copy link

changeset-bot bot commented Jan 23, 2025

🦋 Changeset detected

Latest commit: f80c5f6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@inngest/ai Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@jpwilliams jpwilliams self-assigned this Jan 27, 2025
@jpwilliams jpwilliams added ✨ new New features, integrations, or exports prerelease/inngest Create snapshot releases for a PR for the "inngest" package. labels Jan 27, 2025
@jpwilliams jpwilliams marked this pull request as ready for review January 27, 2025 16:42
@jpwilliams jpwilliams merged commit fadd94a into inngest:main Jan 30, 2025
31 of 35 checks passed
jpwilliams pushed a commit that referenced this pull request Jan 30, 2025
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @inngest/[email protected]

### Patch Changes

- [#816](#816)
[`fadd94a`](fadd94a)
Thanks [@joelhooks](https://github.com/joelhooks)! - Add Deepseek
support

## [email protected]

### Patch Changes

- [#817](#817)
[`446be1b`](446be1b)
Thanks [@jpwilliams](https://github.com/jpwilliams)! - `serve()` and
`connect()` now have looser typing for `client` and `functions`,
resulting in easier use of multiple `inngest` packages in a single
process

- [#823](#823)
[`f1d2385`](f1d2385)
Thanks [@jpwilliams](https://github.com/jpwilliams)! - Allow wildcard
event typing with `.fromRecord()`

    The following schema is now valid:

    ```ts
    export const schemas = new EventSchemas().fromRecord<{
      "app/blog.post.*":
        | {
            name: "app/blog.post.created";
            data: {
              postId: string;
              authorId: string;
              createdAt: string;
            };
          }
        | {
            name: "app/blog.post.published";
            data: {
              postId: string;
              authorId: string;
              publishedAt: string;
            };
          };
    }>();
    ```

When creating a function, this allows you to appropriately type narrow
the event to pull out the correct data:

    ```ts
    inngest.createFunction(
      { id: "my-fn" },
      { event: "app/blog.post.*" },
      async ({ event }) => {
        if (event.name === "app/blog.post.created") {
          console.log("Blog post created at:", event.data.createdAt);
        } else if (event.name === "app/blog.post.published") {
console.log("Blog post published at:", event.data.publishedAt);
        }
      },
    );
    ```

- [#825](#825)
[`661ed7b`](661ed7b)
Thanks [@jpwilliams](https://github.com/jpwilliams)! - If no `functions`
are provided to `inngest.connect()`, it will now use any functions that
have been created with the client instead

- Updated dependencies
\[[`fadd94a`](fadd94a)]:
    -   @inngest/[email protected]

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ new New features, integrations, or exports prerelease/inngest Create snapshot releases for a PR for the "inngest" package.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants