Yesterday we released Prototype 1.6.0.3, the result of some much-needed bug fixes, and a stopgap release on the road to 1.6.1.

It’s a backwards-compatible, drop-in replacement recommended for all users of Prototype 1.6. We’ve fixed 30 bugs and made 25 other improvements to our already-rock-solid library.

Developers who follow along in Git might’ve noticed that the repository has seen a lot of disruptive activity in the last few days as we reassessed many of the commits that had gone into the library since April. Rather than try to fit too many fixes into one release, we decided to scale back and release 1.6.0.3 with the set of improvements we were in complete agreement on.

Because of the way we handled this overhaul, those who try to update their Git working copies to the latest trunk will encounter conflicts, even if they hadn’t made local changes.

Here’s how we recommend bringing your working copy up to date:

  1. First, if you’ve made any local changes, please create a new branch so that those changes aren’t lost.

  2. On your local master branch, run:

    git fetch origin master
git reset --hard 34ee207

    The first line fetches the new commits without trying to apply them to your local copy. The second line resets your master branch to be in sync with the latest revision.

  3. From there, you can cherry-pick from your branch any local commits you made (though you may have to do some manual merging).

Download, report bugs, and get help

<ul>
<li><a href="http://cloud.github.com/downloads/sstephenson/prototype/prototype_1-6-0-3.js">Download Prototype 1.6.0.3</a></li>
	<li><a href="http://prototype.lighthouseapp.com/projects/8886-prototype">Submit bug reports</a> to Lighthouse</li>
	<li><a href="http://prototypejs.org/discuss">Get Prototype help</a> on the Prototype & script.aculo.us mailing list or #prototype <span class="caps">IRC</span> channel</li>
	<li><a href="http://groups.google.com/group/prototype-core">Interact with the Core Team</a> on the prototype-core mailing list</li>
</ul>


<p>As always, thanks to the core team and the many users who contributed bug reports and well-tested patches for this release.</p>