Will Prisma 7 support applying migrations programatically instead of needing the CLI? This is an issue when deploying to k8s with databases that are not available publicly and therefore not accessible from Github Actions.

FYI but one or two of your tables overflow and causes some sideways scrolling on mobile.

Ah yes, the "fork off". 😆

Saw your talk which made me realize I had some weird library configurations on my own libs. Back at work cleaning up now thanks to your talk. :-)

Nice! Btw the release points to the wrong codemod, seems like it should be `@apollo/client-codemod-migrate-3-to-4` :) The one in the docs give a 404 on install.

some more context: we deploy our apps to a k8s cluster, and during deploy both old and new version of the app might receive traffic at the same time, so to make sure users don't get 404s on static files, we put the public files on a CDN and use assetPrefix to point all static files towards it.

That's strange. No warnings at all here.

I'm specifically using bunx, maybe that changes things?

`bunx npm-check-updates --format group -i`

Hmm, yeah seems like bsky borked the upload. But it just was just a screenshow of ncu upgrading a bunch of deps, including one that's private.

Here's my bunfig.toml: github.com/navikt/tsm-c...

hmm, I've configured my bun to use private packages (for a specific scope), and ncu is able to upgrade these for me

`yarn upgrade-interactive` is my bae, but ncu has saved my sanity on my bun projects. 😀

I could host several versions of the app, and route to the correct k8s pod based on the version.

But that's a whole lot of infra just to handle this, when version skew can usually be handled by deploying breaking changes in several steps to allow the changes to propagate to your users.

@johngreensbluesky.bsky.social @hankgreen.bsky.social you should both set up domain handles. 😀 @hank.dftba.com and @john.dftba.com would be cool!

bsky.social/about/blog/4...