ci(deps): update maintenance dependency rollup (v1.8.x) - abandoned#354
Open
renovate[bot] wants to merge 1 commit into
Open
ci(deps): update maintenance dependency rollup (v1.8.x) - abandoned#354renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/v1.8.x-maintenance-deps
branch
6 times, most recently
from
345569c to
514c2da
Compare
renovate
Bot
force-pushed
the
renovate/v1.8.x-maintenance-deps
branch
5 times, most recently
from
51920cd to
5ed809c
Compare
renovate
Bot
force-pushed
the
renovate/v1.8.x-maintenance-deps
branch
9 times, most recently
from
09ed77a to
e6b1c67
Compare
renovate
Bot
force-pushed
the
renovate/v1.8.x-maintenance-deps
branch
5 times, most recently
from
f804638 to
04fdd70
Compare
renovate
Bot
force-pushed
the
renovate/v1.8.x-maintenance-deps
branch
2 times, most recently
from
4679e60 to
7f2d928
Compare
renovate
Bot
force-pushed
the
renovate/v1.8.x-maintenance-deps
branch
4 times, most recently
from
0839d75 to
048a7e3
Compare
renovate
Bot
force-pushed
the
renovate/v1.8.x-maintenance-deps
branch
4 times, most recently
from
8653b56 to
c526282
Compare
renovate
Bot
force-pushed
the
renovate/v1.8.x-maintenance-deps
branch
from
c526282 to
f2f41ed
Compare
renovate
Bot
changed the title
Contributor
Author
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.9.2→3.10.13.9.2→3.10.13.9.2→3.10.13.9.2→3.10.13.9.2→3.10.13.9.2→3.10.13.2.0→3.3.1v6.3.0→v6.4.011.0.4→11.0.611.1.1(+4)v6.0.0→v6.0.5v6.0.8(+2)19.2.4→19.2.519.2.619.2.4→19.2.519.2.66.0.2→6.0.31.10.0→1.11.01.10.0→1.11.06.2.3→6.3.01.13.469→1.14.4732.13.2→2.14.08.3.0→8.4.02.1.0→2.1.1Release Notes
facebook/docusaurus (@docusaurus/core)
v3.10.1Compare Source
🐛 Bug Fix
docusaurus-bundler🔧 Maintenance
docusaurusCommitters: 1
v3.10.0Compare Source
🚀 New Feature
docusaurus-types,docusaurusfuture.v4.mdx1CompatDisabledByDefaultflag (@slorber)siteConfig.storageto stable + addfuture.v4.siteStorageNamespacingflag [Claude] (@slorber)create-docusaurus.mdxextension and strict MDX syntax (@slorber)create-docusaurus,docusaurus-bundler,docusaurus-plugin-content-blog,docusaurus-plugin-content-docs,docusaurus-plugin-content-pages,docusaurus-plugin-pwa,docusaurus-types,docusaurusdocusaurus-mdx-loader,docusaurus-utils,docusauruswrite-heading-idsCLI now supports the--syntaxand--migrateoptions (@slorber)docusaurus-mdx-loaderheadingIdbased on MD/MDX comments (@slorber)docusaurus-theme-live-codeblock,docusaurus-theme-translationspositionprop (@NPX2218)docusaurus-theme-classic,docusaurus-theme-common<DocCard>, improve extensibility, better handling of emoji icons, stable classNames (@slorber)<Tabs>, allow custom<TabItem>components (@slorber)docusaurus-faster,docusaurusdocusaurus-plugin-content-pagesdocusaurus-mdx-loader,docusaurus-theme-classicdocusaurus-theme-classicdocusaurus-theme-search-algoliacreate-docusaurus,docusaurus-plugin-content-blog,docusaurus-plugin-content-docs,docusaurus-plugin-content-pages,docusaurus-plugin-sitemap,docusaurus-types,docusaurus-utils,docusaurusfuture.experimental_vcsAPI +future.experimental_faster.gitEagerVcsflag (@slorber)🐛 Bug Fix
docusaurusurl.resolve()Node.js deprecation warning (@slorber)write-heading-idsCLI when no files provided (@slorber)isInternalUrl(), URI protocol scheme detection should implement the spec more strictly (@slorber)docusaurus-faster,docusauruscreate-docusaurus,docusaurus-logger,docusaurus-plugin-content-blog,docusaurus-plugin-content-docs,docusaurus-plugin-google-gtag,docusaurus-plugin-pwa,docusaurusdocusaurus-utilsdocusaurus-theme-classicdocusaurus-plugin-content-docsdocusaurus-plugin-google-gtagdocusaurus-theme-search-algoliadocusaurus-plugin-content-blog/blog/authors/<author>/page/2(@slorber)blogListPaginatedattribute (@slorber)docusaurus-theme-classic,docusaurus-theme-commonuseKeyboardNavigationhook (@nmggithub)docusaurus-plugin-ideal-image<IdealImage>should forward remaining props to the underlying component (@tempoz)eslint-pluginno-untranslated-textrule options (@andreww2012)docusaurus-mdx-loaderdocusaurus-bundler,docusaurus-faster,docusaurus-theme-mermaid🏃♀️ Performance
docusaurus-plugin-content-blogcreate-docusaurus,docusaurus-utils,docusauruscreate-docusaurus📝 Documentation
docusaurus🤖 Dependencies
docusaurus-bundler,docusaurus-mdx-loader🔧 Maintenance
mdx1Compat.commentson our site (@slorber)git backfillcommand (@slorber)create-docusaurus,docusaurus-babel,docusaurus-bundler,docusaurus-cssnano-preset,docusaurus-faster,docusaurus-logger,docusaurus-mdx-loader,docusaurus-module-type-aliases,docusaurus-plugin-client-redirects,docusaurus-plugin-content-blog,docusaurus-plugin-content-docs,docusaurus-plugin-content-pages,docusaurus-plugin-css-cascade-layers,docusaurus-plugin-debug,docusaurus-plugin-google-analytics,docusaurus-plugin-google-gtag,docusaurus-plugin-google-tag-manager,docusaurus-plugin-ideal-image,docusaurus-plugin-pwa,docusaurus-plugin-rsdoctor,docusaurus-plugin-sitemap,docusaurus-plugin-svgr,docusaurus-plugin-vercel-analytics,docusaurus-preset-classic,docusaurus-remark-plugin-npm2yarn,docusaurus-theme-classic,docusaurus-theme-common,docusaurus-theme-live-codeblock,docusaurus-theme-mermaid,docusaurus-theme-search-algolia,docusaurus-theme-translations,docusaurus-tsconfig,docusaurus-types,docusaurus-utils-common,docusaurus-utils-validation,docusaurus-utils,docusaurus,eslint-plugin,lqip-loader,stylelint-copyrightdocusaurus-plugin-content-docs,docusaurus-plugin-ideal-image,docusaurus-theme-classic,docusaurus-theme-common,docusaurus-theme-mermaid,docusaurus-utils,docusaurusdocusaurus-cssnano-preset,docusaurus-logger,docusaurus-mdx-loader,docusaurus-plugin-client-redirects,docusaurus-plugin-content-blog,docusaurus-plugin-content-docs,docusaurus-plugin-content-pages,docusaurus-plugin-ideal-image,docusaurus-remark-plugin-npm2yarn,docusaurus-theme-classic,docusaurus-theme-common,docusaurus-utils-validation,docusaurus-utils,docusaurusdocusaurus-theme-classic,docusaurus-theme-common,docusaurusdocusaurus-babeldocusaurus-plugin-content-blog🌐 Translations
docusaurus-theme-translationsCommitters: 41
FortAwesome/react-fontawesome (@fortawesome/react-fontawesome)
v3.3.1Compare Source
Chores
v3.3.0Compare Source
Features
Chores
CI/CD
actions/setup-node (actions/setup-node)
v6.4.0Compare Source
pnpm/pnpm (pnpm)
v11.0.6Compare Source
Patch Changes
pnpm_config_npmrc_auth_fileandpnpm_config_userconfigenv vars not actually loading the custom.npmrc. The env vars were parsed and assigned to the resolved config, but only afterloadNpmrcConfighad already read the default~/.npmrc— so the custom file path was set but never read. The relevant env vars are now consulted before the user-level.npmrcis loaded #11465.pnpm-workspace.yamlwhen updating it. Existing keys keep their position, and new keys are inserted in alphabetical position when the existing keys are already sorted (with a leadingpackageskey allowed) or appended at the end otherwise.pnpm self-updateon installations originally set up by pnpm v10. v10 addedPNPM_HOMEdirectly to PATH and wrote apnpmbootstrap shim there. v11 setup writes shims underPNPM_HOME/bininstead, so when a v10 user upgrades to v11 the legacy shim atPNPM_HOMEkeeps pointing into the old.tools/<version>install —pnpm --versioncontinues to report the pre-update version even though the new version was installed underglobal/v11. Self-update now detects this layout, refreshes the legacy shims so the upgrade actually takes effect, and prints a hint suggestingpnpm setupto migrate PATH to the v11 layout. #11464.nodeLinker,hoistPattern) are present inconfig.yamland silently ignored. Previously these settings were dropped without any feedback, leaving users unsure why their global configuration had no effect. The warning suggests moving those settings to a project-levelpnpm-workspace.yaml, or sharing them across projects via config dependencies.overrideshas an invalid shape or contains a non-string value.readPackagedependency map fields, includingdevDependencies, and reject falsy non-object invalid values instead of silently accepting them.pnpm config,pnpm set, andpnpm getby toleratingconfigDependenciesinstall failures. For these commands, a failure to installconfigDependencies(for example because the registry auth token has not been written yet) is now logged at debug level and the command proceeds. All other commands still surface the install error #10684.allowBuildsas an install-state input and clear previously ignored builds when they are explicitly disallowed.catalog:protocol with thepnpm dlx/pnpxcommand, resulting in a catalog entry not found error.PNPM_CONFIG_*(uppercase) environment variables in addition topnpm_config_*. Previously, only the lowercase form was honored, so env vars renamed per the v11 migration guide (e.g.PNPM_CONFIG_USERCONFIG) silently had no effect on case-sensitive systems like macOS and Linux #11465.v11.0.5Compare Source
Patch Changes
Drop the
darwin-x64artifact from@pnpm/exeand from the GitHub release page. The Node.js SEA mechanismpnpm pack-appuses produces a binary that segfaults at startup on Intel Macs because of an upstream Node.js bug (nodejs/node#62893, tracked alongside #59553; the Node.js team has opted not to fix it on the grounds that x64 macOS is being phased out). Re-signing withcodesignorldiddoesn't help — the corruption is in LIEF's Mach-O surgery, before signing.Intel Mac users should install pnpm via
npm install -g pnpm(uses the system Node.js, no SEA), or stay on pnpm 10.x.@pnpm/exe's preinstall on Intel Mac now exits with a clear error pointing at these alternatives.Closes #11423.
pnpm dlx(andpnpx/pnx/pnpm create) now runs the same interactiveapprove-buildsprompt aspnpm add -gwhen the package being launched depends on transitive packages with install scripts. Previously, the v11strictDepBuildsdefault made dlx fail withERR_PNPM_IGNORED_BUILDSand required users to re-run with--allow-build=<pkg>for every offending dependency. dlx also now removes the partially-populated cache directory when the install fails, so a subsequent run starts clean instead of reusing a broken install whose builds were silently skipped #11444.72629fc: Fixpnpm -g ls --jsonandpnpm -g ls --parseableso they emit valid JSON and parseable output respectively, matching pnpm 10 behavior. Since the isolated global packages refactor in pnpm 11, the global list command had a custom path that always printed plain text and ignored--json/--parseable, which broke tools likenpm-check-updatesthat parse the JSON output #11440.pnpm -g ls --depth=<n>(with n > 0) now errors when more than one isolated global install would be involved, since each install has its own lockfile and merging their transitive trees would be incoherent. When the request can be narrowed to a single install group, the regularlistflow is used and the full dependency tree is shown.Fixed
pnpm publishto honorpublishConfig.registryfrompackage.jsonwhen publishing a single package. The native publish flow introduced in v11 was reading the registry from.npmrconly, ignoring the per-package override #11419.When
strictPeerDependenciesistrue, theERR_PNPM_PEER_DEP_ISSUESerror once again renders the peer dependency issues inline using the same format aspnpm peers check, so users (and CI tools like Renovate) can see what failed without runningpnpm peers checkseparately #11439.The
WARNand error code labels in pnpm's output now wrap in brackets ([WARN],[ERR_PNPM_FOO]). Previously the labels relied entirely on a colored background to stand out, which meant they blended into the surrounding text in terminals without color (e.g. whenNO_COLORis set or output is piped). The brackets are painted in the same color as the badge background, so they appear as ordinary padding in color-capable terminals — only the no-color rendering changes.pnpm/action-setup (pnpm/action-setup)
v6.0.5Compare Source
What's Changed
Full Changelog: pnpm/action-setup@v6.0.4...v6.0.5
v6.0.4Compare Source
What's Changed
New Contributors
Full Changelog: pnpm/action-setup@v6.0.3...v6.0.4
v6.0.3Compare Source
Updated pnpm to v11.0.0-rc.5
Full Changelog: pnpm/action-setup@v6.0.2...v6.0.3
v6.0.2Compare Source
What's Changed
New Contributors
Full Changelog: pnpm/action-setup@v6.0.1...v6.0.2
v6.0.1Compare Source
Update pnpm to v11.0.0-rc.2.
pnpm-lock.yamlwill not be saved with two documents unless thepackageManageris set viadevEngines.packageManager. Related issue: #228facebook/react (react)
v19.2.5: 19.2.5 (April 8th, 2026)Compare Source
React Server Components
microsoft/TypeScript (typescript)
v6.0.3Compare Source
Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)
v1.11.0==================
This release is based on Kotlin 2.3.20 and provides new Json exceptions API and some bugfixes and improvements.
Expose Json exceptions structure
To make working with exceptions easier and providing proper error codes in e.g., REST APIs,
classes
JsonException,JsonDecodingException, andJsonEncodingExceptionare now public.They have relevant public properties, such as
shortMessage,path,offset, and others.This API is currently experimental, and we're going to improve it further in the subsequent releases.
See the linked issues for the details: #1930, #1877.
Ability to hide user input from exception messages for security/privacy reasons.
Historically, exception messages in kotlinx.serialization often included the input Json itself for debuggability reason.
Such behavior may pose additional challenges for logging, analytics, and other systems, since
a system is not always allowed to store user data due to privacy/security reasons, which imposes additional sanitation logic.
To address this issue, a new property
exceptionsWithDebugInfois added toJsonConfiguration.Disable it to hide user input from exception messages.
IMPORTANT: This behavior will be enabled by default when this property becomes stable.
See #2590 for more details.
Bugfixes and improvements
mockito/mockito-kotlin (org.mockito.kotlin:mockito-kotlin)
v6.3.0Changelog generated by Shipkit Changelog Gradle Plugin
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.