-
Notifications
You must be signed in to change notification settings - Fork 17
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
Make older versions of your library available #68
Comments
Hello @kletzander , apologies for unexpected error. I did have a quick look into this to get this resolved asap. Please keep supporting this and let us know if you have any other queries or suggestions. |
Hi, the problem still persists.
… On 28. 11. 2024, at 14:24, Mohammed Hanif ***@***.***> wrote:
Hello @kletzander <https://github.com/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 <jitpack/jitpack.io#5289>
Please keep supporting this and let us know if you have any other queries or suggestions.
Thanks.
—
Reply to this email directly, view it on GitHub <#68 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACJLQQ37URQLDLEK3ADGTC32C4KP3AVCNFSM6AAAAABSUZKUCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBWGEZDEMZUG4>.
You are receiving this because you authored the thread.
|
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: