-
Notifications
You must be signed in to change notification settings - Fork 14
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
Version checking thinks "RELEASE" is not up-to-date #11
Comments
Did this go away when you tried out one of the newer master commits for v2.0.0, out of interest? |
Hard to tell -- v2 doesn't work with our work repo setup! |
I just noticed that If that works, I'll go over our dev tooling and see if we still use RELEASE and then re-check this. |
No, it does not work yet. It is not paying any attention to the user-level |
Sorry I completely forgot about this issue and the changes @lverns submitted, I need to get this across the line really so the master branch has a released tag. Wondering what needs to be done to finish it off, guessing it's still an issue? |
It's no longer an issue for me -- I no longer use Depot. |
Completely understandable! 😄 this tool definitely needs some love, just got to find the time and energy to do it. I'll leave this open as a note for now, would be worth bearing in mind with any changes or rewrites. |
In case you're curious, I ended up doing it via a fairly simple shell script that ran |
Oooo I really like that! Thanks for the tip!
…On Tue, 26 May 2020, 16:32 Sean Corfield, ***@***.***> wrote:
In case you're curious, I ended up doing it via a fairly simple shell
script that ran clojure -Stree on my code and edited the output into a
new deps.edn in a temp folder with "RELEASE" in place of the actual
versions, then ran clojure -Stree on that "project" and compared the
output with the original deps tree (I can filter deps by depth so I can
exclusive some or all transient deps).
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#11 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACM6XPXSCHI3AMUKZDKUMTRTPOIBANCNFSM4GFGNF2A>
.
|
This is kind of a follow on from #7 but for the checking side of Depot, rather than the updating side: the version checker reports that
"RELEASE"
is out of date compared to whatever the latest stable release actually is.As noted in that other ticket, we only use
"RELEASE"
for dev/test tooling where we always want to ensure we're always on the most recent release, without needing any manual process to update dependencies.The text was updated successfully, but these errors were encountered: