4 weeks ago - last edited 4 weeks ago
In the past, the Nuxeo team made changes to the source code of the maintained LTS versions available to the public three months after they were made. This still is the case for LTS 2023. If one checks the commits on the LTS 2023 branch as of today the latest change is from Jul 4, 2025.
However, if one checks the commits on the LTS 2025 branch as of today the latest change to the code is from May 26, 2025, more than four month ago. After that date, only changes to some dependency versions seemed to be made available to the public immediately.
Will the Nuxeo team continue to make changes to the source code of LTS 2025 available to the public?
a week ago
Also, the 2025 branch: This branch is 1010 commits ahead of, 546 commits behind 2023. Seems messed up. Most of the 2025 newer things are likely Bumps from dependabot[bot]
Monday
Just one thought I just had, when looking at the commits on LTS 2025 and LTS 2023 branch:
The last commit on LTS 2025 branch that was pushed to the public repository, except the automatic bumps from depandabot, was made on May 26, 2025. Exactly three months later, on Aug 26, 2025, a series of automatic bumps started and no other commits were pushed to the public repository anymore.
If one looks at the commits on LTS 2023 branch one finds commit 22a0b2e Make 'lts-2023' the default branch . With this commit the file .github/dependabot.yaml was added which seems to configure dependabot, both for LTS 2023 branch and LTS 2025 branch.
Could this commit, if also made on LTS 2025 branch, have caused an issue with the method that pushes changes to the public 2025 repository? It seems to have led to immediate bumps instead of ones that were delayed by three months.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.