hey all - I use the self-hosted version, i’m very ...
# infisical-feedback
g
hey all - I use the self-hosted version, i’m very confused by the new versioning scheme for releases, and I’m hoping I can get some clarity? Traditionally, nightly releases result in a final “stable” release, but it looks like it’s the other way around with infisical? Here’s what I mean: Traditional: Firefox Nightly
144.0-a1-2025-09-03
,
04
,
05
, etc… until it ultimately becomes Firefox
144
. Infisical: Infisical
v0.147.1
, and then
v0.147.1-nightly-20250815
, up to
-nightly-20250902
, and then after that
v0.148.0
My main confusion is that
nightly
versions normally signal to users that they are unstable, but it looks like it’s potentially the other way around w/ infisical release versioning? i.e.
v0.148.0
is unstable, and it gets progressively more stable as more
nightly
versions build upon it. Under normal circumstances, I would expect a new version to start with
nightly-whatever
, e.g.
v0.149.0-nightly-20250904
, and once it’s stable, a release named
v0.149.0
is published. Whilst it’s great to see such active development, the versioning scheme makes it very difficult for me to know which version is “safe” and “stable” to use. Thanks for reading through this, I really do love infisical.
I read the docs re: release channels, and from what I can tell, this is what happens:
v.0.147.0-nightly-….
versions will “graduate” to a stable
v0.148.0
version. After that,
v0.148.0-nightly-…
versions will start releasing which will graduate into
v0.149.0
stable. I think it would be worthwhile clarifying this distinction in the docs, as most people will be expecting nightly versions to work differently.
m
Hi @Gabriel Fortuna, thank you for the feedback. We have a document for our release channel here https://infisical.com/docs/self-hosting/guides/releases. It looks like we may need to clear up some of the terminology to make this more intuitive cc: @Carlos Monastyrski
a
Hi team, We were trying to use Infisical SDK with our Python code but found that all the sdks are archived and no longer maintained. Has the team no longer plans for maintain sdks? If not, how can one integrate Infisical in their workflows?
c
Hey @Abhishek Jain! We actually do support a Python SDK. Were you maybe referring to this one?
Hey @Gabriel Fortuna thanks a lot for raising this, really good observation! To clarify: versions like
v0.148.0
are our monthly stable releases. The
-nightly
ones are daily builds with the latest fixes and improvements, and they’re tagged off the latest stable release. Out of curiosity, are you more familiar with a different naming convention for this kind of release cycle? That might help us align our docs more clearly.
g
Hey @Carlos Monastyrski - thanks for getting back to me on this 🙂 Like I mentioned above, typical nightlies signal the unstable start of a new version, and result in the stable final release of that new version e.g Traditional nightly version path 1.
v0.149.0
<- this is a stable version. 2.
v0.150.0-nightly-2025-09-10
After the stable release, a new version is incremented, and starts as an unstable nightly 3.
v0.150.0-nightly-2025-09-11
4.
v0.150.0-nightly-2025-09-12
5. …. dev and nightly releases go on until… 6.
v0.150.0
<- this is the stable release that includes all the
v0.150.0
nightly fixes My confusion arose because infisical nightlies signal the unstable start of the next version, whilst using the version of the current stable release. e.g. Infisical nightly version path 1.
v0.149.0
<- this is a stable version 2.
v0.149.0-nightly-2025-09-10
After the stable release, a new version is not incremented, and unstable nightlies are added to a stable release version. 3.
v0.149.0-nightly-2025-09-11
4.
v0.149.0-nightly-2025-09-12
5. … dev and nightly releases go on until… 6.
v0.150.0
<- this is a stable release that includes all the
v0.149.0
nightly fixes It’s really fine whichever route you take, and the important thing is that you’re offering nightly releases, which is great, but the versioning scheme is totally counter to normal nightly practices. I would either adopt the traditional nightly release approach, or make it very explicit in the docs for releases that Infisical does it differently. You guys are all doing a great job, and as an EnvKey refugee, I’m very glad you were here for us when EnvKey was sunset. 🫶
c
Hi @Gabriel Fortuna, thank you for pointing this out and for explaining it so clearly. We have updated our release process to follow the standard convention, so nightly builds are now published as pre-releases of the next stable version. We've also updated the docs with the new flow here: https://infisical.com/docs/self-hosting/guides/releases. Really appreciate you taking the time to raise this and help us improve. If there's anything else we can support you with, please don't hesitate to let us know.
g
Hi @Carlos Monastyrski - wow - thanks for taking the feedback so well. It’s really appreciated!!!
c
@Carlos Monastyrski maybe the channels were updated, yet on docker there are 2 nightly releases right now, and they are outdated. What I am missing.
All are around 0.153.0 and stopped 26 days ago.
image.png
g
@Cosmin V. Miron (Cosmic Sound) - it looks like infisical has stopped releasing nightlies? And are just releasing normal stable and patch releases now? 🤷
c
Could be so indeed!