Prerelease 6.8.10.dev1 is in pypi

12 views
Skip to first unread message

Ville M. Vainio

unread,
Aug 9, 2026, 6:49:50 AM (yesterday) Aug 9
to leo-editor
Now we have the first Github Actions based release happening.

Here's the prerelease that was automatically uploaded to pypi:


You can test it with:

pip install leo==6.8.10.dev1

Ville M. Vainio

unread,
Aug 9, 2026, 7:23:26 AM (yesterday) Aug 9
to leo-editor
I want to try to automate some things like leoVersion.py and generating the version string in ci, so there will be at least .dev2 before final

Viktor Ransmayr

unread,
Aug 9, 2026, 9:40:19 AM (yesterday) Aug 9
to leo-editor

Hello Ville,

Ville M. Vainio schrieb am Sonntag, 9. August 2026 um 13:23:26 UTC+2:
I want to try to automate some things like leoVersion.py and generating the version string in ci, so there will be at least .dev2 before final

On Sun, Aug 9, 2026 at 1:49 PM Ville M. Vainio <viva...@gmail.com> wrote:
Now we have the first Github Actions based release happening.

Here's the prerelease that was automatically uploaded to pypi:


Since I had distrobox containers available on Debian & Fedora the installation from PyPI was easy & went smooth !

Nothing to report from my tests at this point in time, other than the issue you reported already about the version string.

In order to make it clearer for other readers here is Leo's log started in a Fedora 44 container:

    Leo Log Window
    Leo 6.8.10-devel, master branch, June 3, 2026
    Python 3.14.6, PyQt version 6.11.1
    linux
    setting leoID from os.getenv('USER'): 'user'
          home: /home/user/distroboxes/projects/leo-on-fedora
    leo-editor: /home/user/distroboxes/projects/leo-on-fedora/.venv/lib64/python3.14/site-packages
          load: /home/user/distroboxes/projects/leo-on-fedora/.venv/lib64/python3.14/site-packages/leo/core
        config: /home/user/distroboxes/projects/leo-on-fedora/.venv/lib64/python3.14/site-packages/leo/config
    reading settings in /home/user/distroboxes/projects/leo-on-fedora/.venv/lib64/python3.14/site-packages/leo/config/leoSettings.leo
    reading settings in /home/user/distroboxes/projects/leo-on-fedora/.leo/myLeoSettings.leo
    reading settings in /home/user/distroboxes/projects/leo-on-fedora/.leo/workbook.leo
    read outline in 0.01 seconds

Viktor

Edward K. Ream

unread,
Aug 9, 2026, 12:43:00 PM (yesterday) Aug 9
to leo-e...@googlegroups.com
> On Sun, Aug 9, 2026 at 1:49 PM Ville M. Vainio wrote:

> Here's the prerelease that was automatically uploaded to pypi:
> https://github.com/leo-editor/leo-editor/releases/tag/v6.8.10.dev1
> You can test it with:
> pip install leo==6.8.10.dev1

Fantastic work, Ville. The summary of PRs is going to save me a lot of time.

Running the run_installed_leo.py script is equivalent to do the following in a console:

python -m leo.core.runLeo

As Ville has implied somewhere, the version string is misleading. It is:

Leo 6.8.10-devel, June 3, 2026, not Leo 6.8.10dev1. It's no big deal.

To revert to Leo running from a GitHub repo, just do the following from a console:

pip uninstall leo

Edward

Ville M. Vainio

unread,
Aug 9, 2026, 12:56:20 PM (yesterday) Aug 9
to leo-e...@googlegroups.com, Edward Ream
The --version has been corrected in dev2 actually.

 pip install leo==6.8.10.dev2

Now the last remaining thing before final release is writing release notes @Edward Ream 

Ville M. Vainio

unread,
Aug 9, 2026, 12:58:46 PM (yesterday) Aug 9
to leo-e...@googlegroups.com, Edward Ream
... or should we do the release notes after the release has been pushed? We can then also link to github releases page that has the merged prs

Edward K. Ream

unread,
Aug 9, 2026, 1:05:02 PM (yesterday) Aug 9
to leo-e...@googlegroups.com, Edward Ream
On Sun, Aug 9, 2026 at 11:58 AM Ville M. Vainio <viva...@gmail.com> wrote:
... or should we do the release notes after the release has been pushed? We can then also link to github releases page that has the merged prs

The release notes (in LeoDocs.leo) belong with the actual release. We can always update links later in the online version.

I'll be pushing update release notes soon.  To the "devel" branch!

Edward
Reply all
Reply to author
Forward
0 new messages