Skip to content
Danger

fix(compose): add isImportantForBounds() to SentryTagModifierNode for compose-ui 1.11+ #18025

Sign in to view logs

fix(compose): add isImportantForBounds() to SentryTagModifierNode for compose-ui 1.11+

fix(compose): add isImportantForBounds() to SentryTagModifierNode for compose-ui 1.11+ #18025

Triggered via pull request July 2, 2026 02:12
@tsushanthtsushanth
opened #5672
tsushanth:fix/sentry-compose-isimportantforbounds-1-11
Status Failure
Total duration 38s
Artifacts –

danger.yml

on: pull_request
danger
34s
danger
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 2 warnings, and 1 notice
danger
Process completed with exit code 1.
danger: CHANGELOG.md#L0
Please consider adding a changelog entry for the next release.
danger
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
danger
Running from a forked repo. Danger won't be able to post comments and workflow status on the main repo, printing directly.
danger: CHANGELOG.md#L0
### Instructions and example for changelog Please add an entry to `CHANGELOG.md` to the "Unreleased" section. Make sure the entry includes this PR's number. Example: ```markdown ## Unreleased ### Fixes - add isImportantForBounds() to SentryTagModifierNode for compose-ui 1.11+ ([#5672](https://github.com/getsentry/sentry-java/pull/5672)) ``` If none of the above apply, you can opt out of this check by adding `#skip-changelog` to the PR description or adding a `skip-changelog` label.