X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=Changes;h=40c4df8c892f24c6c4ab02ef1a855a2d71d3d0ac;hp=3c2d211257e6921f3791141d3a923b9191148ca5;hb=1cbdfa9b4506dadbfa520ed0a1fc33d9064be541;hpb=63a50bd691370dbe53aea733ef44f34d5e4e8f06 diff --git a/Changes b/Changes index 3c2d211..40c4df8 100644 --- a/Changes +++ b/Changes @@ -1,55 +1,132 @@ # This file documents the revision history for Perl extension Catalyst. -5.9000 - UNRELEASED +5.90006 - 2011-10-25 09:18:00 - Major changes in this release: + New features: + - A new 'run_options' class data method has been added to Catalyst.pm + This is used to store all the options passed by scripts, allowing + application authors to add custom options to their scripts then + get them passed through to the application. + + Doumentation: + - Clarify that if you manually write your own .psgi file, then optional + proxy support (via the using_frontend_proxy config value) will not be + enabled unless you explicitly apply the default middlewares from + Catalyst, or you apply the middleware manually. + + Bug fixes: + - Fix issue due to perl internals bugs in 5.8 and 5.10 (not present in + other perl versions) require can pass the context inappropriately, + meaning that some methods of loading classes can fail due to void + context being passed throuh to make_immutable, causing it to not return + a value. + This bug caused loading Catalyst::Script::XXX to fail and is fixed + both by bumping the Class::Load dependency, and also adding an explicit + '1;' to the end of the classes, avoiding the context issue. + + - Fix using_frontend_proxy support in mod_perl by using the psgi wrapped + in default middleware in mod_perl context, rather than the raw psgi. + +5.90005 - 2011-10-22 13:35:00 + + New features: + + - $c->uri_for_action can now take an array of CaptureArgs and Args + If you have an action which has both, then you can now say: + $c->uri_for_action('/myaction', [@captures, @args]); + whereas before you had to say: + $c->uri_for_action('/myaction', [@captures], @args); + The previous form is still supported, however in many cases it is + easier for the application code to not have to differentiate between + the two. + + - Catalyst::ScriptRunner has been enhanced so that it will now + load and apply traits, making it easier to customise. + - MyApp::TraitFor::Script (if it exists) will be applied to all + scripts in the application. + - MyApp::TraitFor::Script::XXXX will be applied to the relevant script + (for example MyApp::TraitFor::Script::Server will be applied to + MyApp::Script::Server if it exists, or Catalyst::Script::Server + otherwise). + + Documentation: + + - Document how to get the vhost of the request in $c->req->hostname + to avoid confusion + - Remove documentation showing Global / Regex / Private actionsi + as whilst these still exist (and work), they are not recommended. + - Remove references to the -Engine flag. + - Remove references to the deprecated Catalyst->plugin method + - Spelling fixed (and tested) throughout the documentation + - Note that wrapping the setup method will not work with method modifiers + and provide an alternative. + +5.90004 - 2011-10-11 17:12:00 + + Bug fixes: + + - Don't guess engine class names when setting an engine through + MyApp->engine_class. + +5.90003 - 2011-10-05 08:32:00 + 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: