Skip to content

chore(deps): lock file maintenance - #2099

Open
renovate[bot] wants to merge 1 commit into
developfrom
renovate/lock-file-maintenance
Open

renovate[bot] wants to merge 1 commit into
developfrom
renovate/lock-file-maintenance

Conversation

@renovate

@renovate renovate Bot commented Aug 29, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Only on Sunday and Saturday (* * * * 0,6)
  • 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate
renovate Bot requested a review from a team as a code owner August 29, 2026 03:46
@renovate
renovate Bot requested a review from soleksy-splunk August 29, 2026 03:46
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 5685a51 to 2004ac3 Compare September 3, 2026 00:35
@renovate
renovate Bot requested a review from a team as a code owner September 3, 2026 00:35
@renovate
renovate Bot requested a review from sgoral-splunk September 3, 2026 00:35
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 6 times, most recently from 401f1b7 to 24c3151 Compare September 9, 2026 15:13
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 6cfe331 to 0d35bd5 Compare September 15, 2026 09:08
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from 0e40ff0 to ab3d2da Compare September 24, 2026 20:48
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from e404c67 to 28bf544 Compare October 5, 2026 19:39

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 28bf544168

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread ui/yarn.lock Outdated
Comment on lines 3189 to 3190
"@splunk/visualization-schemas@28.9.0", "@splunk/visualization-schemas@^28.9.1":
version "28.9.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Align the visualization schema resolution

The refreshed visualization packages now request @splunk/visualization-schemas ^28.9.1, but this stanza still resolves that selector to 28.9.0 because ui/package.json pins the package in resolutions. This newly introduced out-of-range override makes the dashboard visualization code run against an older schema API; bump the resolution to 28.9.1 or retain the related visualization packages at 28.9.0.

Useful? React with 👍 / 👎.

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 28bf544 to ca8a0f6 Compare October 13, 2026 13:50
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-06T13:32:14.239197Z 0713e24 New commits
🔒 Security Review ✅ Completed 2026-11-06T13:31:04.366488Z 0713e24 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ca8a0f6565

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread ui/yarn.lock
dependencies:
nanoid "^3.3.17"
nanoid "^3.3.20"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Raise nanoid to PostCSS's declared minimum

With the existing resolutions entry pinning nanoid to 3.3.18, every install now supplies PostCSS 8.5.30 a version outside its newly declared ^3.3.20 range. This leaves the UI dependency tree in an unsupported state; update the resolution to at least 3.3.20 or keep PostCSS on a release whose nanoid range includes 3.3.18.

Useful? React with 👍 / 👎.

@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from ea5bd2a to 5c938c9 Compare October 22, 2026 17:05
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 5c938c9 to 1dc326d Compare October 26, 2026 20:10
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch 3 times, most recently from a51f070 to 9bdf9d2 Compare November 5, 2026 21:54
@renovate
renovate Bot force-pushed the renovate/lock-file-maintenance branch from 9bdf9d2 to 0713e24 Compare November 6, 2026 13:28

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0713e24996

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread ui/yarn.lock
resolved "https://registry.npmjs.org/@splunk/react-page/-/react-page-8.4.0.tgz#63ede439d5a212bba6c4c33c8f9f188f7aba134d"
integrity sha512-aXwN3P+SkdpY8yzm6WESWjEVE9kdIcbwE/H8MSEYBdFXjQ+1sMRPgfB6SR0LRtB+lJ+umKsvGT1Qt52aIzEuvA==
dependencies:
"@splunk/react-ui" "^5.18.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep react-page within the pinned react-ui range

When the UI is installed, the existing resolutions entry in ui/package.json forces @splunk/react-ui to 5.15.0, so upgrading @splunk/react-page to 8.4.0 now supplies it with a version outside its declared ^5.18.0 dependency range. Either retain react-page 8.3.2 or update the react-ui pin so react-page does not run against an older, unsupported API.

Useful? React with 👍 / 👎.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants