v1.0.0-rc.7

As the library is now passing practically all of the yaml-test-suite tests, along with any others I've been able to find, and there are no more required features that are missing, this might be the last release before 1.0.0. Therefore, this version has been released on npm with the latest tag, so from now on the install command is just:

npm install yaml

In terms of features, rc.7 has rather little to offer on top of rc.6:

• parseCST is now also included in the default YAML export
• Add a test harness for yaml-test-suite event tests, yaml/dist/test-events
• Add a new default-false option, keepCstNodes
• Bugfix: Encode & decode URI escapes in tag suffixes

v1.0.0-rc.6

• Add support for YAML 1.0 and YAML 1.1, renaming extended schema as yaml-1.1 (note: YAML 1.0 prefix tags are parsed and stringified, but are not resolved)
• Refactor the API a bit again, adding parseDocument & renaming parseDocuments as parseAllDocuments. This more closely matches the naming pattern used by other libraries.
• Add type and format to content nodes, allowing for stringification control.
• Add keepBlobsInJSON and keepNodeTypes options, both defaulting to true.
• Split default options in YAML.defaultOptions and YAML.Document.defaults, depending on YAML version dependence
• Update to latest yaml-test-suite (now only four tests are broken in the upstream repo: yaml/yaml-test-suite#25, yaml/yaml-test-suite#27, yaml/yaml-test-suite#38, yaml/yaml-test-suite#39)
• Various minor bugfixes

v1.0.0-rc.5

• Add doc.anchors
• Add Alias and Merge nodes to AST (#12)

v1.0.0-rc.4

• Rename lowest API level more appropriately as a CST parser rather than an AST parser, so you'll now need to import yaml/parse-cst rather than yaml/parse-ast to use it.
• Simplify the object-level API, dropping Node#origTag, skip setting empty values, and letting Pair extend Node.
• Document the YAML.Document contents more clearly as an AST.

v1.0.0-rc.3

• Refactor Document#resolveValue() into YAML.createNode().
• Drop the internal doc reference from collections, and otherwise simplify the Map and Seq objects by separating out the parsing functions -- this should also make it easier to move or copy a collection between documents. Subsequently, directly calling .toString() on a Map or Seq will now get you a JSON representation of the object; for YAML output you'll need to stringify the whole document.
• Bug fixes, including in particular #18 (reported by @zoroaster00).

v1.0.0-rc.2

Switched from beta to rc because this really is nearly ready to publish.

• Documentation is now at https://eemeli.org/yaml/, rather than partly in README files and partly missing.
• Rethink semantic/syntax error boundary: Instead of classifying based on source API level, syntax errors now result in broken data while semantic errors "only" affect metadata.
• Add public re-exports: map, pair, parse-ast, scalar, seq, types/binary, types/timestamp
• Specify node ≥ 6 dependency (PR #11)
• Please ignore rc.1, it was missing a minor package.json update

v1.0.0-beta.7

Various bugfixes, in particular #7, #8, #9 and #10 as reported by @ikatyang.

v1.0.0-beta.6

Getting close to a v1 release...

• Actual documentation is developing at http://eemeli.org/yaml/
• Finalise (read: refactor) much of the public API
  • Document#contents can be set to anything
  • Add Document#resolveValue() to deeply wrap values in YAML objects
  • Move warnings from Document#errors to Document#warnings
  • Add YAML.stringify() and YAML.defaultOptions
  • Replace "stream" with "documents" in API
  • Add YAMLSemanticError class for Document#parse() errors
• String(Document) output improvements
  • tags are properly included, including prefixes
  • output is prettily folded where possible & appropriate
• Fix various corner-case syntax bugs, with thanks in particular to @ikatyang

v1.0.0-beta.4

• Comments mostly work
• Tags are included in resolved nodes
• Consider comments at start without directives-end indicator to be part of the document contents, not directives

v1.0.0-beta.3

• Merge raw-yaml@0.2.5 as src/ast
• Fix remaining error-reporting mismatches