1.4.0

The drill reaches the deep parts of a repertoire; notes survive leaving a
session; the move list scrolls itself rather than the note.

1.3.1

Arrows past the first are kept and released; a position holding more than
one of your own moves no longer scores the rest as mistakes.

1.3.0

Repertoires move out of the plugin's own folder and into the vault, where the
rest of your notes are.

Added

• A setting for where repertoires are kept. Settings → Community plugins →
  Chess Repertoire → Repertoire folder, a folder picker over the vault. Leave it
  empty for "Chess Repertoires" in the root. Changing it moves the files already
  written into the new folder, so it can be reorganised later without stranding
  anything; a name already taken in the destination is left alone rather than
  overwritten, and anything that could not be moved stays readable where it was.

Changed

• Repertoires are stored in the vault rather than in
  .obsidian/plugins/chess-repertoire/storage. That folder is deleted whole
  when the plugin is uninstalled, and Obsidian Sync, version history and file
  recovery all pass over it - so uninstalling to reinstall, which is the ordinary
  way to fix a plugin, took every repertoire with it and left nothing to restore
  from.

  Existing repertoires are copied into the new folder the first time 1.3.0 loads,
  and the old folder is then renamed to storage_bak rather than deleted. The
  copy never overwrites, and the rename only happens once every file has arrived;
  a run that could not read something copies nothing over it, leaves the
  originals alone and tries again next load.

  Your notes need no changes. They reference repertoires by id, and the id is
  unchanged.

  storage_bak is not a backup you can keep. It is still inside the plugin
  folder, so it goes the same way on uninstall. Check your repertoires open, copy
  anything else out of it, and delete it.

  Repertoires are .json, which Obsidian Sync counts as an unsupported
  extension: moving them into the vault only syncs them if Settings → Sync →
  All other file types is on.

1.2.0

Housekeeping from the Obsidian plugin review. Obsidian 1.13 is now the
minimum; older installs stay on 1.1.0.

1.1.0

Added

• Variations on a repertoire's first move. Every variation hangs off the move
  before the alternatives it holds, and the first move has none - so an
  alternative to it had nowhere to live. Playing a second first move was refused
  with a notice, the PGN importer dropped one, and a merge counted it as lost.
  The tree now keeps those alternatives itself, and they behave like any other
  variation: they import and export, drill, appear on the map, promote to the
  mainline, reorder and delete.

  This is invisible in an ordinary opening repertoire, where the first move is a
  fixed choice. It matters in one opened from a mid-game position, where the
  first move is a real decision and recording the candidates is the whole reason
  for importing the position.

• Merging repertoires that continue from one another. A note often holds an
  opening in instalments: a base line, then a repertoire opening from the
  position it ends in, then another from where that one stops. A merge joins each
  one at whatever move reaches the position it opens from, rather than only at a
  shared starting position. Positions are matched without their clocks, so a line
  arriving by a different move order still joins, and joining repeats until
  nothing more attaches, so the instalments may be listed in any order.

• Drawn positions marked with a ½, in the move list, on the board and on map
  cards. Stalemate, insufficient material, the fifty-move rule and repetition are
  all read from the board rather than set by hand, so there is nothing to
  remember and nothing to go stale. The mark sits beside a classification rather
  than replacing it: a move can be a blunder and still be the one that draws.

Fixed

• PGN export silently dropped the variations on a line's last move, and with
  them everything underneath. Those are alternatives to a move that is not there,
  which makes them what follows the line - so the line now carries on into the
  first of them, and the rest become alternatives to its opening move. Reading
  that back gives the same tree.

• Deleting a mainline that had alternatives beside it left them with nothing
  to be alternatives to, and no first move for the list to draw them under. The
  oldest alternative now takes the vacant mainline.

Changed

• A merged continuation carries the mainline on rather than arriving as a
  variation. Where the line it joins already goes on, a new reply really is an
  alternative to what follows and still hangs off the move before it; where the
  line stops, the first thing grafted on continues it. A note holding an opening
  in instalments now merges into one line rather than a line that ends and a
  variation that resumes it.

• Map cards show the position their own moves reach, rather than the position
  their first move reached. A card that forks now shows the position its children
  branch from, and a card that ends a line shows how it ends - the mate, the drawn
  position, the endgame. Previously a fork's card sat one position behind the fork
  it was illustrating, and the branches hanging off it differed from it and from
  one another by a single move, so they all looked alike.

• A repertoire that records more than one first move draws the starting
  position as its own card on the map, since that fork has no move to hang off
  either. One with a single first move draws exactly as before.

• Repertoire files move to storage version 0.0.7, which adds the first move's
  alternatives. Older files are read unchanged and gain an empty list on load, so
  nothing needs converting.

---

Full changelog: https://github.com/moise-dev/obsidian-chess-repertoire/blob/1.1.0/CHANGELOG.md

1.0.0

fix: grant the release job write access to contents

gh release create was hitting a 403 - the default GITHUB_TOKEN is read-only
unless a workflow explicitly asks for more, which this one never did. It was
presumably relying on a repo-level "Workflow permissions" default that never
applied here. Declaring contents: write is self-contained and doesn't depend
on that setting either way.