-
Notifications
You must be signed in to change notification settings - Fork 92
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
Release request, to prevent repeated shadowed-var warnings in the REPL #197
Comments
Hi, Joel! It looks like you have a lot on your plate lately, so I'd like to offer to help on this in any way I can. Garden is an awesome library, and I appreciate all the hard work you've done to get it to where it stands now. If you need certain tasks to be done before you're comfortable pushing a release, I'd love to help. Thanks again! |
Seconding this - it would be greatly appreciated! |
Waiting for this too! |
I too am awaiting this. I wonder: is there a workaround in the meantime? |
A workaround is copying the single culprit namespace, modify it as desired and place it ahead in your classpath (e.g. in |
Seconding this... I think it may be good to fork this library and deploy to clojars until active maintenance here can resume. |
A workaround when using
Not as human-friendly as a version number, but it gets the job done. |
Hi. Sorry about this. Its been a long time since I have worked on or made a release of the library. I would use the solution proposed by @fearnoeval for now since I can't make any promises about when I can do this. |
@noprompt, would it be possible to give someone else power to make a release? It's always nicer to use a release than a git sha, if at all possible. |
Hey folks, if anyone else has a need for a clojars/mvn release, we've put out a release with all the latest changes under |
Thanks for hosting a package release!
|
thanks! :) |
Just checking in on this, would be great to have a garden release, or maybe add @plexus as a project maintainer, if he's willing? |
Requesting a new release be pushed.
Due to #194 , warnings are output in the REPL every time it is started or deps are reloaded, for users who have upgraded to Clojure 1.11. Since the issue was resolved in #195, pushing a new release would prevent these warnings.
If there's anything I can do to help, please let me know. Thanks!
The text was updated successfully, but these errors were encountered: