0.10.1

Enhancements

• [Parser] The code paths for load_pgn() and move() have been merged. Any future changes to the move parser will be available in both funtions.

Bug Fixes

• [Parser] Fix bug where sloppy parser could not parse correctly disambiguated moves.

0.10.0

Enhancements

• [Parser] Add optional sloppy argument to .move and .load_pgn. This change relaxes the SAN move parser to allow for overly
  disambiguated moves arising during absolute pins. Over disambiguation violates the SAN spec, but many programs (including Chessbase and Fritz) seem to ignore this rule.

0.9.4

Bug Fixes

• [PGN] load_pgn() now correctly parses black to move indicators after comments or RAV's (1. d4 d5 2. Bf4 Nf6 3. e3 g6 4. Nf3 (4. Nc3 Bg7 5. Nf3 O-O 6. Be2 c5) **4...** Bg7 5. h3 { 5. Be2 O-O 6. O-O c5 7. c3 Nc6 } **5...** O-O).
• [PGN] load_pgn() now ignores numeric annotation glyphs (25. Rb3 $1 h4)
• [PGN] if available, pgn() now uses the move number specified in the PGN SetUp header
• [FEN] validate_fen() now ensures the en-passant square is valid with respect to the side to move

0.9.3

Enhancements

• Modify package.json for inclusion with cdnjs

0.9.2

Bug fixes

• load_pgn() now ignores (and correctly parses) Recursive Annotation Variation (RAV) found with a PGN move list
• Fixes handling of multi-char move evaluation symbols (e.g. 1. a4?!)

Documentation

• Document calling .header() without arguments to retrieve PGN header information

0.9.1

Bug fixes

• Fix bug where load_pgn() was attempting to parse half move markers - three consecutive periods '...' - as actual moves.

0.9.0

Enhancements

• Upgrade to semantic versioning. This release should be used as a reference point for all projects which have been tracking master for the past few years.