# This file documents the revision history for Perl extension Catalyst.
-5.80027 2010-09-01
+ - Fixed Catalyst::Engine::Stomp compatibility. Applications using
+ Catalyst::Engine::Stomp are believed to continue working without
+ any changes with the new Catalyst major version.
+
+ - Fixed issues auto-loading engine with older scripts.
+
+ - Catalyst::Engine::Wx is officially unsupported and BROKEN. If you
+ are using this engine then please get in touch with us and we'll
+ be happy to help with the changes it needs to be compatible with
+ the new major version of Catalyst.
+
+ - XXX removal of engine_class?
+ - XXX removal of setup_engine($name)?
+
+5.80032 2011-02-23 01:10:00
+
+ Bug fixes:
+ - Fix compatibility issue with code which was testing the value of
+ $c->res->body multiple times. Previously this would cause the value
+ to be built, and ergo cause the $c->res->has_body predicate to start
+ returning true.
+ Having a response body is indicated by $c->res->body being defined.
+
+ - Fix bug with calling $upload->slurp multiple times in one request
+ not working as expected as the file handle wasn't returned to
+ the zero position. (Adam Sjøgren)
+
+ - Fix some weird perl 5.8 situations where $c can get squashed unexpectedly
+ in Catalyst::execute
+
+ - Fix chained dispatch where chains were being compared for length (number
+ of private parts in the chain) vs where they are being compared for
+ PathPart length (i.e. number of non-capturing URI elements in your path).
+
+ This bug meant that sometimes multiple Args or CaptureArgs (e.g. /*/*)
+ type paths would be preferred to those with fixed path elements
+ (e.g. /account/*)
+
+ New features:
+ - Add MYAPP_RESTARTER and CATALYST_RESTARTER environment variables to
+ allow the restarter class to be chosen per application or generally.
+
+ This feature was added to enable GUI restarters (such as the soon to
+ be released CatalystX::Restarter::GTK to be enabled more easily by
+ developers without changing their application code.
+
+5.80031 2011-01-31 08:13:02
+
+ Bug fixes:
+ - Update dependency on MooseX::Role::WithOverloading to ensure that
+ a version which can deal with / depends on a new Package::Stash
+ is installed. (As if some other dependency is pulled in during upgrading
+ which results in new Package::Stash, then it can leave you with a broken
+ version of MooseX::Role::WithOverloading.
+
+ - Fix undef warning in Catalyst::Engine::FastCGI when writing an empty
+ body (e.g. doing a redirect)
+
+5.89000 2011-01-24 09:28:45 (TRIAL release)
+
+ This is a development release from psgi branch of Catalyst-Runtime.
+
+ Removed features:
+
+ - All of the Catalyst::Engine::* namespace is now gone. Instead we only have
+ one Catalyst::Engine class speaking the PSGI protocol natively. Everything
+ the various Catalyst::Engine:: classes did before is now supposed to happen
+ through PSGI handlers such as Plack::Handler::FCGI,
+ Plack::Handler::HTTP::Server::PSGI, Plack::Handler::Apache2, and so
+ on. However, deployment can still work the same as it did before. The
+ catalyst scripts still exist and continue to work.
+
+ If you find anything that either doesn't work anymore as it did before or
+ anything that could be done before with the various Catalyst::Engine::
+ classes, but can't be done anymore with the single PSGI Catalyst::Engine
+ class, please tell us *now*.
+
+5.80030 2011-01-04 13:13:02
+
+ New features:
+ - Add a --proc_title option to the FCGI script to set the process
+ title.
+ - Allow the response body to be set to `undef' explicitly to indicate the
+ absence of a body. It can be used to indicate that no body should be sent at
+ all and processing of views should be skipped. This is especially useful for
+ things like X-Sendfile, which now no longer require providing fake response
+ bodies to suppress view processing. In order for this to work, you will also
+ have upgrade Catalyst::Action::RenderView to at least version 0.15.
+
+ Bug fixes:
+ - Deal correctly with GLOB file handles in the response body (setting
+ the Content-Length header appropriately)
+ - Chained dispatch has been fixed to always prefer paths
+ with the minimum number of captures (rather than the
+ maximum number of actions). This means that (for example)
+ a URI path /foo/* made out of 2 actions will take preference
+ to a URI path /*/* made out of 3 actions. Please check your applications
+ if you are using chained action and please write new test to report
+ failing case.
+ - Stop relying on bugs in the pure-perl version of Package::Stash. New
+ versions of Package::Stash load Package::Stash::XS if
+ available. Package::Stash::XS fixes some of the bugs of the pure-perl
+ version, exposing our faulty assumption and breaking things. We now work
+ with both old and new versions of Package::Stash, both with and without
+ Package::Stash::XS being installed. Older versions of Catalyst-Runtime also
+ work with both old and new versions of Package::Stash, but only if
+ Package::Stash::XS is *not* installed.
+
+ Documentation:
+ - Clarify that when forwarding or detaching, the end action associated
+ with the original dispatched action will be run afterwards (fallen)
+
+5.80029 2010-10-03 16:39:00
+
+ New features:
+ - Add a warning when $c->view is called and cannot locate a default_view
+ or current_view. This clarifies the logging when ::RenderView gets
+ confused.
+
+ Warning fixes:
+ - Deal warning in with Moose >= 1.15 if you add a method called 'meta' to a
+ class which already has one by using _add_meta_method.
+
+5.80028 2010-09-28 20:49:00
+
+ Bug fixes:
+ - use Class::MOP in Catalyst::Utils.
+
+ - Do not keep a reference to a closed over context in ctx_request, allowing
+ the caller to dispose of the request context at their leisure.
+
+ - Changes to be compatible with bleadperl
+
+5.80027 2010-09-01 22:14:00
Bug fixes:
- Fix an issue with newly added test cases which depended on Catalyst::Action::RenderView
projects / catagits/Catalyst-Runtime.git / blobdiff