You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Yes, we are using your library in our project, but every time you release newer version you also remove older versions from jitpack repository, which breaks our pipeline. We upgraded to newer version every time, but now, with 1.1.0 you force us to use material3, but that would enforce massive refactor to whole application.
Describe the solution you'd like
It is a good habit to keep older versions of the library available for those who don't need new features or those like us, who can't afford immediate refactor of application to material3.
Describe alternatives you've considered
As this aggressive change broke our pipeline completely, I have no other option than to remove this library from our dependencies and consider it to be a bad idea and not reliable source for future dependencies.
The text was updated successfully, but these errors were encountered:
kletzander
changed the title
Support older versions of your library
Make older versions of your library available
Nov 28, 2024
Hello @kletzander , apologies for unexpected error. I did have a quick look into this to get this resolved asap.
We usually do not remove any artifacts from the jitpack repository. But it seems like a known issue from Jitpack side where some of the old packages gets lost. Here's the mentioned issue link for the same :- jitpack/jitpack.io#5289
Please keep supporting this and let us know if you have any other queries or suggestions.
Thanks.
Is your feature request related to a problem? Please describe.
Yes, we are using your library in our project, but every time you release newer version you also remove older versions from jitpack repository, which breaks our pipeline. We upgraded to newer version every time, but now, with 1.1.0 you force us to use material3, but that would enforce massive refactor to whole application.
Describe the solution you'd like
It is a good habit to keep older versions of the library available for those who don't need new features or those like us, who can't afford immediate refactor of application to material3.
Describe alternatives you've considered
As this aggressive change broke our pipeline completely, I have no other option than to remove this library from our dependencies and consider it to be a bad idea and not reliable source for future dependencies.
The text was updated successfully, but these errors were encountered: