Skip to content
Tags give the ability to mark specific points in history as being important
  • v0.6.7 protected
    4e562330 · Fixup CI ·
    Release: Tarot release
    Fixup CI
    ========
    
  • v0.5.26/2.1.2 protected
    Automatically update the flatpak package
    ========================================
    
  • v0.5.27/2.1.2 protected
    ab90a6fa · Also push to tarot-deb ·
    Automatically update the deb package
    ====================================
    
  • v0.6.8 protected
    f7f36771 · Update the deb package ·
    Release: Tarot release
    Automatically update the deb package
    
  • v0.6.9 protected Release: Tarot release
    Fixup packaging
    ===============
    
  • v0.5.28/2.1.2 protected
    1ef0d188 · Allow empty modifications ·
    Release: Tarot release
    Allow empty modifications
    
  • v0.5.29/3.0.3 protected Release: Tarot release
    Update the bindings to gobject
    ==============================
    
    In the previous introduction of the bindings, the gobject annotations
    were not present.  The libtool version is not incremented since the
    API followed the usual definition even in its early version, so there
    could not be any mistake.  The gir data is not part of the API.
    
  • v1.0.0 protected Release: Tarot release
    First graphical version
    =======================
    
    This new version comes with a full graphical version that can play a
    certain game to the end.  This is very exciting to me, thus this is a
    major release!!
    
    It is by no means any stable, there will be lots of bugs addressed
    during patch releases.
    
    I am taking any suggestion, of course.
    
  • v0.5.30/3.0.3 protected
    260695b4 · Merge branch 'develop' ·
    Update the packaging
    ====================
    
    The mingw package is now updated with each release.
    
  • v1.0.1 protected
    161b7e58 · Allow empty modifications ·
    Release: Tarot release
    Packaging update
    ================
    
    When a new version is released, the mingw package is automatically updated
    
  • v1.0.2 protected Release: Tarot release
    Slight graphical corrections
    ============================
    
    - To select a card, you just have to click on it;
    - The card of the trick taker is highlighted;
    - The mingw package has now some missing dependencies included;
    - The game now asks you kindly to declare a slam.
    
  • v0.5.31/3.0.3 protected
    148e0eb9 · Merge branch 'develop' ·
    Provide a simpler definition of the API
    =======================================
    
    The package now contains a file named *api.xml* in the package data
    directory, describing the types and functions in an xml-friendly
    fashion.
    
  • v1.0.3 protected
    0cb207af · Fixup appdata ·
    Release: Tarot release
    Provide an AppData metadata file
    
    In order to be published by flatpak-friendly software distributions, I
    have to provide this kind of metadata.  I have chosen to give it as an
    XSLT stylesheet to apply on a list of releases, because it may change
    independently of the source code (as the releases are purely git
    tags).
    
    I have also provided a mechanism to extract releases from the git tags
    automatically.  The release messages are simply the git tags,
    converted from org-mode to HTML.  This is interesting because the
    appstream metadata supports HTML to a certain extent.
    
    Finally, I have set up a strict validation with appstream-util.
    Unfortunately, the CI/CD pipeline runs on the old debian, so the
    launcher tag is not supported.
    
  • v1.0.4 protected
    24a63634 · Merge branch... ·
    Release: Tarot release
    Packaging fixup
    
    The previous release would make the build dependent on xsltproc.  This
    has been fixed.
    
  • v0.5.32/3.0.3 protected
    Fix a wrong annotation
    
    There was a missing Gtk-Doc annotation in the interface, so it is not
    compatible and hard to patch from the vala side.  So I make a dot
    release.
    
  • v1.1.0 protected Release: Tarot release
    Tune the MCTS
    
    In this release, you can tune the MCTS parameters.  Specifically,
    there are new command-line parameters:
    - =--mcts-parameter=: override the MCTS main parameter;
    - =--mcts-simulation-agreed=: increase this value to favor simulations
      where all players agree on their cards;
    - =--mcts-simulation-random=: increase this value to favor simulations
      where all players deal at random.
    
    This release is mostly useful for internal purposes.  I need this
    functionality in order to tune the default value for the parameters,
    because the AI is not really good yet.  However it is easier for the
    CI pipeline if I always have a fully released version of tarot to use
    in libtarot.
    
  • v1.1.1 protected Release: Tarot release
    Fix a memory corruption issue
    
    A struct was passed out of the reach of Vala, through a C-compile-time
    macro.  This struct had an owned field, that would be destroyed
    twice.  Making the field unowned solved the problem.
    
  • v1.2.0/3.1.3 protected
    D-Bus introduction and restructuring the source package
    
    There has been one main development, and a bit of maintainer work.
    
    There is now a D-bus interface for the server.  In the future, it will
    be useful to have MCTS players running in a separate process, not
    blocking the main app.
    
    Now, =libtarot= has been merged with the base =tarot= package.  This
    means that tarot is now released with extended version tags: package
    version / libtool version.  It also means that all packaging will have
    to be adapted.  There is one key benefit: the CI now runs on the
    project as a whole, allowing simultaneous development on program and
    library. and packaging every commit.
    
  • v1.2.1/3.1.3 protected
    Restore the build
    
    Since 1.2.0 was the first tag since the libtarot merge, the tag format
    changed and I could not debug it.  Now the package builds again.
    
  • v1.2.2/3.1.3 protected
    Restore the ability to build the Flatpak
    
    There was a build problem with the Flatpak because the manifest would
    use a local archive source, however it had to be an URL.