Seems I forgot to update it when doing the release.   I could add the 2.2.1 plugin info to 2.2 plugin repo as a workaround.

We could use convention instead of the hard coded configuration for plugin repo url in the future to avoid this kind of issues.

On Thu, Feb 3, 2011 at 11:55 PM, Kevan Miller <> wrote:
Doesn't look like the plugin repository was updated for 2.2.1. Anybody else seeing the same?