Browse files

Updated README.

  • Loading branch information...
1 parent 0a0d6b2 commit d675199683155336957939c405dab71e1a87edbb @gstokkink gstokkink committed May 4, 2012
Showing with 3 additions and 0 deletions.
  1. +3 −0 README.rdoc
@@ -238,6 +238,9 @@ The materialised path pattern requires Ancestry to use a 'like' condition in ord
The latest version of ancestry is recommended. The three numbers of each version numbers are respectively the major, minor and patch versions. We started with major version 1 because it looks so much better and ancestry was already quite mature and complete when it was published. The major version is only bumped when backwards compatibility is broken. The minor version is bumped when new features are added. The patch version is bumped when bugs are fixed.
+- Version 1.3.0 (2012-05-04)
+ - Ancestry now ignores default scopes when moving or destroying nodes, ensuring tree consistency
+ - Changed ActiveRecord dependency to 2.3.14
- Version 1.2.5 (2012-03-15)
- Fixed warnings: "parenthesize argument(s) for future version"
- Fixed a bug in the restore_ancestry_integrity! method (thx Arthur Holstvoogd)

1 comment on commit d675199

dmitry commented on d675199 May 14, 2012

Is it possible to update next version, like 1.4 to support Rails 3.2 without backward compatibility? In my fork there are a lot of fixes that I've cherry-picked from other sources.

Please sign in to comment.