Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency com.slack.lint.compose:compose-lint-checks to v1.3.1 #264

Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 28, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.slack.lint.compose:compose-lint-checks 1.2.0 -> 1.3.1 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

slackhq/compose-lints (com.slack.lint.compose:compose-lint-checks)

v1.3.1

Compare Source

2024-01-25

  • Lower the lint API back to 14, not 15.

v1.3.0

Compare Source

2024-01-25

  • New: Implement ModifierComposed check to lint against use of Modifier.composed, which is no longer recommended in favor of the new Modifier.Node API.
  • New: Implement ComposeUnstableReceiver check to warn when composable extension functions or composables instance functions have unstable receivers/containing classes.
  • New: Check for property accessors with composition locals.
  • Enhancement: The ComposeComposableModifier message now recommends the new Modifier.Node API.
  • Enhancement: Make lints significantly more robust to edge cases like typealiases, import aliases, parentheses, fully-qualified references, and whitespace. Our tests now cover all these cases.
  • Enhancement: Update @Preview detection to also detect Compose Desktop's own @Preview annotation.
  • Enhancement: Improve the ComposeParameterOrder check to only lint the parameter list and add a quickfix.
  • Enhancement: Add support for checking for loops in multiple content emitters.
  • Fix: Fix allowed names config for Unit-returning functions.
  • Fix: Ignore context receivers in multiple content emissions lint.
  • Fix: Allow nullable types for trailing lambdas in ComposeParameterOrder.
  • Fix: Best-effort work around name mangling when comparing name in M2ApiDetector's allow list.
  • Fix: Fix ComposePreviewPublic to always just require private, remove preview parameter configuration.
  • Docs: Improve docs for ComposeContentEmitterReturningValues
  • Build against lint-api 31.2.2.
  • Test against lint-api 31.4.0-alpha06.
  • Raise Kotlin apiVersion/languageVersion to 1.9.0.

Special thanks to @​jzbrooks, @​joeMalebe, @​dellisd for contributing to this release!


Configuration

📅 Schedule: Branch creation - "on sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@AntsyLich
Copy link
Member

Will be remove with #216

@AntsyLich AntsyLich closed this Jan 28, 2024
@AntsyLich AntsyLich deleted the renovate/com.slack.lint.compose-compose-lint-checks-1.x branch January 28, 2024 20:48
Copy link
Contributor Author

renovate bot commented Jan 28, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (1.3.1). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants