Gabriel Fortuna
09/04/2025, 10:52 AM144.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.Gabriel Fortuna
09/04/2025, 11:11 AMv.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.Maidul Islam
09/04/2025, 4:38 PMAbhishek Jain
09/05/2025, 5:51 PMCarlos Monastyrski
09/08/2025, 9:17 PMCarlos Monastyrski
09/08/2025, 9:24 PMv0.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.Gabriel Fortuna
09/09/2025, 7:00 AMv0.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. 🫶Carlos Monastyrski
09/12/2025, 1:45 AMGabriel Fortuna
09/12/2025, 6:21 AMCosmin V. Miron (Cosmic Sound)
11/22/2025, 12:47 PMCosmin V. Miron (Cosmic Sound)
11/22/2025, 12:49 PMCosmin V. Miron (Cosmic Sound)
11/22/2025, 12:49 PMGabriel Fortuna
11/23/2025, 7:57 AMCosmin V. Miron (Cosmic Sound)
11/23/2025, 9:00 AM