Sorry it should work now the pipeline
# spicedb
j
Sorry -- it should work now -- the pipeline also turns releases back into drafts sometimes after they're cut
d
@jzelinskie Thanks for the quick turnaround, you folks continue to impress. And no worries at all, I was just curious and wanted to notice you folks 🙂 That said, I just started another brew upgrade and now it still downloaded the 1.22.0 rc version instead of 404'ing. Do you really want this to be brew default behaviour? I'd expect a "stable" channel to not download rc material, I'd expect to "subscribe" to a dedicated "beta" channel or sth similar to get RCs
see screenshots, this happens now when you just do "brew upgrade"
j
Sorry -- I haven't been on discord in a minute. I created this issue to track this https://github.com/authzed/spicedb/issues/1378
We've been pretty focused on production environments using containers that we've forgotten that some folks might be using these repositories directly without pinning versions. We'll gauge interest to see if it makes sense to change the policy. The advantage of keeping it this way is that folks that aren't sensitive to upgrades (they would've pinned the version) will be able to try out pre-releases.
d
no worries 🙂 and ty
@jzelinskie So, as you talk about version pinning I just tried various ways to install v1.21.0 using brew - without success, sadly. brew install spicedb@1.21.0 or brew install spicedb@v1.21.0 or ...@1.21 ...@v1.21 did not work. Searching using brew search also does not show different versions. I'd be fine if I could just specify the version, but either it's too early/I'm dumb or that's not currently possible 🙈 Could you tell me what command to use?
(and as rc4 was released, there's also the 404 again)
j
brew install authzed/tap/spicedb@1.21.0
should now work
d
thanks! Just to verify, yes, now it works 🙂