Update all #17
Open
Update all #17
Conversation
This file contains 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
oscarg798
force-pushed
the
renovate/all
branch
5 times, most recently
from
07e6f93 to
a08dc81
Compare
oscarg798
force-pushed
the
renovate/all
branch
from
a08dc81 to
c804bd5
Compare
oscarg798
force-pushed
the
master
branch
3 times, most recently
from
3a6a3bc to
6e5659b
Compare
oscarg798
force-pushed
the
master
branch
2 times, most recently
from
ebbb9b0 to
ec994be
Compare
# for free
to join this conversation on GitHub.
Already have an account?
# 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:
1.4.4->1.4.81.4.4->1.4.80.7.0->0.7.40.23.0->0.23.10.23.0->0.23.10.23.0->0.23.10.23.0->0.23.10.23.0->0.23.10.6.1->0.6.30.13.2->1.0.10.13.2->1.6.04.0.0->5.0.12.10.3->2.10.132.10.9.1->2.10.12.21.4.0->1.4.11.12.0->1.12.21.12.0->1.12.21.0.0-beta02->1.0.01.0.0-alpha07->2.4.12.8.6->2.9.02.2.1->2.2.22.26.3->2.27.23.16.1->3.22.02.0.34->2.0.361.4.0->1.5.02.6->2.8.13.2.0->4.0.03.12.4->4.3.13.12.4->4.3.14.12.0->4.13.14.12.0->4.13.14.12.0->4.13.14.6.2->4.6.44.6.2->4.6.41.0.0-alpha02->1.0.0-beta011.3.6->1.4.11.3.6->1.4.12.3.1->2.4.12.3.1->2.4.12.3.1->2.4.12.4.0-alpha02->2.4.12.3.1->2.4.12.4.0->2.4.11.3.0->1.4.07.1.1->7.1.21.1.1->1.2.02.1.0->2.1.31.3.0-rc02->1.4.01.4.0->1.4.1Release Notes
skydoves/landscapist
v1.4.8Compare Source
What's Changed
Full Changelog: skydoves/landscapist@1.4.7...1.4.8
v1.4.7Compare Source
What's Changed
4.13.0and AGP to7.1.0by @skydoves in https://github.com/skydoves/landscapist/pull/106Full Changelog: skydoves/landscapist@1.4.6...1.4.7
v1.4.6Compare Source
🎉 Released a new version
1.4.6! 🎉What's Changed
Full Changelog: skydoves/landscapist@1.4.5...1.4.6
v1.4.5Compare Source
What's Changed
Full Changelog: skydoves/landscapist@1.4.4...1.4.5
google/accompanist
v0.23.1What's Changed
vanpra/compose-material-dialogs
v0.6.3Compare Source
v0.6.2Compare Source
arrow-kt/arrow
v1.0.1Compare Source
What's Changed
getOrElseby @codymikol in https://github.com/arrow-kt/arrow/pull/2548New Contributors
Full Changelog: arrow-kt/arrow@1.0.0...1.0.1
v1.0.0Compare Source
1.0.0 (2021-09-20)
Option-related ext. functions (#2436) [Azim Muradov]composeandplusmethods across the lenses (#2415) [Mitchell Skaggs]v0.13.3Compare Source
0.13.3 (2021-09-20)
airbnb/lottie-android
v5.0.1New Features
[Removed API] Removed the
setScale(float)APIs fromLottieAnimationViewandLottieDrawable. The expected behavior was highly ambiguous when paired with other scale types and canvas transformations. For the vast majority of cases, ImageView.ScaleType should be sufficient. For remaining cases, you may apply transformations to Canvas and useLottieDrawable#drawdirectly.Added support for the "Rounded Corners" effect on Shape and Rect layers (#1953)
Prior to 5.0, LottieAnimationView would always call setLayerType with either HARDWARE or SOFTWARE. In the hardware case, this would case Android to allocate a dedicated hardware buffer for the animation that had to be uploaded to the GPU separately. In the software case, LottieAnimationView would rely on View's internal drawing cache.
This has a few disadvantages:
choose a render mode.
Benefits as a result of this change:
Lottie can now render outside of its composition bounds. To allow this with views such as LottieAnimationView, set
clipToCompositionBoundsto false onLottieDrawableorLottieAnimationViewandclipChildrento false on the parent view. For Compose, use theclipToCompositionBoundsparameter.Prior to 5.0, LottieAnimationView handled all animation controls when the view's visibility or attach state changed. This worked fine for consumers of LottieAnimationView. However, custom uses of LottieDrawable were prone to leaking infinite animators if they did not properly handle cancelling animations correctly. This opens up the possibility for unexpected behavior and increased battery drain. Lottie now behaves more like animated drawables in the platform and moves this logic into the Drawable via its setVisible API. This should lead to no explicit behavior changes if you are using LottieAnimationView. However, if you are using LottieDrawable directly and were explicitly pausing/cancelling animations on lifecycle changes, you may want to cross check your expected behavior with that of LottieDrawable after this update. This change also resolved a long standing bug when Lottie is used in RecyclerViews due to the complex way in which RecyclerView handles View lifecycles (#1495).
#1981
Add an API setClipToCompositionBounds on LottieAnimationView, LottieDrawable, and the LottieAnimation composable to prevent Lottie from clipping animations to the composition bounds.
Add an API to always render dynamically set bitmaps at the original animation bounds. Previously, dynamically set bitmaps would be rendered at their own size anchored to the top left
of the original bitmap. This meant that if you wanted to supply a lower resolution bitmap to save memory, it would render smaller. The default behavior remains the same but you can
enable setMaintainOriginalImageBounds to be able to supply lower resolution bitmaps (#1706).
Add support for
LottieProperty.TEXTto use dynamic properties for text. This enables dynamic text support for lottie-compose (#1995).Add getters for Marker fields (#1998)
Add support for reversed polystar paths (#2003)
Bugs Fixed
v4.2.2Bugs Fixed
v4.2.1Features and Improvements
Bugs Fixed
v4.2.0v4.1.0BREAKING CHANGES
Before this release, drop shadows and blurs were completely ignored. They will now be rendered. In most cases, they will now be rendered correctly. However, you should read the implementation details here if they are not.
JodaOrg/joda-time
v2.10.13See the change notes for more information.
v2.10.12See the change notes for more information.
v2.10.11See the change notes for more information.
v2.10.10See the change notes for more information.
v2.10.9See the change notes for more information.
v2.10.8See the change notes for more information.
v2.10.7See the change notes for more information.
v2.10.6See the change notes for more information.
v2.10.5See the change notes for more information.
v2.10.4See the change notes for more information.
dlew/joda-time-android
v2.10.12.2v2.10.12.1v2.10.12mockk/mockk
v1.12.2Compare Source
andThenJust, thanks @NWuenschev1.12.1unmockkAllinside theMockKExtension, thanks @gmazzogoogle/gson
v2.9.0The minimum supported Java version changes from 6 to 7.
module-info.classinto Multi-Release JAR folder (#2013)maintained anymore (#2063)
GsonBuilder.disableJdkUnsafe()(#1904)UPPER_CASE_WITH_UNDERSCORESin FieldNamingPolicy (#2024)Gson.newJsonWriterignoring lenient and HTML-safe setting (#1989)FieldNamingPolicy.upperCaseFirstLetteruppercasing non-letter (#2004)v2.8.9sun.miscoptional (#1993).Gson.excluder()exposing internalExcluderclass (#1986).RuntimeTypeAdapterFactorydepending on internalStreamsclass (#1959).java.sqloptional (#1707).v2.8.8Unsafeif there is a security manager (#1712).EnumTypeAdapternow works better when ProGuard has obfuscated enum fields (#1495).v2.8.7ISO8601UtilsTestfailing on systems with UTC+X.JsonStreamParser.IllegalStateExceptioninJsonTreeWriter(#1592).JsonArray.isEmpty()(#1640).rubensousa/GravitySnapHelper
v2.2.2Compare Source
GravitySnapRecyclerViewwhen Gravity.CENTER is used.tomakehurst/wiremock
v2.27.2Compare Source
v2.27.1Compare Source
v2.27.0Compare Source
queueit/android-webui-sdk
v2.0.36Compare Source
Release notes:
queueDisabledInfoBreaking changes:
onQueueDisabledcallback was changed. Its signature looks like this now:v2.0.35Compare Source
Release notes:
Two new methods have been added to the QueueITEngine class:
A new callback was added in
QueueListener,onSessionRestart. With that callback, you can restart the queue session for the user, by runningrun,runWithToken, orrunWithKeymaterial-components/material-components-android
v1.5.0Compare Source
What's new since 1.4.0
Material3themes, styles, and functionality! Check out the following resources for more information:Dividercomponent (Docs)Other highlights
Badgingbd4914d)BottomAppBar0ed7c76)34740b6)BottomNavigationView943c4f0)BottomSheeta38d2d8)Chipc08a07d)CollapsingToolbarLayout655dde0)9ebf1a1)af35dfb)5c14772)841f229)f0ce498)f0ac362)3ad232d)MaterialButtonc5c7a74)153fdee)MaterialDatePickercb5d622)eb7b114)281688a)8fda897)Snackbar58ceeab)b0558dc](https://github.com/material-components/materiaConfiguration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Renovate Bot.