Project Release: git-next v2025.5.1

2025-05-25T15:16:00+01:00

Today I released version 2025.5.1</code> of git-next</a>, my Trunk-based development manager. This update fixes an embarrasing bug in the previous version, where it couldn’t update the next</code> branch. Which is basically git-next</code>’s whole thing.</p>

Key Changes:</h2>
Git Operations Overhaul 🔧</h3>

Fixed remote push synchronization issues</li>
</ul>

While switching to git2</code> in the previous release I got the process wrong and my tests weren’t sufficient to pick up on it.</p>
</blockquote>

Added detailed push conflict detection</li>
</ul>

So, working through the push process I’ve added more checks.</p>
</blockquote>

Enhanced rebase handling with parent commit validation

Improved commit log traversal with duplicate filtering</li>
</ul>
</li>
</ul>
Configuration & Maintenance 🛠</h3>

Removed legacy external repo support</li>
</ul>

This had originally been added as an option, but I’m not aware that it get’s
used and it complicates matters when deciding the name of the remote that we
should be pushing to.
Where as, when we have only internal repos. we always know that they will
called ‘origin’.</p>
</blockquote>

Simplified remote management (now always uses ‘origin’)</li>
Refactored ServerRepoConfig to builder pattern</li>
</ul>

I’m moving away from constructor to use builders more</p>
</blockquote>

Added Docker publishing workflow to Justfile</li>
</ul>

Because I kept forgetting to push the image to codeberg:</p>
</blockquote>
   just</span></span> publish-docker-image v2025.5.1</span>
</span></code></pre>
Diagnostics & Reliability 🩺</h3>

Added more logging:

Added detailed push failure diagnostics</li>
Implemented repository state logging</li>
</ul>
</li>
Fixed shutdown error visibility</li>
</ul>

When using the --ui</code> or --xui</code> any error that caused the server to abort we
lost when the screen reset to normal.
Now it is logged to the screen after the console is reset.</p>
</blockquote>

Removed debug symbols from dev builds</li>
</ul>

An optimisation for development only.</p>
</blockquote>
Documentation Updates 📚</h3>

Corrected Forgejo naming throughout codebase</li>
</ul>

I had been using ForgeJo</code> consistently, but wrongly.</p>
</blockquote>

Removed deprecated gitdir references</li>
</ul>

Now that we only support internal repos, we don’t support the gitdir</code> option
for repos.</p>
</blockquote>
Testing Improvements ✅</h3>

Added comprehensive force push tests</li>
</ul>

Given the mess I made with git push, there are now more tests around this.</p>
</blockquote>

Implemented remote test setup framework</li>
</ul>

Part of that is setting up two git repos on disk and making one the remote of
the other.</p>
</blockquote>

Added 6 new test cases for branch validation</li>
</ul>

Tests to check that we use --force-with-lease</code> only when required, which is
when CI fails and next</code> needs to be reset back to main</code>.</p>
</blockquote>

Enhanced commit history verification</li>
</ul>

Again, more tests to check this is doing what it is supposed to.</p>
</blockquote>
This release focuses on hardening Git operations while improving
maintainability and diagnostics.</p>

Project Update: git-next

2025-05-08T18:44:00+01:00

Migration Cleanup Completed</h2>
The `.dev/TODO.md</code> file has been significantly simplified after completing the migration from gix</code> to git2</code> in the gitlib</code> module. The detailed migration checklist has been replaced with a fresh TODO template for the next project.</p>`

New Docker Publishing Workflow</h2>

A new just</a> recipe has been added to streamline Docker image publishing.
The publish-docker-image</code> command now handles:</p>
• Pulling images from the internal registry
• Retagging for Codeberg.org</a>
• Pushing to the public registry</p>
Example usage:</p>
just</span></span> publish-docker-image v1.2.3</span>
</span></code></pre>

kemitix.net - git-next

Project Release: git-next v2025.5.1

Project Update: git-next

Migration Cleanup Completed</h2>
The `.dev/TODO.md</code> file has been significantly simplified after completing the migration from gix</code> to git2</code> in the gitlib</code> module. The detailed migration checklist has been replaced with a fresh TODO template for the next project.</p>`

Project Release: git-next v2025.5.0

kemitix.net - git-next

Project Release: git-next v2025.5.1

Project Update: git-next

Migration Cleanup Completed</h2> The .dev/TODO.md</code> file has been significantly simplified after completing the migration from gix</code> to git2</code> in the gitlib</code> module. The detailed migration checklist has been replaced with a fresh TODO template for the next project.</p>

Project Release: git-next v2025.5.0

Key Changes:</h2> Backend Migration:</h3> Completed migration from gix</a> to git2</a> for Git operations</li> Implemented git2-based functionality for: Rebase operations (with new tests)</li> Remote operations (fetch/push)</li> Branch switching</li> File reading</li> Clone operations</li>

Backend Migration:</h3> Completed migration from gix</a> to git2</a> for Git operations</li> Implemented git2-based functionality for: Rebase operations (with new tests)</li> Remote operations (fetch/push)</li> Branch switching</li> File reading</li> Clone operations</li>

Cargo Features:</h3> Moved email and desktop notifications into two new non-default features: notify-desktop</code></li> notify-email</code></li> </ul> </li>

Migration Cleanup Completed</h2>
The `.dev/TODO.md</code> file has been significantly simplified after completing the migration from gix</code> to git2</code> in the gitlib</code> module. The detailed migration checklist has been replaced with a fresh TODO template for the next project.</p>`