build(deps): bump trim and next-mdx-remote

Removes trim. It's no longer used after updating ancestor dependency next-mdx-remote. These dependencies need to be updated together.

Removes trim

Updates next-mdx-remote from 3.0.8 to 4.4.1

Release notes

Sourced from next-mdx-remote's releases.

v4.4.1

What's Changed

chore(types): remove unused imports by @thiskevinwang in hashicorp/next-mdx-remote#348

fix: Make sure frontmatter types flow through to MDXRemote by @BRKalow in hashicorp/next-mdx-remote#351

Full Changelog: https://github.com/hashicorp/next-mdx-remote/compare/v4.4.0...v4.4.1

v4.4.0

This release includes a few fixes for frontmatter types, as well as a way to provide a frontmatter type to serialize or compileMDX and have it propagate through to the returned frontmatter property. See the documentation for an example.

serialize:
import { serialize } from 'next-mdx-remote/serialize'
interface Frontmatter {
title: string
published: string
description?: string
}
//     👇 should have type Frontmatter
const { frontmatter } = serialize<Record<string, unknown>, Frontmatter>(source)
compileMDX:
import { compileMDX } from 'next-mdx-remote/rsc'
interface Frontmatter {
title: string
published: string
description?: string
}
export default async function Page({ source }) {
//              👇 should have type Frontmatter
const { content, frontmatter } = await compileMDX<Frontmatter>(source)
return (
    &lt;&gt;
        &lt;h1&gt;{frontmatter.title}&lt;/h1&gt;
        {content}
    &lt;/&gt;
)

}
What's Changed

docs: fix react server components example by @greyhere in hashicorp/next-mdx-remote#334

... (truncated)

Commits

1c8acee 4.4.1
e4c7a69 fix: Make sure frontmatter types flow through to MDXRemote (#351)
e7f6ec1 chore(types): remove unused imports (#348)
ce066d7 4.4.0
2b35582 feat: Improve frontmatter types, pass generic TFrontmatter type through (#342)
697c682 remove newline from template literal (#346)
772d213 fix: TFrontmatter type to unknown (#340)
c559bdc fix(rsc): do not require compiledSource in types (#339)
1508a53 Bump decode-uri-component from 0.2.0 to 0.2.2 (#318)
e9c0275 Bump semver-regex from 2.0.0 to 3.1.4 (#313)
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/cisco-sbg-ui/atomic-react/network/alerts).

cisco-sbg-ui / atomic-react

build(deps): bump trim and next-mdx-remote #1320

v4.4.1

What's Changed

v4.4.0

What's Changed