You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme.md
+38Lines changed: 38 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,6 +45,11 @@ Please see the [project documentation](https://socketry.github.io/falcon/) for m
45
45
46
46
Please see the [project releases](https://socketry.github.io/falcon/releases/index) for all releases.
47
47
48
+
### v0.49.0
49
+
50
+
-[Falcon Server Container Health Checks](https://socketry.github.io/falcon/releases/index#falcon-server-container-health-checks)
51
+
-[Falcon Server Process Title](https://socketry.github.io/falcon/releases/index#falcon-server-process-title)
52
+
48
53
### v0.48.4
49
54
50
55
- Improve compatibility of rackup handler w.r.t. sinatra.
@@ -53,6 +58,39 @@ Please see the [project releases](https://socketry.github.io/falcon/releases/ind
53
58
54
59
- Fix Falcon Supervisor implementation: due to invalid code, it was unable to start.
55
60
61
+
### Compatibility Fixes
62
+
63
+
During the `v0.44.0` release cycle, the workflows for testing older rack releases were accidentally dropped. As such, `v0.44.0` was not compatible with older versions of rack. This release restores compatibility with older versions of rack.
64
+
65
+
Specifically, `protocol-rack` now provides `Protocol::Rack::Adapter.parse_file` to load Rack applications. Rack 2's `Rack::Builder.parse_file` returns both the application and a set of options (multi-value return). Rack 3 changed this to only return the application, as the prior multi-value return was confusing at best. This change allows `protocol-rack` to work with both versions of rack, and `falcon` adopts that interface.
66
+
67
+
### Falcon Serve Options
68
+
69
+
In addition, `falcon serve` provides two new options:
70
+
71
+
1.`--[no]-restart` which controls what happens when `async-container` instances crash. By default, `falcon serve` will restart the container when it crashes. This can be disabled with `--no-restart`.
72
+
73
+
2.`--graceful-stop [timeout]` which allows you to specify a timeout for graceful shutdown. This is useful when you want to stop the server, but allow existing connections to finish processing before the server stops. This feature is highly experimental and doesn't work correctly in all cases yet, but we are aiming to improve it.
74
+
75
+
### Falcon Host
76
+
77
+
`async-service` is a new gem that exposes a generic service interface on top of `async-container`. Previously, `falcon host` used `async-container` directly and `build-environment` for configuration. In order to allow for more generic service definitions and configuration, `async-service` now provides a similar interface to `build-environment` and exposes this in a way that can be used for services other tha falcon. This makes it simpler to integrate multiple services into a single application.
78
+
79
+
The current configuration format uses definitions like this:
Copy file name to clipboardExpand all lines: releases.md
+20-22Lines changed: 20 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Releases
2
2
3
-
## Unreleased
3
+
## v0.49.0
4
4
5
5
### Falcon Server Container Health Checks
6
6
@@ -12,23 +12,21 @@
12
12
13
13
The Falcon server process title is now updated periodically (alongside the health check) to include information about the numnber of connections and requests.
-**C** – Connections: `(current/total)` connections accepted by the server
28
+
-**R** – Requests: `(current/total)` requests processed by the server
29
+
-**L** – Scheduler Load: A floating-point value representing the event loop load
32
30
33
31
## v0.48.4
34
32
@@ -50,9 +48,9 @@ Specifically, `protocol-rack` now provides `Protocol::Rack::Adapter.parse_file`
50
48
51
49
In addition, `falcon serve` provides two new options:
52
50
53
-
1.`--[no]-restart` which controls what happens when `async-container` instances crash. By default, `falcon serve` will restart the container when it crashes. This can be disabled with `--no-restart`.
51
+
1.`--[no]-restart` which controls what happens when `async-container` instances crash. By default, `falcon serve` will restart the container when it crashes. This can be disabled with `--no-restart`.
54
52
55
-
2.`--graceful-stop [timeout]` which allows you to specify a timeout for graceful shutdown. This is useful when you want to stop the server, but allow existing connections to finish processing before the server stops. This feature is highly experimental and doesn't work correctly in all cases yet, but we are aiming to improve it.
53
+
2.`--graceful-stop [timeout]` which allows you to specify a timeout for graceful shutdown. This is useful when you want to stop the server, but allow existing connections to finish processing before the server stops. This feature is highly experimental and doesn't work correctly in all cases yet, but we are aiming to improve it.
56
54
57
55
# v0.44.0
58
56
@@ -62,13 +60,13 @@ In addition, `falcon serve` provides two new options:
62
60
63
61
The current configuration format uses definitions like this:
0 commit comments