But what happened to 0.1.x ??

[LoicMahieu]

bower scrollReveal.js#~0.1.3          ENORESTARGET No tag found that was able to satisfy ~0.1.3

Additional error details:
Available versions: 2.0.1, 2.0.0

As I could understand, you git push --force your repository with your new version ?
All previous commit and tags are forgotten ! bower install are broken for projects that depends on previous tags...

Why overwrite the whole history and not just commit your changes, even if the repository is completely changed ?

If you still have the old repository/branch/tags, please push it on a branch, other than master.
Meanwhile I push a repository with a copy of scrollReveal.js#0.1.3 https://github.com/LoicMahieu/scrollReveal.js-0.1.3 and simply change bower.json to

-    "scrollReveal.js": "~0.1.3",
+    "scrollReveal.js": "LoicMahieu/scrollReveal.js-0.1.3#0.1.3",

[jlmakes]

@LoicMahieu It’s simple, the previous version contained numerous bugs and documentation inconsistencies. With no plans for a 1.4 to reconcile those issues, I am no longer supporting 1.x.

I contemplated keeping the older version available, but after I re-built the documentation into the wiki and pruned all past issues and PRs for incorrect and outdated information, I chose to drop the hammer and nix 1.x. (Virtually all of 2.0 is backwards compatible anyway.)

I will add a change log soon (including breaking changes and a migration guide), but here’s the gist:

• after is no longer a keyword for controlling animation delay.
• init is no longer a member of the config object.

If you’re going to take the time to fork your own outdated copy and then update your bower.json with it, you’re better off just upgrading and removing after from your markup.