Skip to content

chore(deps): Bump the npm_and_yarn group across 2 directories with 3 updates#2

Open
dependabot[bot] wants to merge 1 commit into
2026from
dependabot/npm_and_yarn/plp-platform/npm_and_yarn-0b69251ac1
Open

chore(deps): Bump the npm_and_yarn group across 2 directories with 3 updates#2
dependabot[bot] wants to merge 1 commit into
2026from
dependabot/npm_and_yarn/plp-platform/npm_and_yarn-0b69251ac1

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github Dec 23, 2025

Bumps the npm_and_yarn group with 2 updates in the /plp-platform directory: next and jws.
Bumps the npm_and_yarn group with 1 update in the /plp-platform/plp_program directory: js-yaml.

Updates next from 14.2.18 to 14.2.35

Release notes

Sourced from next's releases.

v14.2.35

Please see the Next.js Security Update for information about this security patch.

Commits

Updates js-yaml from 4.1.0 to 3.14.2

Changelog

Sourced from js-yaml's changelog.

[4.1.1] - 2025-11-12

Security

  • Fix prototype pollution issue in yaml merge (<<) operator.
Commits

Updates jws from 4.0.0 to 4.0.1

Release notes

Sourced from jws's releases.

v4.0.1

Changed

  • Fix advisory GHSA-869p-cjfg-cm3x: createSign and createVerify now require that a non empty secret is provided (via opts.secret, opts.privateKey or opts.key) when using HMAC algorithms.
  • Upgrading JWA version to 2.0.1, addressing a compatibility issue for Node >= 25.
Changelog

Sourced from jws's changelog.

[4.0.1]

Changed

  • Fix advisory GHSA-869p-cjfg-cm3x: createSign and createVerify now require that a non empty secret is provided (via opts.secret, opts.privateKey or opts.key) when using HMAC algorithms.
  • Upgrading JWA version to 2.0.1, adressing a compatibility issue for Node >= 25.

[3.2.3]

Changed

  • Fix advisory GHSA-869p-cjfg-cm3x: createSign and createVerify now require that a non empty secret is provided (via opts.secret, opts.privateKey or opts.key) when using HMAC algorithms.
  • Upgrading JWA version to 1.4.2, adressing a compatibility issue for Node >= 25.

[3.0.0]

Changed

2.0.0 - 2015-01-30

Changed

  • BREAKING: Default payload encoding changed from binary to utf8. utf8 is a is a more sensible default than binary because many payloads, as far as I can tell, will contain user-facing strings that could be in any language. ([6b6de48])

  • Code reorganization, thanks [@​fearphage]! (7880050)

Added

  • Option in all relevant methods for encoding. For those few users that might be depending on a binary encoding of the messages, this is for them. ([6b6de48])

... (truncated)

