Jujutsu

Breaking changes

• The default template aliases were replaced as follows:

  • builtin_op_log_root(op_id: OperationId) ->
    format_root_operation(root: Operation)
  • builtin_log_root(change_id: ChangeId, commit_id: CommitId) ->
    format_root_commit(root: Commit)
  • builtin_change_id_with_hidden_and_divergent_info ->
    format_short_change_id_with_hidden_and_divergent_info(commit: Commit)

• The --revision option of jj rebase is renamed to --revisions. The short
  alias -r is still supported.

New features

• The list of conflicted paths is printed whenever the working copy changes.
  This can be

Deprecations

• jj move was deprecated in favor of jj squash.

Breaking changes

• The git_head template keyword now returns an optional value instead of a
  list of 0 or 1 element.

• The jj sparse set --edit/--reset flags were split up into jj sparse edit/reset subcommands respectively.

• The jj sparse subcommands now parse and print patterns as workspace-relative
  paths.

• The jj log command no longer uses the default revset when a path is specified.

New features

• Config now supports rgb hex colors (in the form #rrggbb) wherever existing color names are supported.

No code changes (fixing Rust Cargo.toml stuff).

Breaking changes

• The minimum supported Rust version (MSRV) is now 1.76.0.

• The on-disk index format changed. New index files will be created
  automatically, but it can fail if the repository is co-located and predates
  Git GC issues #815. If
  reindexing failed, you'll need to clean up corrupted operation history by
  jj op abandon ..<bad operation ID>.

• Dropped support for the "legacy" graph-drawing style. Use "ascii" for a very
  similar result.

• The default log output no longer lists all tagged heads. Set revsets.log = "@ | ancestors(immutable_heads().., 2) | heads(immutable_heads())" to restore
  the old behavior.

• Dropped support for the deprecated : revset operator. Use :: inst

Deprecations

• jj checkout and jj merge are both deprecated; use jj new instead to
  replace both of these commands in all instances.

  Rationale: jj checkout and jj merge both implement identical
  functionality, which is a subset of jj new. checkout creates a new working
  copy commit on top of a single specified revision, i.e. with one parent.
  merge creates a new working copy commit on top of at least two specified
  revisions, i.e. with two or more parents.

  The only difference between these commands and jj new, which also creates
  a new working copy commit, is that new can create a working copy commit on
  top of any arbitrary number of revi