ActiveModelListener and AutoTagger become better Ruby citizens

May 15, 2010 Pivotal Labs

If you use auto_tagger in conjunction with a continuous integration build you may have noticed that the autotag executable exits with a status code of “1” when it shouldn’t. Thanks to Sarah Mei I just pushed version 0.1.5, which fixes this bug. Thanks Sarah!

If you use active_model_listener, you are probably pretty tired of that active record deprecation notices. After Todd Persen pointed this out to me I just pushed version 0.2.5 which fixes this.

About the Author

Biography

More Content by Pivotal Labs
Previous
Stubbing out Paperclip/ImageMagick in Tests
Stubbing out Paperclip/ImageMagick in Tests

Many people use the ultra popular Paperclip library to handle file attachments in Rails. Unfortunately the ...

Next
Pivotal Labs Happy Hour – Friday before GoRuCo
Pivotal Labs Happy Hour – Friday before GoRuCo

Pivotal Labs is hosting a happy hour the Friday before GoRuCo at the Blue Owl. We're looking for brilliant...

Enter curious. Exit smarter.

Learn More