# This file documents the revision history for Perl extension Catalyst.
-5.9000 - UNRELEASED
+5.90003 - 2011-10-05 02:03:00
- Major changes in this release:
+ Bug fixes:
+
+ - Make default body reponses for 302s W3C compliant. RT#71237
+
+ - Fix issue where groups of attributes to override controller actions
+ in config would be (incorrectly) overwritten, if the parser for that
+ attribute mangled the contents of the attribute. This was found
+ with Catalyst::Controller::ActionRole, where Does => [ '+Foo' ]
+ would be transformed to Does => [ 'Foo' ] and written back to config,
+ whereas Does => '+Foo' would not be changed in config. RT#65463
+
+ Enhancements:
+
+ - Set a matching Content-type for the redirect if Catalyst sets the
+ body. This is for compatibility with a WatchGuard Firewall.
+
+ Backward compatibility fixes:
+
+ - Restore (an almost empty) Catalyst::Engine::HTTP to the dist for old
+ scripts which explictly require Catalyst::Engine::HTTP
+
+ Documentation fixes:
- The Catalyst::Engine classes have all been removed and deprecated,
- to be replaced with Plack handlers.
+ - Document Catalyst::Plugin::Authentication fails tests unless
+ you use the latest version with Catalyst 5.9
- Plack is an implementation of the PSGI specification, which is
- a standard interface between web servers and application frameworks.
+ - Clarify that prepare is called as a class method
- This should be no different for developers, and you should not have to
- migrate your applications unless you are using a custom engine already.
+ - Clarify use of uri_for further. RT#57011
- This change benefits Catalyst significantly by reducing the amount of
- code inside the framework, and means that the framework gets upstream
- bug fixes in Plack, and automatically gains support for any web server
- which a PSGI compliant handler is written for.
+5.90002 - 2011-08-22 21:44:00
+ Backward compatibility fixes:
- It also allows you more flexibility with your application, and allows
- the use of cross web framework 'middleware'.
+ - Deploying via mod_perl in some cases is fixed by making
+ Catalyst::EngineLoader detect mod_perl in more generic
+ circumstances.
+ https://github.com/miyagawa/Plack/issues/239
- Developers are recommended to read Catalyst::Upgrading for notes about
- upgrading, especially if you are using an unusual deployment method.
+ Documentation fixes:
- Documentation for how to take advantage of PSGI can be found in
- Catalyst::PSGI, and information about deploying your application
- has been moved to Catalyst::Manual::Deployment.
+ - Fix incorrect example in Catalyst::PSGI.
+ - Add note that if you are using the PSGI engine, then $c->req->env
+ needs to become $c->engine->env when you upgrade.
- A number of modules have been updated to pass their tests or not
- produce deprecation warnings with the latest version of Catalyst.
- It is recommended that you upgrade any of these that you are using
- after installing this version of Catalyst.
+5.90001 - 2011-08-15 22:42
- These extensions are:
+ Realise that we accidentally chopped a digit off the versioning scheme
+ without anyone noticing, which is a bad thing.
- Catalyst::Engine::HTTP::Prefork - this is now deprecated, see
- Catalyst::Upgrading.
+ Feel like a fool. Well done t0m.
- Test::WWW::Mechanize::Catalyst - has been updated to not produce
- deprecation warnings.
+ Cut another release.
- Catalyst::ActionRole::ACL - has been updated to fix failing tests
- (although older versions still function perfectly with this
- version of Catalyst).
+5.9000 - 2011-08-15 22:18
- Catalyst::Plugin::Session::Store::DBIC - has been updated to fix
- failing tests (although older versions still function perfectly
- with this version of Catalyst).
+ See Catalyst::Delta for the major changes in this release.
- Changelong since the last TRIAL release:
+ Changelog since the last TRIAL release:
Backward compatibility fixes:
projects / catagits/Catalyst-Runtime.git / blobdiff