merge temp/9.13.0 into deps/jni-0.15.x#3516
Merged
buenaflor merged 58 commits intodeps/jni-0.15.xfrom Feb 16, 2026
Merged
Conversation
Bumps [actions/cache](https://github.com/actions/cache) from 4 to 5. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](actions/cache@v4...v5) --- updated-dependencies: - dependency-name: actions/cache dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 5 to 6. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v5...v6) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* feat(logging): introduce SentryDebugLogger for enhanced diagnostic logging This commit adds a new `SentryDebugLogger` class to provide a lightweight, isolate-compatible logging solution for the Sentry SDK. The logger supports various log levels and can be configured for each isolate. Additionally, it integrates with `SentryOptions` to enable logging based on the debug flag and diagnostic level. The existing `IsolateLogger` has been removed in favor of this new implementation, streamlining the logging process across the SDK. - Added `SentryDebugLogger` for structured logging. - Updated `SentryOptions` to configure the logger based on debug settings. - Replaced instances of `IsolateLogger` with `SentryDebugLogger` in relevant files. - Added unit tests for the new logger functionality. * refactor(sentry): remove debug logger warning from Sentry initialization This commit removes a debug logger warning message from the Sentry class during initialization. The change helps to clean up the logging output and streamline the initialization process without affecting functionality. * docs(debug_logger): update example usage and clarify instance requirements This commit updates the documentation for the `SentryDebugLogger` to reflect the correct variable name in the example and adds a note emphasizing that each package should have at least one top-level instance of the logger. This enhances clarity for users implementing the logger in their applications. * refactor(sentry): remove unused debug logger import and enhance debug logger documentation This commit removes the unused import of the debug logger from the Sentry class and adds an internal annotation to the `SentryDebugLogger` in the debug logger file. Additionally, a comment is added in the isolate worker to suppress a lint warning related to the internal member usage, improving code clarity and maintainability. * refactor(sentry): remove unused debug logger import from sentry_options.dart This commit removes the unused import of the debug logger from the `sentry_options.dart` file, contributing to cleaner code and improved maintainability. * docs(debug_logger): correct example usage in documentation This commit updates the example usage in the `SentryDebugLogger` documentation to reflect the correct variable name, enhancing clarity for users implementing the logger in their applications. * Update * refactor(debug_logger): remove unused category parameter from logging methods This commit simplifies the `SentryDebugLogger` class by removing the unused `category` parameter from the `debug`, `info`, `warning`, `error`, and `fatal` logging methods. This change enhances code clarity and reduces unnecessary complexity in the logging interface. * refactor(debug_logger_test): remove test for category logging This commit removes the test case that checks logging with a category parameter from the `debug_logger_test.dart` file. This change aligns with the recent refactor of the `SentryDebugLogger` class, which eliminated the unused category parameter, thereby enhancing the clarity and relevance of the test suite. * refactor(android_replay_handler): enhance debug logging with context This commit updates the logging statements in the `_AndroidReplayHandler` class to include the debug name from the configuration. This change improves the clarity of log messages by providing context for unexpected messages and payload types, aiding in debugging and monitoring efforts. * refactor(debug_logger_test): enhance test coverage and improve naming conventions This commit refactors the `debug_logger_test.dart` file by renaming test groups for clarity and adding new tests to verify the behavior of `SentryOptions.debug` and `SentryOptions.diagnosticLevel`. The changes improve the organization and comprehensiveness of the test suite, ensuring better validation of the `SentryDebugLogger` configuration and logging functionality. * refactor(sentry_options): improve debug logger configuration and diagnostic level handling This commit refactors the `SentryOptions` class to enhance the configuration of the debug logger. The `diagnosticLevel` setter now updates the logger's minimum level dynamically, ensuring that changes to the diagnostic level are reflected immediately. Additionally, the debug logger configuration is encapsulated in a private method for better organization and clarity. * refactor(logging): replace SentryDebugLogger with SentryInternalLogger and enhance logging functionality This commit refactors the logging mechanism by replacing the `SentryDebugLogger` with the new `SentryInternalLogger` across the codebase. The `SentryInternalLogger` provides improved logging capabilities, including compile-time constants for release, profile, and debug modes, ensuring better tree-shaking and performance. Additionally, the associated tests have been updated to validate the new logger's behavior, enhancing overall logging clarity and maintainability. * refactor(logging): remove SentryDebugLogger and its import from the codebase This commit removes the `SentryDebugLogger` class and its associated import from `sentry_options.dart`, streamlining the logging functionality in the Sentry SDK. This change is part of the ongoing effort to enhance the logging mechanism by transitioning to the `SentryInternalLogger`, which offers improved capabilities and performance. * refactor(sentry_options): update logger configuration methods to use SentryInternalLogger This commit modifies the `SentryOptions` class to replace calls to the deprecated `_configureDebugLogger` method with `_configureInternalLogger`. This change aligns with the recent transition to the `SentryInternalLogger`, ensuring consistent logging configuration and improving overall code clarity. * refactor(logging): rename debugLogger to internalLogger for consistency This commit renames the `debugLogger` to `internalLogger` across the codebase, including tests and various components. This change aligns with the recent transition to the `SentryInternalLogger`, ensuring consistent naming and improving clarity in the logging functionality. * refactor(logging): remove debugLogger test and update logging references to internalLogger This commit removes the test for the `debugLogger` constant in `internal_logger_test.dart` and updates references from `debugLogger` to `internalLogger` in the `_AndroidEnvelopeHandler` and `_AndroidReplayHandler` classes. These changes ensure consistency in the logging implementation and align with the recent transition to the `SentryInternalLogger`. * refactor(logging): move _defaultLogOutput method to SentryInternalLogger This commit relocates the `_defaultLogOutput` method into the `SentryInternalLogger` class, enhancing the organization of the logging functionality. This change improves code clarity and aligns with the ongoing refactor to streamline the logging mechanism within the Sentry SDK. * refactor(logging): improve error logging format in isolate_worker This commit enhances the error logging format in the `isolate_worker.dart` file by improving the readability of the log statement. The changes ensure that the error and stack trace are clearly separated, contributing to better debugging and monitoring of isolate message handling failures.
…Sdk` is disabled (#3420) * Update * Update CHANGELOG * Enhance AndroidEnvelopeSender to buffer envelopes when worker is not started and flush them upon starting. Update tests to reflect new buffering behavior and log changes from warning to info level. * Refactor SentryNativeJava tests: Split tests into separate files for VM and web environments. Introduce new test file for SentryNativeJava with ReplaySizeAdjustment and EnvelopeSender initialization tests. Remove redundant web stubs and streamline imports. * Refactor AndroidEnvelopeSender: Remove pending envelopes buffering and streamline envelope capture logic. Ensure envelopes are sent directly when the worker is available, and adjust logging for envelope capture in the main isolate. Update SentryNativeJava to start the envelope sender conditionally. * Enhance AndroidEnvelopeSender to manage closed state and improve envelope capture logic. Introduce a flag to prevent envelope capture after closure and update logging to use a required logger parameter. Adjust tests to reflect changes in behavior when the worker is not started. * Refactor AndroidEnvelopeSender: Adjust captureEnvelope method to ensure client assignment occurs after closed state check. This change improves clarity and maintains the integrity of the envelope sending process. * Fix AndroidEnvelopeSender start method to prevent spawning a worker if already closed. Update tests to reflect the expected spawn count when the sender is closed. * Update Android envelope capture test to assert behavior when the native channel is unavailable. Introduced a matcher for improved error handling in the captureEnvelope method. * Refactor AndroidEnvelopeSender start method to ensure proper closure handling during worker spawning. Introduce a guard clause to close the worker if the sender is already closed, enhancing stability and preventing resource leaks. * Refactor AndroidEnvelopeSender test to clarify logging behavior when sending envelopes in the main isolate. Update test description for improved readability and understanding of the expected functionality. * refactor(AndroidEnvelopeSender): update constructor to use SentryOptions and improve logging This commit refactors the `AndroidEnvelopeSender` class to replace the `_options` parameter with `SentryOptions` in the constructor. It also enhances the logging mechanism by utilizing `internalLogger` for logging messages related to envelope capture. The `_captureEnvelope` method has been updated to streamline error handling and improve clarity in logging, ensuring better maintainability and consistency across the codebase. * refactor(AndroidEnvelopeSender test): enhance logging configuration for envelope sending This commit updates the logging mechanism in the `AndroidEnvelopeSender` test to utilize the new `SentryInternalLogger`. The changes include removing the previous debug options and configuring the logger to capture logs with improved structure and clarity. This refactor aims to enhance the maintainability and consistency of logging behavior during envelope sending in the main isolate.
* Update * Refine test naming conventions in AGENTS.md for improved clarity and structure - Updated guidelines to ensure test group and test names read as coherent sentences. - Introduced a structured approach for naming by depth, emphasizing the use of subjects, contexts, variants, and behaviors. - Added examples and anti-patterns to illustrate best practices in test organization and naming. * Enhance Dart code design guidelines in AGENTS.md - Added comprehensive guidelines for identifiers, ordering, formatting, comments, and documentation to improve code consistency and readability. - Included best practices for naming conventions, code structure, and documentation styles to align with the Effective Dart guide. - Emphasized the importance of adhering to these guidelines for new and modified tests. * Refactor AGENTS.md for improved clarity and structure - Streamlined project structure section by removing table format for a more concise list format. - Updated environment section to include specific Flutter and Dart versions. - Enhanced testing guidelines with clearer commands and descriptions for Dart and Flutter packages. - Added new guidelines for modern Dart language features to promote clarity and reduce boilerplate in code. * Enhance agent documentation and testing guidelines - Updated AGENTS.md to clarify the structure and purpose of the Sentry Dart/Flutter SDK. - Introduced new documentation files for code guidelines and test conventions, emphasizing best practices for Dart/Flutter development. - Added detailed sections on naming conventions, test structure, and the use of modern Dart features to improve code clarity and maintainability. - Ensured that all new and modified code adheres to these updated guidelines for consistency across the project. * Update documentation comments guidelines in code-guidelines.md - Renamed section from "Doc Comments" to "Documentation Comments" for clarity. - Added recommendations for when to write comments, emphasizing the importance of self-documenting code. - Included specific guidelines on documenting public APIs and non-obvious reasoning, while advising against commenting on obvious behavior and providing excessive inline commentary.
Bumps [aws-sdk-s3](https://github.com/aws/aws-sdk-ruby) from 1.203.0 to 1.208.0. - [Release notes](https://github.com/aws/aws-sdk-ruby/releases) - [Changelog](https://github.com/aws/aws-sdk-ruby/blob/version-3/gems/aws-sdk-s3/CHANGELOG.md) - [Commits](https://github.com/aws/aws-sdk-ruby/commits) --- updated-dependencies: - dependency-name: aws-sdk-s3 dependency-version: 1.208.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [aws-sdk-s3](https://github.com/aws/aws-sdk-ruby) from 1.203.0 to 1.208.0. - [Release notes](https://github.com/aws/aws-sdk-ruby/releases) - [Changelog](https://github.com/aws/aws-sdk-ruby/blob/version-3/gems/aws-sdk-s3/CHANGELOG.md) - [Commits](https://github.com/aws/aws-sdk-ruby/commits) --- updated-dependencies: - dependency-name: aws-sdk-s3 dependency-version: 1.208.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [ruby/setup-ruby](https://github.com/ruby/setup-ruby) from 1.268.0 to 1.278.0. - [Release notes](https://github.com/ruby/setup-ruby/releases) - [Changelog](https://github.com/ruby/setup-ruby/blob/master/release.rb) - [Commits](ruby/setup-ruby@8aeb6ff...4c24fa5) --- updated-dependencies: - dependency-name: ruby/setup-ruby dependency-version: 1.278.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: GitHub <noreply@github.com>
Bumps [reactivecircus/android-emulator-runner](https://github.com/reactivecircus/android-emulator-runner) from 2.34.0 to 2.35.0. - [Release notes](https://github.com/reactivecircus/android-emulator-runner/releases) - [Changelog](https://github.com/ReactiveCircus/android-emulator-runner/blob/main/CHANGELOG.md) - [Commits](ReactiveCircus/android-emulator-runner@1dcd009...b530d96) --- updated-dependencies: - dependency-name: reactivecircus/android-emulator-runner dependency-version: 2.35.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Giancarlo Buenaflor <giancarlo_buenaflor@yahoo.com>
Co-authored-by: GitHub <noreply@github.com>
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v4...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Giancarlo Buenaflor <giancarlo_buenaflor@yahoo.com>
…her` (#3448) * Add TelemetryProcessor for span and log buffering Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Remove SpanV2 and TraceLifecycle dependencies - Remove addSpan method from TelemetryProcessor interface - Remove span buffer from DefaultTelemetryProcessor - Remove captureSpan method from SentryClient - Remove traceLifecycle property from SentryOptions - Remove span imports and exports - Update mocks to remove span-related code Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Remove span-related tests from sentry_client_test Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Remove span-related processor tests Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Remove span import from Flutter mocks Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * Fix wiring up * Update * Update * Update CHANGELOG * Update * Remove logbatcher * Polish --------- Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
* chore: update metrics/flutter.properties to 3.38.7 * update * update * Update --------- Co-authored-by: GitHub <noreply@github.com> Co-authored-by: Giancarlo Buenaflor <giancarlobuenaflor97@gmail.com>
* update kotlin version handling in android build scripts for CI compatibility * Fix Kotlin version format in workflow file * Update * Update * Update * Remove CI override comment for Kotlin language version Removed comment about allowing CI to override Kotlin language version.
* Fix analyze * Fix analyze * Fix analyze * Fix analyze * Fix analyze * Fix analyze * Fix analyze * Fix analyze * Fix analyze * Fix analyze * Refactor Pana score check logic in analyze.yml
Add .claude/settings.local.json to .gitignore to prevent committing local Claude Code configuration.
…3451) Co-authored-by: GitHub <noreply@github.com>
Adds trace connected metrics feature to Dart --------- Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
…irst (#3463) Make log implementation consistent with metrics and span-first Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
Bumps [actions/setup-java](https://github.com/actions/setup-java) from 4 to 5. - [Release notes](https://github.com/actions/setup-java/releases) - [Commits](actions/setup-java@v4...v5) --- updated-dependencies: - dependency-name: actions/setup-java dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…3472) Add a new `captureNativeFailedRequests` option to control native HTTP failed request capturing independently from `captureFailedRequests`. This separation allows users to: - Keep Dart-side failed request capturing enabled while disabling native - Or vice versa, based on their needs For backwards compatibility, `captureNativeFailedRequests` defaults to `null`, which falls back to the value of `captureFailedRequests`. This ensures existing users who set `captureFailedRequests = false` will still have native capturing disabled as expected.
Bumps [ruby/setup-ruby](https://github.com/ruby/setup-ruby) from 1.278.0 to 1.286.0. - [Release notes](https://github.com/ruby/setup-ruby/releases) - [Changelog](https://github.com/ruby/setup-ruby/blob/master/release.rb) - [Commits](ruby/setup-ruby@4c24fa5...90be115) --- updated-dependencies: - dependency-name: ruby/setup-ruby dependency-version: 1.286.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* fix(dart): Catch client exceptions in HttpTransport.send Prevents unhandled exceptions like `ClientException: Connection closed before full header was received` from crashing the host application. The error is logged via internalLogger and only rethrown in automatedTestMode. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Update * Update CHANGELOG * Update * Update * Implement lost event recording in HttpTransport for network errors Enhance the HttpTransport class to record lost events when a network error occurs during envelope transmission. This includes logging discarded events for both Sentry transactions and spans. Add corresponding tests to verify the functionality when client exceptions are thrown. * Refactor lost event handling in HttpTransport and TransportUtils Consolidate lost event recording logic into TransportUtils for better reusability. Update HttpTransport to utilize the new method for recording lost events on network errors. Enhance logging for response statuses, including rate limit handling. Remove redundant lost event recording method from HttpTransport. * Update * Update * Rename to recordLostEvents --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
* Update CHANGELOG * Revise CHANGELOG for enhancements and dependencies Updated CHANGELOG to reflect enhancements and dependency bumps.
…3476) Co-authored-by: GitHub <noreply@github.com>
Co-authored-by: GitHub <noreply@github.com>
…viewing dependency updates (#3509) * Update BUGBOT.md
* chore: update packages/flutter/scripts/update-android.sh to 8.32.0 * Add spotlight as debugImplementation * Update analyze * Updat * Update android example sdk targets * Update --------- Co-authored-by: GitHub <noreply@github.com> Co-authored-by: Giancarlo Buenaflor <giancarlo_buenaflor@yahoo.com> Co-authored-by: Giancarlo Buenaflor <giancarlobuenaflor97@gmail.com>
* feat: Synchronize PropagationContext to native SDKs (#3406) Native crashes/errors on Android and iOS carry their own independently- generated traceId, disconnecting them from the Dart-side trace. This wires up the existing native setTrace APIs so the Dart PropagationContext is synced to native on init and whenever generateNewTrace() is called. - Add OnTraceReset lifecycle event dispatched from Hub.generateNewTrace() - Add NativeTraceSyncIntegration that subscribes to OnTraceReset and calls the platform-specific native setTrace API - Implement setTrace on all platform bindings (JNI for Android, method channel for Cocoa, no-op for C/Web) - Add supportsTraceSync capability flag to SentryNativeBinding - Disable native auto trace ID generation on Android so Flutter is the single source of truth - Add setTrace handler in iOS SentryFlutterPlugin.swift - Register NativeTraceSyncIntegration in default integrations Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix build * Update CHANGELOG * Update * Update * Update * Update * Fix mocks * Update * Update doc * Fix changelog * Update * Review * Update * Bubble up error from native flutter plugin in swift * Move enableNativeTraceSync from dart to flutter options * Fix duplicate result * Improve documentation --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* chore: update packages/flutter/scripts/update-native.sh to 0.12.6 * Update gitignore --------- Co-authored-by: GitHub <noreply@github.com> Co-authored-by: Giancarlo Buenaflor <giancarlobuenaflor97@gmail.com>
…cking (#3508) * feat(dart): Add `features` list to `SdkVersion` metadata Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat(flutter): Merge native SDK features into event metadata Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat(flutter): Report SPM vs CocoaPods build type as SDK feature on iOS Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Review * Remove redundant comments --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
🚨 Detected changes in high risk code 🚨High-risk code has higher potential to break the SDK and may be hard to test. To prevent severe bugs, apply the rollout process for releasing such changes and be extra careful when changing and reviewing these files:
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR merges version 9.13.0 into the deps/jni-0.15.x branch, representing a substantial SDK update with major architectural changes to the tracing and telemetry systems.
Changes:
- Version bump from 9.9.1 to 9.13.0 across all packages
- Major refactoring: Introduction of InstrumentationSpan abstraction layer replacing direct ISentrySpan usage
- Telemetry system overhaul: LogBatcher replaced with TelemetryProcessor, SentryLogger split into separate logger and metrics APIs
- Native SDK updates: Android 8.28.0→8.32.0, Cocoa 8.56.2 (unchanged), JavaScript 10.6.0→10.38.0, Native 0.10.0→0.12.6
- New native trace synchronization feature for iOS/macOS/Android
Reviewed changes
Copilot reviewed 245 out of 249 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| packages/dart/lib/src/tracing/instrumentation/* | New instrumentation abstraction layer |
| packages/dart/lib/src/telemetry/* | Complete telemetry system rewrite |
| packages//lib/src/ | Integration updates to use InstrumentationSpanFactory |
| packages/flutter/lib/src/integrations/* | New NativeTraceSyncIntegration and ReplayTelemetryIntegration |
| packages/flutter/android/build.gradle | Android SDK 8.28.0→8.32.0, added sentry-spotlight |
| packages/flutter/ios/* | Swift implementation of setTrace for native sync |
| test files | Extensive test updates for new telemetry system |
| .github/workflows/* | CI/CD updates including new Kotlin compatibility workflow |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
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.
#skip-changelog