Jujutsu 0.44.0 released with stabilized tag support
The Git-compatible version control system adds tag fetching/pushing capabilities and new features for workspace management and revision processing.
Conversation activity · last 4 days peak 6/hr
Summary, timeline and people extracted by Claude from 35 items across 2 sources · 21h ago. Quotes are verbatim.
Jujutsu 0.44.0 was released on 2026-08-05, introducing stabilized support for fetching and pushing tags alongside several breaking changes and new features. The release includes new revset functions, template functions, and command flags for improved workflow flexibility, though it requires configuration updates for existing repositories due to changes in how tags are handled.
- Jujutsu 0.44.0 stabilizes tag support with tracking similar to bookmarks, though this introduces breaking changes for existing repositories.
- Multiple new features including merge_point() revset function, improved jj run flags (--passthrough, --ignore-changes, --ignore-errors), and jj file search enhancements.
- Developer community reports mixed experiences: some praise workflow safety and flexibility, while others struggle with onboarding and conceptual differences from git's staging index.
- Jujutsu has adoption at Google and is gaining traction for monorepo and complex workflow scenarios despite a learning curve for git users.
How it unfolded
-
Report Release documented on Hacker News
The release appeared on Hacker News with 49 points, linking to official changelog documentation.
-
Analysis Google adoption mentioned
jesseb34r notes that jj is already in use internally at Google with their VCS as a backend.
-
Reaction Community guidance on interactive workflows
hjvt suggests using `jj split` to separate changes, addressing the interactive staging concern raised by other users.
-
Reaction Positive user experience reported
xilef describes recent migration to jujutsu for monorepo workflow, praising features like change mobility, conflict resolution, and undo functionality.
-
Reaction User reports onboarding challenges
Commenter mariusor describes difficulty adopting jj for existing git repositories, particularly with interactive staging workflows that feel incompatible with jj's design.
-
Report Release announced on Lobsters
The release was shared on Lobsters discussion site, gaining 74 points and 33 comments from the developer community.
-
Event Jujutsu 0.44.0 released
Jujutsu 0.44.0 was released, introducing stabilized tag support for fetching and pushing. Tags can now be tracked or untracked like bookmarks, with tracked tags pushed by default.
What people are saying verbatim
“Support for fetching and pushing tags has now been stabilized. Tags can be tracked or untracked just like bookmarks.”
Jujutsu project · Official changelog · Aug 4
“make changes, interactively add them to the index then commit, push, feels like it does not work with jj”
mariusor, Lobsters commenter · Lobsters · Aug 6, 5:47 AM
“I think you may be looking for `jj split` to separate different changes from one working state, to push one through, and continue working on the rest.”
hjvt, Lobsters commenter · Lobsters · Aug 6, 6:49 AM
“The best part by far is how safe it feels. You can do some crazy rebase and mess everything up, squash commits by accident, whatever, and its all recoverable.”
Brids, Lobsters commenter, 6-month jj user · Lobsters · Aug 6, 9:51 AM
“jj is already in use internally at google with their vcs as a backend.”
jesseb34r, Lobsters commenter · Lobsters · Aug 6, 9:57 AM
“--ignore-changes is exactly what I wanted to run against ephemeral workspaces without risk of persisting accidental modifications.”
AviKav, Lobsters commenter · Lobsters · Aug 6, 6:33 AM
Voices from the web unedited
-
jj doesn't have a staging index "by default", but you can use an extra commit for the same purpose. Let's say you start off with something like this: ``` @ wtnrrk [] (no description set) ◆ wvnouv main [] initial commit ``` There is no staging index yet. `wv` (main) is a stable commit and `wt` is the working copy commit (in Git, that would be the…
-
I made two attempts now at trying to work with an existing git repo using jj and I haven't got the hang of it. I'm even unable to articulate what issues I have, probably something related to the cognitive load of having two separate types of hashes ... But my workflow of: make changes, interactively add them to the index then commit, push, feels…
-
> make changes, interactively add them to the index then commit, push Based on the "interactively add" bit, I think you may be looking for `jj split` to separate different changes from one working state, to push one through, and continue working on the rest. It is actually pretty much the workflow I tend to have.
-
Not related to this particular release, but I recently bit the bullet and moved from a multiple-workspace git situation on a big mono to just using jujutsu. While I am probably only scraping the surface of the tool, I am feeling quite liberated by being able to do the following: - create changes wherever and whenever I feel like it - move those…
-
i believe jj is already in use internally at google with their vcs as a backend.
-
> `jj run` gained a `--ignore-changes` flag to avoid editing any revisions even if the command modifies the working copy. This is great. I was experimenting with bodging hidpi support into the macos version of vintage story and ended up with an alias to build and launch arbitrary revisions. `--ignore-changes` is exactly what I wanted to run…
-
I would like to see more of how to do X with jj as well, since I am still not using it well outside of single person projects. So far I've found:
-
Treat the working copy revision like an index that automatically stashes and unstashes on rebase, and replace `git add -p`/`-i` with `jj split -i`. That's my advice, as a former heavy `git add -p` user.
-
there are some plans! https://ersc.io/blog/ersc-availability#user-content-fnref-1 (yeah, it's just a footnote)
-
This is a great step; supporting tags directly will let me drop one of the last two things I return to the git CLI for, and I'm guessing some of my fetch issues with locking are about to disappear to, thanks to https://github.com/jj-vcs/jj/issues/7530 --- I hope eventually we will have a post about a new jj version where the first and most active…