Updates for Athena 0.20.0

shard.yml

@@ -2,7 +2,7 @@ name: skeleton
 
 version: 0.1.0
 
-crystal: ~> 1.13
+crystal: ~> 1.14
 
 license: MIT
 
@@ -15,7 +15,7 @@ targets:
 dependencies:
   athena:
     github: athena-framework/framework
-    version: ~> 0.19.2
+    version: ~> 0.20.0
 
 development_dependencies:
   ameba:

src/commands/README.md

@@ -1,6 +1,6 @@
 # `src/commands`
 
-The `src/commands` directory contains all of the [console commands](https://athenaframework.org/components/console/) for your application.
+The `src/commands` directory contains all of the [console commands](https://athenaframework.org/getting_started/commands/) for your application.
 These can be used for administrative tasks, or as an alternative way to interact with the application such as for cron jobs.
 The commands may also reuse the same services defined in the rest of the application.
 

src/exceptions/README.md

@@ -1,6 +1,6 @@
 # `src/exceptions`
 
-The `src/exceptions` directory contains all of the custom [ATH::Exceptions::HTTPException](https://athenaframework.org/Framework/Exceptions/HTTPException/) and/or `::Exception` types for the application. Having specialized exception types can help by providing more helpful errors, allowing more specific state to be included in the exception instance, and allow more targeted logic in `rescue` blocks and/or within an [exception](https://athenaframework.org/components/#8-exception-handling) event listener.
+The `src/exceptions` directory contains all of the custom [ATH::Exception::HTTPException](https://athenaframework.org/Framework/Exception/HTTPException/) and/or `::Exception` types for the application. Having specialized exception types can help by providing more helpful errors, allowing more specific state to be included in the exception instance, and allow more targeted logic in `rescue` blocks and/or within an [exception](https://athenaframework.org/getting_started/middleware/#8-exception-handling) event listener.
 
 Also leveraging `::Exception` in the service layer allows for more flexibility as those exceptions would be valid in both HTTP and CLI contexts.
 While if within the HTTP context they could easily be rescued and a more specific HTTP exception be raised in its place.