v1.0.0

[dex4er]

The main goal:

• The first stable release
• The stable API for extensions that should not change for longer time
• All necessary updates for the current version of Kubernetes

[robertobandini]

I think we should add some more details and also specify that we will think to updates and why on the 1.1.0 for example.
Perhaps a document that gradually describes the roadmap in a general sense.

[dex4er]

The goal: to polish binary packages for all major OSes

[dex4er]

It should be ready in v0.1.4 as I'm working now on the AppStream metainfo files and other metadata for Mac and Windows.

[dex4er]

The goal: to stabilize @freelensapp/extensions then new releases should not break compatibility of extensiosn for longer time

[robertobandini]

Thanks @dex4er then after that we can start to work to depedency updates.

[dex4er]

I'm not sure if we have very important changes for 1.0.0. I think we can just bump the major version and release it.

[dex4er]

[dex4er]

@mariomamo main...dex4er:freelens:node-20-electron-34

[dex4er]

So as you see I made minimalistic approach to upgrade only Electron skipping all other changes. I didn't run tests yet. My goal is to adapt pipelines to use newer Ubuntu first so we could use GitHub Actions to test properly any other upgrades.

[mariomamo]

Thanks for your suggestion, @dex4er. I followed your instructions and found that updating the Node.js version in the "package.json" file at the root of the project also requires updating the TypeScript version, which fixes many vulnerabilities. Therefore, I believe it's worth updating it. I also resolved all the compilation issues without too many difficulties. In the coming days, I'll do some testing and commit these changes.

However, if having the updated Electron version within the next few days is important for you, I can start by committing just that, or you can proceed with the merge since you've already made that change.

[dex4er]

@mariomamo ok, so i'll try to rebase my PR to unblock tests then we can go with updating the rest ie. TypeScript. Speeking of which: I updated it for freelensapp/freelens-node-pod-menu#73 and it worked. OK, this extension is a stub now so it is far less complex that the main project, but we'll see how far we can go.

[dex4er]

I fixed some bugs that were already 1 and half year old: lensapp/lens#7965 and lensapp/lens#7964

It was just a cherry-pick with my changes. Nothing super important but at least we'll have better version that old, long-dead OpenLens.

I'm going to check if we can also adapt lensapp/lens#7953

[robertobandini]

[dex4er]

So my proposition is to test if the current nightly builds are fine then we can release v1.0.0 in the beginning of the next week then be focused on #152

[robertobandini]

I agree! That's great!

[dex4er]

For comparition: the current version is

[dex4er]

Upgrade of Electron is possible but we stick to the current plan that now we're releasing v1.0.0 based on the current main branch. The main reason is that this version is already tested well and does not require additional changes for Linux. Changing Node version will break binary compatible with older Linux then will force us to test all dependencies again. It is not trivial task: each Linux distro has own quirks then it'll take more time to test them properly.

New Node and Chrome will bring new quirks and it'll slow down significantly a preparation of the new release. The main goal of v1.0.0 is to provide stable API for extensions to gather larger audience then it is rather clear: https://en.wikipedia.org/wiki/Release_early,_release_often is the best strategy.

[robertobandini]

I agree to maintain the actual plan and then go forward with the Electron upgrade.
So actually this is generally enough but we need to test all dependencies?
#154
Could it help in the future to increase automated testing and possibly establish a beta testing process?
@dex4er @mariomamo
Thanks about your great work!

[dex4er]

All distributed now:

[robertobandini]

Thanks!