Commits
  • 34c45b2 Merge commit from fork
  • 49bc39b version 4.0.1
  • d42350c Enhance tests for HMAC streaming sign and verify
  • 5cb007c Improve secretOrKey initialization in VerifyStream
  • f9a2e1c Improve secret handling in SignStream
  • b9fb8d3 Merge pull request #102 from auth0/SRE-57-Upload-opslevel-yaml
  • 95b75ee Upload OpsLevel YAML
  • 8857ee7 test: remove unused variable (#96)
  • See full diff in compare view
Maintainer changes

This version was pushed to npm by julien.wollscheid, a new releaser for jws since your current version.


Updates js-yaml from 4.1.0 to 4.1.1

Changelog

Sourced from js-yaml's changelog.

[4.1.1] - 2025-11-12

Security

  • Fix prototype pollution issue in yaml merge (<<) operator.
Commits

You can trigger a rebase of this PR 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

…updates

Bumps the npm_and_yarn group with 2 updates in the /plp-platform directory: [next](https://github.com/vercel/next.js) and [jws](https://github.com/brianloveswords/node-jws).
Bumps the npm_and_yarn group with 1 update in the /plp-platform/plp_program directory: [js-yaml](https://github.com/nodeca/js-yaml).


Updates `next` from 14.2.18 to 14.2.35
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v14.2.18...v14.2.35)

Updates `js-yaml` from 4.1.0 to 3.14.2
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@4.1.0...4.1.1)

Updates `jws` from 4.0.0 to 4.0.1
- [Release notes](https://github.com/brianloveswords/node-jws/releases)
- [Changelog](https://github.com/auth0/node-jws/blob/master/CHANGELOG.md)
- [Commits](auth0/node-jws@v4.0.0...v4.0.1)

Updates `js-yaml` from 4.1.0 to 4.1.1
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@4.1.0...4.1.1)

---
updated-dependencies:
- dependency-name: next
  dependency-version: 14.2.35
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: js-yaml
  dependency-version: 3.14.2
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: jws
  dependency-version: 4.0.1
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: js-yaml
  dependency-version: 4.1.1
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Dec 23, 2025
@aitankfish aitankfish force-pushed the dependabot/npm_and_yarn/plp-platform/npm_and_yarn-0b69251ac1 branch from 393ef7c to 96d049a Compare January 5, 2026 07:18
@netlify
Copy link
Copy Markdown

netlify Bot commented Jan 5, 2026

Deploy Preview for superb-dango-3ac646 ready!

Name Link
🔨 Latest commit 96d049a
🔍 Latest deploy log https://app.netlify.com/projects/superb-dango-3ac646/deploys/695b65c4eccf1000087943ba
😎 Deploy Preview https://deploy-preview-2--superb-dango-3ac646.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@dependabot dependabot Bot changed the base branch from main to 2026 April 22, 2026 23:53
aitankfish added a commit that referenced this pull request May 23, 2026
Two bugs and a content update in one commit.

Bug #1 — the entire /docs/build/ section was being silently dropped
from git
====
The root .gitignore had `build/` (intended to catch Next.js build
output) which matched the docs Fumadocs source dir
`apps/docs/content/docs/build/`. The existing `!docs/build/` exception
only covered the legacy Mintlify directory at the repo root, not the
Fumadocs path. Result: every file in apps/docs/content/docs/build/ —
quickstart, architecture, public-api, on-chain-program,
agent-integration, meta.json — was untracked in every branch. None
of them are in any commit. The pages that show up on
docs.pnl.market today are a stale Vercel cache from before the
gitignore broke things.

Fix: add `!apps/docs/content/docs/build/` exception. Force-add the
whole directory in this commit so future Vercel rebuilds have the
actual source.

Bug #2 — agent-integration.mdx page was stale by ~30 commits
====
The page still said "What's coming next: MCP server" and listed
`pnl_vote_intent` as a planned tool. The MCP server is shipped
v0.4.0 with 16 tools, 9 endpoints, autosign, encrypted local
wallet, claim flow, notifications. The page misrepresented the
product to anyone who landed on it.

Fix: rewrite the page around the shipped state. Tool surface table.
Trust model explained. Slash commands listed. Read-only integration
path documented for agents that don't need write access. Cards
linking to the new MCP server reference page.

New content — /docs/build/mcp-server
====
Canonical reference for @pnl/mcp-server. Install (one-shot + manual).
Full tool surface with auth model per category. Deep-link vs autosign
flows. Trust model: autosign cap (default 0.05, override can only
lower never raise), claim uncapped (withdrawal), sig-auth payload
binding (sha256 of canonical body folded into challenge), on-chain
verification. Backend endpoints listed with the challenge format
documented. Env vars (PNL_API_BASE_URL, PNL_RPC_URL, PNL_PASSPHRASE)
with override guidance. Wallet file layout. Example flow ("pitch +
notify" round-trip). Non-custodial framing tied back to the
regulatory-posture page.

Added to apps/docs/content/docs/build/meta.json nav.

README — MCP section
====
Root README's "For AI Agents & Integrators" section gains a fourth
sub-surface: the MCP server. Install snippet, tool surface count,
trust model summary, deep-links to the docs site and the apps/mcp
README. Now 4 surfaces, not 3.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants