Skip to content

chore(deps): weekly bump#796

Open
hyochan wants to merge 1 commit into
mainfrom
chore/deps-2026-05-11
Open

chore(deps): weekly bump#796
hyochan wants to merge 1 commit into
mainfrom
chore/deps-2026-05-11

Conversation

@hyochan
Copy link
Copy Markdown
Owner

@hyochan hyochan commented May 10, 2026

Summary

  • Bump React Native toolchain packages to 0.85.3.
  • Bump react-native-nitro-modules and nitrogen to 0.35.6.
  • Add @react-native/jest-preset and switch Jest to the moved preset required by React Native 0.85.
  • Regenerate Nitro bindings with yarn prepare.

Guarded paths touched

  • nitrogen/generated/** was regenerated by nitrogen@0.35.6 and needs human review before merge.

Verification

  • yarn typecheck
  • yarn lint (passes with existing Prettier warnings in scripts/generate-release-notes.js)
  • yarn test
  • yarn prepare

Summary by CodeRabbit

  • Chores
    • Updated React Native framework and development dependencies to the latest versions to ensure stability and compatibility with current tooling ecosystem.

Review Change Stack

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 10, 2026

📝 Walkthrough

Walkthrough

This PR upgrades the React Native framework and its ecosystem tooling from 0.82.1 to 0.85.3 across the monorepo. It updates both root and example package.json files with coordinated dependency bumps, introduces @react-native/jest-preset, and reconfigures Jest to use the new explicit preset package instead of a string reference.

Changes

Dependency and Configuration Upgrade

Layer / File(s) Summary
Root dependencies
package.json
Updates react-native from 0.79.2 to 0.85.3, react-native-nitro-modules from 0.35.4 to 0.35.6, @react-native/babel-preset and @react-native/eslint-config to 0.85.3, and introduces @react-native/jest-preset at 0.85.3.
Jest configuration
package.json
Changes Jest preset from string "react-native" to "@react-native/jest-preset" to reference the new explicit package dependency.
Example app dependencies
example/package.json
Mirrors root updates: bumps react-native from 0.82.1 to 0.85.3, react-native-nitro-modules from 0.35.4 to 0.35.6, and @react-native/babel-preset, @react-native/metro-config, and @react-native/typescript-config from 0.82.1 to 0.85.3.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested labels

dependencies

Poem

🐰 With React Native bumped up high,
To 0.85.3 in the sky,
Jest presets renamed with care,
Dependencies updated everywhere—
A stable foundation laid just right!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'chore(deps): weekly bump' is vague and generic, using non-descriptive terms that don't convey meaningful information about the specific dependency updates being made. Consider a more descriptive title such as 'chore(deps): bump React Native to 0.85.3 and add jest-preset' to better communicate the main changes.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/deps-2026-05-11

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 10, 2026

/gemini review

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 10, 2026

Auto-review found blockers. Push a fix or wait for human review; next daily run will re-evaluate.

  • Guarded paths touched: nitrogen/generated/** was regenerated by the Nitro toolchain bump and requires human review before this automation can approve or auto-merge.
  • CI was still in progress when reviewed by the daily automation.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
example/package.json (1)

18-18: 💤 Low value

Consider aligning React versions across workspace.

The example app uses React 19.1.1 while the root package uses 19.0.0. While this patch difference may not cause issues in a workspace setup, aligning versions can prevent potential inconsistencies and simplify dependency management.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@example/package.json` at line 18, The project has mismatched React versions
between workspaces (example package.json lists "react": "19.1.1" while root uses
"19.0.0"); update the example/package.json React dependency to match the
workspace root version (or bump the root to 19.1.1 if you intend to standardize
on that) so that the "react" entry in example/package.json and the root
package.json specify the same semantically identical version string; locate and
edit the "react" field in example/package.json to align it with the root
dependency.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Around line 99-100: Update the React dependency in package.json from "react":
"19.0.0" to a compatible version >=19.2.3 (prefer using a caret like "^19.2.3")
so it matches React Native 0.85.3's peerDependency; modify the "react" entry in
package.json accordingly and run your package manager (npm/yarn/pnpm) to
reinstall and update lockfile.

---

Nitpick comments:
In `@example/package.json`:
- Line 18: The project has mismatched React versions between workspaces (example
package.json lists "react": "19.1.1" while root uses "19.0.0"); update the
example/package.json React dependency to match the workspace root version (or
bump the root to 19.1.1 if you intend to standardize on that) so that the
"react" entry in example/package.json and the root package.json specify the same
semantically identical version string; locate and edit the "react" field in
example/package.json to align it with the root dependency.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cc1b52ba-7a37-4292-97d9-dd64396aedf7

📥 Commits

Reviewing files that changed from the base of the PR and between 53695af and cd8e562.

⛔ Files ignored due to path filters (23)
  • nitrogen/generated/android/NitroSoundOnLoad.cpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JAVEncoderAudioQualityIOSType.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JAVEncodingOption.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JAVLinearPCMBitDepthKeyIOSType.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JAVModeIOSOption.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JAudioEncoderAndroidType.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JAudioQualityType.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JAudioSet.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JAudioSourceAndroidType.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JFunc_void_PlayBackType.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JFunc_void_PlaybackEndType.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JFunc_void_RecordBackType.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JHybridSoundSpec.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JOutputFormatAndroidType.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JPlayBackType.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JPlaybackEndType.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/c++/JRecordBackType.hpp is excluded by !**/generated/**
  • nitrogen/generated/android/kotlin/com/margelo/nitro/sound/AudioSet.kt is excluded by !**/generated/**
  • nitrogen/generated/android/kotlin/com/margelo/nitro/sound/PlayBackType.kt is excluded by !**/generated/**
  • nitrogen/generated/android/kotlin/com/margelo/nitro/sound/PlaybackEndType.kt is excluded by !**/generated/**
  • nitrogen/generated/android/kotlin/com/margelo/nitro/sound/RecordBackType.kt is excluded by !**/generated/**
  • nitrogen/generated/ios/NitroSound+autolinking.rb is excluded by !**/generated/**
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (2)
  • example/package.json
  • package.json

Comment thread package.json
Comment on lines 99 to +100
"react": "19.0.0",
"react-native": "0.79.2",
"react-native": "0.85.3",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🌐 Web query:

Does React Native 0.85.3 support React 19?

💡 Result:

Yes, React Native 0.85.3 supports React 19. The package.json for React Native specifies "react": "^19.2.3" as a peerDependency [1][2][3], indicating compatibility with React 19 versions starting from 19.2.3. This aligns with earlier releases like 0.83 explicitly including React 19.2 [4], and the progression through 0.85 RCs and stable versions maintaining the same peer dependency range [5][6]. React Native 0.85.3 is a patch release with no changes to dependencies listed [5], so it inherits this support. Official docs and release notes confirm 0.85.x is active and current as of 2026-05-10 [7][8][9].

Citations:


Update React to version 19.2.3 or later for React Native 0.85.3 compatibility.

React Native 0.85.3 requires React 19.2.3+ (specified as "react": "^19.2.3" in its peerDependencies). The current version 19.0.0 is incompatible and will cause runtime errors or hook failures. Upgrade to React >=19.2.3.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` around lines 99 - 100, Update the React dependency in
package.json from "react": "19.0.0" to a compatible version >=19.2.3 (prefer
using a caret like "^19.2.3") so it matches React Native 0.85.3's
peerDependency; modify the "react" entry in package.json accordingly and run
your package manager (npm/yarn/pnpm) to reinstall and update lockfile.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request upgrades React Native to version 0.85.3 and Nitro modules to 0.35.6, alongside updating various dependencies and build configurations. Key changes include syntax adjustments in generated C++ files and the addition of manual equals and hashCode overrides in generated Kotlin data classes. Feedback indicates that these manual overrides are redundant for Kotlin data classes and introduce performance overhead through unnecessary object allocation and boxing; it is recommended to update the generator to rely on default language behavior.

Comment on lines +78 to +122
override fun equals(other: Any?): Boolean {
if (this === other) return true
if (other !is AudioSet) return false
return Objects.deepEquals(this.AVEncoderAudioQualityKeyIOS, other.AVEncoderAudioQualityKeyIOS)
&& Objects.deepEquals(this.AVModeIOS, other.AVModeIOS)
&& Objects.deepEquals(this.AVEncodingOptionIOS, other.AVEncodingOptionIOS)
&& Objects.deepEquals(this.AVFormatIDKeyIOS, other.AVFormatIDKeyIOS)
&& Objects.deepEquals(this.AVNumberOfChannelsKeyIOS, other.AVNumberOfChannelsKeyIOS)
&& Objects.deepEquals(this.AVLinearPCMBitDepthKeyIOS, other.AVLinearPCMBitDepthKeyIOS)
&& Objects.deepEquals(this.AVLinearPCMIsBigEndianKeyIOS, other.AVLinearPCMIsBigEndianKeyIOS)
&& Objects.deepEquals(this.AVLinearPCMIsFloatKeyIOS, other.AVLinearPCMIsFloatKeyIOS)
&& Objects.deepEquals(this.AVLinearPCMIsNonInterleavedIOS, other.AVLinearPCMIsNonInterleavedIOS)
&& Objects.deepEquals(this.AVSampleRateKeyIOS, other.AVSampleRateKeyIOS)
&& Objects.deepEquals(this.AudioSourceAndroid, other.AudioSourceAndroid)
&& Objects.deepEquals(this.OutputFormatAndroid, other.OutputFormatAndroid)
&& Objects.deepEquals(this.AudioEncoderAndroid, other.AudioEncoderAndroid)
&& Objects.deepEquals(this.AudioQuality, other.AudioQuality)
&& Objects.deepEquals(this.AudioChannels, other.AudioChannels)
&& Objects.deepEquals(this.AudioSamplingRate, other.AudioSamplingRate)
&& Objects.deepEquals(this.AudioEncodingBitRate, other.AudioEncodingBitRate)
&& Objects.deepEquals(this.IncludeBase64, other.IncludeBase64)
}

override fun hashCode(): Int {
return arrayOf(
AVEncoderAudioQualityKeyIOS,
AVModeIOS,
AVEncodingOptionIOS,
AVFormatIDKeyIOS,
AVNumberOfChannelsKeyIOS,
AVLinearPCMBitDepthKeyIOS,
AVLinearPCMIsBigEndianKeyIOS,
AVLinearPCMIsFloatKeyIOS,
AVLinearPCMIsNonInterleavedIOS,
AVSampleRateKeyIOS,
AudioSourceAndroid,
OutputFormatAndroid,
AudioEncoderAndroid,
AudioQuality,
AudioChannels,
AudioSamplingRate,
AudioEncodingBitRate,
IncludeBase64
).contentDeepHashCode()
}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The manual overrides for equals and hashCode in this data class are sub-optimal for performance and likely redundant.

  1. Redundancy: Kotlin data class automatically generates equals and hashCode based on primary constructor properties. Unless these properties are arrays (which require contentDeepEquals/HashCode), the manual implementation is unnecessary.
  2. Performance: The hashCode implementation creates a new Array<Any?> and boxes all primitive fields (like AudioChannels or IncludeBase64) on every call. This is inefficient and increases GC pressure.
  3. Idiomatic Kotlin: Using java.util.Objects.deepEquals is less idiomatic than the standard == operator, which correctly handles nulls and value equality for standard types.

Since this is generated code, consider updating the nitrogen generator to either rely on default data class behavior or use a more efficient implementation (e.g., java.util.Objects.hash() or a manual field-by-field hash computation). This issue also affects PlayBackType.kt, PlaybackEndType.kt, and RecordBackType.kt.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the project to React Native 0.85.3 and Nitro modules 0.35.6, alongside various dependency updates and modifications to generated C++, Kotlin, and iOS autolinking code. The review identifies a version mismatch for the react dependency between the root and example package.json files, which may cause runtime issues. Additionally, the manual equals and hashCode overrides in the generated Kotlin data classes are flagged as redundant and inefficient compared to standard compiler-generated implementations.

Comment thread example/package.json
@@ -17,8 +17,8 @@
"@react-native-community/slider": "^5.2.0",
"react": "19.1.1",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

There is a version mismatch for react between the root package.json (19.0.0) and the example/package.json (19.1.1). In React Native projects, having multiple versions of React in the same dependency tree can lead to runtime issues like the 'Invalid hook call' error. It is recommended to synchronize these versions to ensure a single React instance is used throughout the project.

Comment on lines +78 to +122
override fun equals(other: Any?): Boolean {
if (this === other) return true
if (other !is AudioSet) return false
return Objects.deepEquals(this.AVEncoderAudioQualityKeyIOS, other.AVEncoderAudioQualityKeyIOS)
&& Objects.deepEquals(this.AVModeIOS, other.AVModeIOS)
&& Objects.deepEquals(this.AVEncodingOptionIOS, other.AVEncodingOptionIOS)
&& Objects.deepEquals(this.AVFormatIDKeyIOS, other.AVFormatIDKeyIOS)
&& Objects.deepEquals(this.AVNumberOfChannelsKeyIOS, other.AVNumberOfChannelsKeyIOS)
&& Objects.deepEquals(this.AVLinearPCMBitDepthKeyIOS, other.AVLinearPCMBitDepthKeyIOS)
&& Objects.deepEquals(this.AVLinearPCMIsBigEndianKeyIOS, other.AVLinearPCMIsBigEndianKeyIOS)
&& Objects.deepEquals(this.AVLinearPCMIsFloatKeyIOS, other.AVLinearPCMIsFloatKeyIOS)
&& Objects.deepEquals(this.AVLinearPCMIsNonInterleavedIOS, other.AVLinearPCMIsNonInterleavedIOS)
&& Objects.deepEquals(this.AVSampleRateKeyIOS, other.AVSampleRateKeyIOS)
&& Objects.deepEquals(this.AudioSourceAndroid, other.AudioSourceAndroid)
&& Objects.deepEquals(this.OutputFormatAndroid, other.OutputFormatAndroid)
&& Objects.deepEquals(this.AudioEncoderAndroid, other.AudioEncoderAndroid)
&& Objects.deepEquals(this.AudioQuality, other.AudioQuality)
&& Objects.deepEquals(this.AudioChannels, other.AudioChannels)
&& Objects.deepEquals(this.AudioSamplingRate, other.AudioSamplingRate)
&& Objects.deepEquals(this.AudioEncodingBitRate, other.AudioEncodingBitRate)
&& Objects.deepEquals(this.IncludeBase64, other.IncludeBase64)
}

override fun hashCode(): Int {
return arrayOf(
AVEncoderAudioQualityKeyIOS,
AVModeIOS,
AVEncodingOptionIOS,
AVFormatIDKeyIOS,
AVNumberOfChannelsKeyIOS,
AVLinearPCMBitDepthKeyIOS,
AVLinearPCMIsBigEndianKeyIOS,
AVLinearPCMIsFloatKeyIOS,
AVLinearPCMIsNonInterleavedIOS,
AVSampleRateKeyIOS,
AudioSourceAndroid,
OutputFormatAndroid,
AudioEncoderAndroid,
AudioQuality,
AudioChannels,
AudioSamplingRate,
AudioEncodingBitRate,
IncludeBase64
).contentDeepHashCode()
}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The manual overrides for equals and hashCode in this data class appear redundant and less efficient than the compiler-generated versions. Since the properties are standard types (primitives, strings, etc.) and not arrays, Kotlin's default data class implementation already provides correct equality and hashing logic. The current hashCode implementation is particularly suboptimal as it allocates a new Array on every call. If this is a change in the nitrogen generator, it is recommended to only generate these overrides when the class contains Array properties that require deep equality checks.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates React Native to version 0.85.3 and Nitro modules to 0.35.6 across the main package and example project. It includes refinements to C++ constant declarations and an iOS build configuration change to disable auto-generated ObjC headers. Feedback was provided concerning the manual equals and hashCode overrides in generated Kotlin data classes, highlighting that these implementations are less efficient than the default compiler-generated versions due to unnecessary object allocations and deep comparison overhead.

Comment on lines +78 to +122
override fun equals(other: Any?): Boolean {
if (this === other) return true
if (other !is AudioSet) return false
return Objects.deepEquals(this.AVEncoderAudioQualityKeyIOS, other.AVEncoderAudioQualityKeyIOS)
&& Objects.deepEquals(this.AVModeIOS, other.AVModeIOS)
&& Objects.deepEquals(this.AVEncodingOptionIOS, other.AVEncodingOptionIOS)
&& Objects.deepEquals(this.AVFormatIDKeyIOS, other.AVFormatIDKeyIOS)
&& Objects.deepEquals(this.AVNumberOfChannelsKeyIOS, other.AVNumberOfChannelsKeyIOS)
&& Objects.deepEquals(this.AVLinearPCMBitDepthKeyIOS, other.AVLinearPCMBitDepthKeyIOS)
&& Objects.deepEquals(this.AVLinearPCMIsBigEndianKeyIOS, other.AVLinearPCMIsBigEndianKeyIOS)
&& Objects.deepEquals(this.AVLinearPCMIsFloatKeyIOS, other.AVLinearPCMIsFloatKeyIOS)
&& Objects.deepEquals(this.AVLinearPCMIsNonInterleavedIOS, other.AVLinearPCMIsNonInterleavedIOS)
&& Objects.deepEquals(this.AVSampleRateKeyIOS, other.AVSampleRateKeyIOS)
&& Objects.deepEquals(this.AudioSourceAndroid, other.AudioSourceAndroid)
&& Objects.deepEquals(this.OutputFormatAndroid, other.OutputFormatAndroid)
&& Objects.deepEquals(this.AudioEncoderAndroid, other.AudioEncoderAndroid)
&& Objects.deepEquals(this.AudioQuality, other.AudioQuality)
&& Objects.deepEquals(this.AudioChannels, other.AudioChannels)
&& Objects.deepEquals(this.AudioSamplingRate, other.AudioSamplingRate)
&& Objects.deepEquals(this.AudioEncodingBitRate, other.AudioEncodingBitRate)
&& Objects.deepEquals(this.IncludeBase64, other.IncludeBase64)
}

override fun hashCode(): Int {
return arrayOf(
AVEncoderAudioQualityKeyIOS,
AVModeIOS,
AVEncodingOptionIOS,
AVFormatIDKeyIOS,
AVNumberOfChannelsKeyIOS,
AVLinearPCMBitDepthKeyIOS,
AVLinearPCMIsBigEndianKeyIOS,
AVLinearPCMIsFloatKeyIOS,
AVLinearPCMIsNonInterleavedIOS,
AVSampleRateKeyIOS,
AudioSourceAndroid,
OutputFormatAndroid,
AudioEncoderAndroid,
AudioQuality,
AudioChannels,
AudioSamplingRate,
AudioEncodingBitRate,
IncludeBase64
).contentDeepHashCode()
}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The manual overrides for equals and hashCode are inefficient. Objects.deepEquals is significantly slower than standard equality checks for non-array types because it performs multiple internal type checks. Furthermore, arrayOf(...).contentDeepHashCode() allocates a new array on every invocation of hashCode. For a data class, unless these properties are specifically arrays that require deep comparison (which is unlikely for these specific field names), it is better to rely on the default compiler-generated implementations or use more efficient alternatives like Objects.hash() to avoid unnecessary allocations.

Copy link
Copy Markdown
Owner Author

hyochan commented May 11, 2026

Auto-review found blockers on this daily re-check. Push a fix or wait for human review; next daily run will re-evaluate.

  • Guarded paths touched: nitrogen/generated/** was regenerated by the Nitro toolchain bump and requires human review before this automation can approve or auto-merge.
  • Bot findings remain actionable: CodeRabbit flagged React 19.2.3+ compatibility for React Native 0.85.3, and Gemini/CodeRabbit flagged generated Kotlin equals/hashCode overhead in nitrogen/generated/android/kotlin/**.
  • CI is now green on cd8e562, but green CI does not override the guarded-path gate.
  • Copilot PR Reviewer unavailable: GitHub rejected copilot-pull-request-reviewer as a non-collaborator.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 13, 2026

Daily re-check (2026-05-13 KST): still blocked by the guarded-path gate.

  • CI is green and merge state is CLEAN on cd8e56202da45360cb70b57eec1b79baa06ef6a8.
  • Gemini and CodeRabbit have reviewed this HEAD.
  • This PR touches nitrogen/generated/**, so the daily automation will not approve or enable auto-merge without human review.

Next action: human review/approval of the generated Nitro output, then the automation can re-evaluate on the next run.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 13, 2026

Daily re-check (2026-05-14 KST): still blocked by the guarded-path gate.

  • CI is green and merge state is CLEAN on cd8e56202da45360cb70b57eec1b79baa06ef6a8.
  • Gemini and CodeRabbit have reviewed this HEAD; Copilot PR reviewer remains unavailable/not requested.
  • The PR touches nitrogen/generated/**, which the automation must not approve or auto-merge without human review.

Auto-review found blockers. Push a fix or wait for human review; next daily run will re-evaluate.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 13, 2026

Daily re-check (2026-05-14 KST): still blocked by the guarded-path gate.

  • CI is green and merge state is CLEAN on cd8e56202da45360cb70b57eec1b79baa06ef6a8.
  • Gemini and CodeRabbit have reviewed this HEAD; Copilot PR Reviewer is unavailable for this repo.
  • This PR touches nitrogen/generated/**, which the daily runbook marks as human-review-only.
  • Because this is a self-authored PR for the automation token, I cannot request changes through GitHub review. Leaving this blocker comment instead and not approving or enabling auto-merge.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 15, 2026

Daily re-check (2026-05-15 KST): still blocked by the guarded-path gate.

  • CI is green and merge state is CLEAN on cd8e562.
  • The PR touches guarded generated files under nitrogen/generated/**, so automation will not approve or enable auto-merge.
  • Human maintainer review is required before this can progress.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 15, 2026

Daily re-check (2026-05-16 KST): still blocked by the guarded-path gate.

  • CI is green and merge state is CLEAN on cd8e562.
  • Gemini and CodeRabbit reviewed the current HEAD; CodeRabbit/Gemini still have review comments recorded.
  • Copilot reviewer request is unavailable: copilot-pull-request-reviewer is not a repository collaborator.
  • The PR touches guarded generated files under nitrogen/generated/**, so this automation cannot approve or auto-merge it. Human review is required.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 16, 2026

Daily re-check (2026-05-17 KST): still blocked by the guarded-path gate.

  • CI is green and merge state is CLEAN on cd8e562.
  • Gemini and CodeRabbit have reviewed the current HEAD and still have review comments.
  • Copilot PR Reviewer is unavailable for this repository, so this remains a 2-bot loop.
  • This PR touches guarded generated files under nitrogen/generated/**, so automation will not approve or auto-merge it without human review.
  • Self-authored PR: automation cannot submit a request-changes review, so this comment records the blocker instead.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 17, 2026

Daily re-check (2026-05-18 KST): still blocked by the guarded-path gate.

  • CI is green and merge state is CLEAN on cd8e562.
  • Gemini and CodeRabbit have reviewed this HEAD; Copilot reviewer is unavailable/not installed for this repo.
  • The PR touches guarded generated files under nitrogen/generated/**, so the automation cannot approve or auto-merge it. Human review is required before merge.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 17, 2026

Daily re-check (2026-05-18 KST): still blocked by the guarded-path gate.

  • CI is green and merge state is CLEAN on cd8e562.
  • Gemini and CodeRabbit reviewed the current HEAD; Copilot PR Reviewer is unavailable for this repository, so this remains a 2-bot loop.
  • This PR touches guarded generated files under nitrogen/generated/**, so automation will not approve or auto-merge it without human review.
  • Self-authored PR: automation cannot submit a request-changes review, so this comment records the blocker instead.
  • Monday dependency check found the same eligible core bumps already represented by this PR; no new dependency branch was opened.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 18, 2026

Daily re-check (2026-05-19 KST): still blocked by the guarded-path gate.

  • CI is green and merge state is CLEAN on cd8e562.
  • The PR touches guarded generated bindings under nitrogen/generated/**, which requires human review before automation can progress.
  • Because this is a self-PR, automation cannot submit a request-changes review; treating this comment as the blocking review note.

No auto-merge attempted.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 20, 2026

Daily re-check (2026-05-20 KST): still blocked by the guarded-path gate.

  • CI is green and merge state is CLEAN on cd8e562.
  • Gemini and CodeRabbit reviewed the current HEAD; Copilot PR Reviewer remains unavailable for this repository.
  • This PR touches guarded generated bindings under nitrogen/generated/**, which requires human review before automation can approve or enable auto-merge.
  • Because this is a self-PR for the automation token, automation cannot submit a request-changes review; treating this comment as the blocking review note.

No auto-merge attempted.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 20, 2026

Daily re-check (2026-05-20 KST): still blocked by the guarded-path gate.

  • CI is green and merge state is CLEAN on cd8e562.
  • Gemini and CodeRabbit have reviewed the current HEAD; Copilot PR Reviewer remains unavailable for this repository.
  • The PR touches guarded generated files under nitrogen/generated/**, so this automation cannot approve or enable auto-merge without human review.
  • Self-authored PR: automation cannot submit a request-changes review, so this comment records the blocker instead.

No auto-merge attempted.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 21, 2026

Daily re-check (2026-05-21 KST): still blocked by automated review gates.

  • mergeStateStatus is now DIRTY, so this PR cannot be progressed automatically.
  • The PR touches guarded generated bindings under nitrogen/generated/**, which requires human review before merge.
  • Self-PR branch: posting this blocker comment instead of submitting a request-changes review.

Auto-review found blockers. Push a fix or rebase/update the branch; next daily run will re-evaluate.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 21, 2026

Daily re-check (2026-05-21 KST): still blocked by automation gates.

  • Merge state is DIRTY; rebase or resolve conflicts against main before this can progress.
  • The PR touches guarded generated files under nitrogen/generated/**, which requires human review before automation can merge.
  • CI is green on cd8e562, and existing Gemini/CodeRabbit reviews are noted; no bot re-kick was needed today.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 22, 2026

Auto-review found blockers. Push a fix; next daily run will re-evaluate.

  • mergeStateStatus is DIRTY, so the branch must be updated before automation can progress it.
  • The PR touches guarded generated files under nitrogen/generated/**, which require human review under the daily triage runbook.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 22, 2026

Daily re-check (2026-05-23 KST): still blocked by automation gates.

  • mergeStateStatus is DIRTY, so the branch must be updated or conflicts resolved before automation can progress it.
  • The PR touches guarded generated files under nitrogen/generated/**, which require human review under the daily triage runbook.
  • Self-authored PR: automation cannot submit a request-changes review, so this comment records the blocker instead.

No auto-merge attempted.

@hyochan
Copy link
Copy Markdown
Owner Author

hyochan commented May 23, 2026

Daily re-check (2026-05-23 KST): still blocked by automation gates.

  • mergeStateStatus is DIRTY; rebase or resolve conflicts against main before automation can progress this PR.
  • The PR touches guarded generated files under nitrogen/generated/**, so it still requires human review even though CI is green.
  • Gemini and CodeRabbit have reviewed the current HEAD; Copilot PR Reviewer remains unavailable for this repository.

Push a fix or wait for human review; the next daily run will re-evaluate.

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.

1 participant