fix(deps): update frontend-app-runtime-tooling#148
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/frontend-app-runtime-tooling
branch
9 times, most recently
from
ad07b5b to
1452323
Compare
renovate
Bot
force-pushed
the
renovate/frontend-app-runtime-tooling
branch
6 times, most recently
from
77c2606 to
06069a5
Compare
renovate
Bot
force-pushed
the
renovate/frontend-app-runtime-tooling
branch
4 times, most recently
from
2593eb6 to
7262214
Compare
renovate
Bot
force-pushed
the
renovate/frontend-app-runtime-tooling
branch
from
7262214 to
c462d26
Compare
renovate
Bot
force-pushed
the
renovate/frontend-app-runtime-tooling
branch
2 times, most recently
from
6354990 to
3af4c94
Compare
renovate
Bot
force-pushed
the
renovate/frontend-app-runtime-tooling
branch
from
3af4c94 to
c076fbf
Compare
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:
fce4f15→224f38e87999aad8e448a→242549c10.33.0→10.34.119.2.0→19.2.619.2.719.2.0→19.2.619.2.70.83.6→0.85.3~2.30.1→~2.31.01.20.7→1.21.81.21.94.2.1→4.4.04.4.1~5.6.2→~5.8.0~4.23.0→~4.25.015.15.3→15.15.513.16.0→13.16.10.7.4→0.9.1Release Notes
pnpm/pnpm (pnpm)
v10.34.1: pnpm 10.34.1Compare Source
Patch Changes
pnpm-lock.yamlentries whose remote tarballresolution:block is missing theintegrityfield. Previously the worker that extracts a downloaded tarball skipped hash verification when no integrity was supplied and minted a fresh one from the unverified bytes, so an attacker who could both alter the lockfile (e.g. via a pull request that stripsintegrity:) and serve modified content at the referenced tarball URL could install a tampered package without any error — including under--frozen-lockfile. pnpm now fails closed at lockfile-read time withERR_PNPM_MISSING_TARBALL_INTEGRITY. Git-hosted tarballs (gitHosted: trueor a URL on codeload.github.com / bitbucket.org / gitlab.com) andfile:tarballs are exempt — the commit SHA in a git-host URL and the user-controlled local path already anchor the bytes.Platinum Sponsors
Gold Sponsors
v10.34.0: pnpm 10.34Compare Source
Minor Changes
Treat tarball-integrity mismatches against the lockfile as a hard failure by default. Previously,
pnpm install(non-frozen) would logERR_PNPM_TARBALL_INTEGRITY, silently re-resolve from the registry, and overwrite the locked integrity — which meant a compromised registry, proxy, or republished version could substitute attacker-controlled content on a clean machine even though the project shipped a committed lockfile.pnpm installnow exits withERR_PNPM_TARBALL_INTEGRITYand a hint pointing at the new opt-in flag.The only opt-in is
pnpm install --update-checksums— narrowly scoped to refreshing the locked integrity values from what the registry currently serves. Mirrors yarn's flag of the same name. A warning still prints when the bypass takes effect so the operation is auditable.--forceandpnpm updatedeliberately do not bypass the integrity check. They are routine refresh operations; silently overwriting a locked integrity in those flows would erase the protection a committed lockfile is supposed to provide.--frozen-lockfilebehavior is unchanged.--fix-lockfilekeeps its documented purpose (filling in missing lockfile entries) and is also not a bypass.Patch Changes
_authToken,_auth,username/_password,tokenHelper, inlinecert/key) to the registry declared in the same config source at load time, so a later layer overridingregistry=(workspace.npmrc,pnpm-workspace.yaml, CLI--registry) cannot redirect a credential or client certificate authored for a different host. A deprecation warning is emitted whenever an unscoped per-registry setting is encountered, naming the source and the URL it was pinned to. Reported by JUNYI LIU.minimumReleaseAgehandling when cached metadata is abbreviated. The npm registry returns abbreviated package metadata (without the per-versiontimefield) by default, which made the maturity check throwERR_PNPM_MISSING_TIMEwhenever cached abbreviated metadata was reused. pnpm now upgrades cached abbreviated metadata to the full document via a follow-up fetch whenminimumReleaseAgeis active, persists the upgrade to the on-disk cache so subsequent installs skip the extra fetch, and letsERR_PNPM_MISSING_TIMEfrom the cache fast-path fall through to the network fetch even under strict mode.commitfield is not a 40-character hexadecimal SHA before invokinggit. A malicious lockfile could otherwise smuggle a value such as--upload-pack=<command>throughgit fetch/git checkout, which on SSH or local-file transports executes the supplied command.diff --githeaders reference paths outside the patched package directory. Previously a malicious.patchfile added via a pull request could write, delete, or rename arbitrary files reachable by the user runningpnpm install.--prefix=<dir>not being honored when locating the workspace root. The--prefix → dirrename was applied after workspace detection, so workspace settings declared in<dir>/pnpm-workspace.yamlwere not loaded when pnpm was invoked from outside<dir>#11535.@x/../../../../../.git/hooks) when reading them from a package manifest or symlinking them intonode_modules. A malicious registry package could otherwise use a transitive dependency key to makepnpm installcreate symlinks at attacker-chosen paths outside the intendednode_modulesdirectory.Platinum Sponsors
Gold Sponsors
v10.33.4: pnpm 10.33.4Compare Source
Patch Changes
Pin the integrity of git-hosted tarballs (codeload.github.com, gitlab.com, bitbucket.org) in the lockfile so that subsequent installs detect a tampered or substituted tarball and refuse to install it. Previously the lockfile only stored the tarball URL for git dependencies, so a compromised git host or a man-in-the-middle could serve arbitrary code on later installs without lockfile changes.
A new
gitHosted: truefield is recorded on git-hosted tarball resolutions in the lockfile, letting every reader/writer route them by a single typed check instead of pattern-matching the tarball URL in each call site. Lockfiles written by older pnpm versions are enriched on load (URL fallback) so the field can be relied on uniformly across the codebase.Fix a regression where
pnpm --recursive --filter '!<pkg>' run/exec/test/addwould include the workspace root in the matched projects. The workspace root is now correctly excluded by default when only negative--filterarguments are provided, matching the documented behavior. To include the root, pass--include-workspace-root#11341.Platinum Sponsors
Gold Sponsors
v10.33.3Compare Source
v10.33.2Compare Source
v10.33.1: pnpm 10.33.1Compare Source
Patch Changes
packageManagerfield selects pnpm v11 or newer, commands that v10 would have passed through to npm (version,login,logout,publish,unpublish,deprecate,dist-tag,docs,ping,search,star,stars,unstar,whoami, etc.) are now handed over to the wanted pnpm, which implements them natively. Previously they silently shelled out to npm — making, for example,pnpm version --helpprint npm's help on a project withpackageManager: pnpm@11.0.0-rc.3#11328.Platinum Sponsors
Gold Sponsors
facebook/react (react)
v19.2.6: 19.2.6 (May 6th, 2026)Compare Source
React Server Components
(by @eps1lon and @unstubbable)
v19.2.5: 19.2.5 (April 8th, 2026)Compare Source
React Server Components
v19.2.4: 19.2.4 (January 26th, 2026)Compare Source
React Server Components
v19.2.3: 19.2.3 (December 11th, 2025)Compare Source
React Server Components
v19.2.2: 19.2.2 (December 11th, 2025)Compare Source
React Server Components
react-server-dom-webpack/*.unbundledto privatereact-server-dom-unbundled(@eps1lon #35290)v19.2.1: 19.2.1 (December 3rd, 2025)Compare Source
React Server Components
facebook/react-native (react-native)
v0.85.3Compare Source
v0.85.2: 0.85.2Compare Source
Hermes dSYMS:
Hermes V1 dSYMS:
ReactNativeDependencies dSYMs:
ReactNative Core dSYMs:
You can file issues or pick requests against this release here.
To help you upgrade to this version, you can use the Upgrade Helper ⚛️.
View the whole changelog in the CHANGELOG.md file.
v0.85.1: 0.85.1Compare Source
Hermes dSYMS:
Hermes V1 dSYMS:
ReactNativeDependencies dSYMs:
ReactNative Core dSYMs:
You can file issues or pick requests against this release here.
To help you upgrade to this version, you can use the Upgrade Helper ⚛️.
View the whole changelog in the CHANGELOG.md file.
v0.85.0: 0.85.0Compare Source
Hermes dSYMS:
Hermes V1 dSYMS:
ReactNativeDependencies dSYMs:
ReactNative Core dSYMs:
You can file issues or pick requests against this release here.
To help you upgrade to this version, you can use the Upgrade Helper ⚛️.
View the whole changelog in the CHANGELOG.md file.
v0.84.1: 0.84.1Compare Source
Fixed
Android specific
gradle.propertiesresolution for monorepos by reading from parent Gradle start parameters (projectDir/currentDir) before falling back to../../android/gradle.properties, sohermesV1Enabledcan be inherited correctly. (c5ae0c820a by @Titozzz)inspector-modern/chrome/Registration.hwhen HermesV1 is disabled. (5ee695ad8f by @tjzel)hermesV1Enabledtotrue(45896674d1 by @tjzel)Hermes dSYMS:
Hermes V1 dSYMS:
ReactNativeDependencies dSYMs:
ReactNative Core dSYMs:
You can file issues or pick requests against this release here.
To help you upgrade to this version, you can use the Upgrade Helper ⚛️.
View the whole changelog in the CHANGELOG.md file.
v0.84.0: 0.84.0Compare Source
Hermes dSYMS:
Hermes V1 dSYMS:
ReactNativeDependencies dSYMs:
ReactNative Core dSYMs:
You can file issues or pick requests against this release here.
To help you upgrade to this version, you can use the Upgrade Helper ⚛️.
View the whole changelog in the CHANGELOG.md file.
v0.83.9Compare Source
v0.83.8Compare Source
v0.83.7Compare Source
software-mansion/react-native-gesture-handler (react-native-gesture-handler)
v2.31.2Compare Source
🐛 Bug fixes
🔢 Miscellaneous
Full Changelog: software-mansion/react-native-gesture-handler@v2.31.1...v2.31.2
v2.31.1Compare Source
❗ Important changes
🔢 Miscellaneous
Full Changelog: software-mansion/react-native-gesture-handler@v2.31.0...v2.31.1
v2.31.0Compare Source
❗ Important changes
👍 Improvements
pointerEventsforPressablecomponent by @huextrat in #3925pointerEventsforPressablecomponent by @huextrat in #3927FullWindowOverlayas the native root by @j-piasecki in #4039Textcomponent by @m-bert in #4003numberOfPointerstoNativegesture events by @m-bert in #4023🐛 Bug fixes
handleGesture:fromReset:by @m-bert in #3983pointerTypeinHovergesture by @m-bert in #3989onFinalizecallback inTapby @m-bert in #4029🔢 Miscellaneous
exactOptionalPropertyTypessupport by @YevheniiKotyrlo in #4012expoon v2 branch by @m-bert in #4052New Contributors
Full Changelog: software-mansion/react-native-gesture-handler@v2.30.1...v2.31.0
kirillzyusko/react-native-keyboard-controller (react-native-keyboard-controller)
v1.21.8Compare Source
Fixing crashes in some edge cases 🤐
🐛 Bug fixes
38076a9)cb011a8)👍 Improvements
weakreference to keyboard view on iOS (1a6450e)🔢 Miscellaneous
6e68167)7dcd70a) by @yairopro19fc3d7)765af50)v1.21.7Compare Source
Enhancing
KeyboardChatScrollViewfunctionality and improving library stability 👍🐛 Bug fixes
viewPositionInWindow(1048f52)👍 Improvements
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.