Skip to content

fix(deps): update dependency @scalar/nextjs-api-reference to ^0.11.0 - autoclosed#93

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/scalar-monorepo
Closed

fix(deps): update dependency @scalar/nextjs-api-reference to ^0.11.0 - autoclosed#93
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/scalar-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@scalar/nextjs-api-reference (source) ^0.10.10^0.11.0 age confidence

Release Notes

scalar/scalar (@​scalar/nextjs-api-reference)

v0.11.6

v0.11.5

v0.11.4

v0.11.3

v0.11.2

v0.11.1

v0.11.0

Minor Changes
  • #​9422: Add a nonce option for Content Security Policy support.

    When you pass a nonce, the rendered HTML stamps it onto the inline <script> and the CDN <script> tag (and Scalar's own <style> tags, plus a matching <meta property="csp-nonce">). This lets the API Reference run under a strict script-src with no unsafe-inline and no unsafe-eval.

    ApiReference({
      url: '/openapi.json',
      // Match this value in your `script-src` CSP directive.
      nonce: 'r4nd0m',
    })

    Note: style-src still needs 'unsafe-inline'. The reference renders inline style="…" attributes, which a CSP nonce can never authorize (nonces only apply to <script>, <style> and <link> elements), so a nonce-only style-src is not possible. The win is a fully strict script-src.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel

vercel Bot commented Jun 8, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
respondeo Ready Ready Preview, Comment Jun 28, 2026 9:32pm
respondeo-docs Ready Ready Preview, Comment Jun 28, 2026 9:32pm

@renovate renovate Bot force-pushed the renovate/scalar-monorepo branch from 5ff37b4 to d3cad98 Compare June 9, 2026 17:40
@renovate renovate Bot force-pushed the renovate/scalar-monorepo branch from d3cad98 to 4b6d2ad Compare June 11, 2026 13:11
@renovate renovate Bot force-pushed the renovate/scalar-monorepo branch from 4b6d2ad to e5b7355 Compare June 17, 2026 17:58
@renovate renovate Bot changed the title fix(deps): update scalar monorepo to ^0.11.0 fix(deps): update scalar monorepo Jun 22, 2026
@renovate renovate Bot force-pushed the renovate/scalar-monorepo branch from e5b7355 to 8811003 Compare June 22, 2026 22:59
@renovate renovate Bot changed the title fix(deps): update scalar monorepo fix(deps): update dependency @scalar/nextjs-api-reference to ^0.11.0 Jun 25, 2026
@renovate renovate Bot force-pushed the renovate/scalar-monorepo branch from 8811003 to 0eec048 Compare June 26, 2026 11:41
@renovate renovate Bot force-pushed the renovate/scalar-monorepo branch from 0eec048 to 6faba18 Compare June 28, 2026 17:42
@renovate renovate Bot requested a review from sebdanielsson as a code owner June 28, 2026 17:42
@renovate renovate Bot force-pushed the renovate/scalar-monorepo branch from 6faba18 to def121f Compare June 28, 2026 18:55
@renovate renovate Bot changed the title fix(deps): update dependency @scalar/nextjs-api-reference to ^0.11.0 fix(deps): update dependency @scalar/nextjs-api-reference to ^0.11.0 - autoclosed Jun 28, 2026
@renovate renovate Bot closed this Jun 28, 2026
@renovate renovate Bot deleted the renovate/scalar-monorepo branch June 28, 2026 22:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants