Bump to 2.29.0 #489
Bump to 2.29.0 #489
Conversation
matthewfala
force-pushed
the
bump-2.29.0
branch
2 times, most recently
from
d85add3 to
a34236b
Compare
CHANGELOG.md
Outdated
| Compared to `2.28.4` this release adds: | ||
| * Feature - Add `store_dir_limit_size` option [fluent-bit-docs:971](https://github.com/fluent/fluent-bit-docs/pull/971) | ||
| * Feature - New filter for AWS ECS Metadata [fluentbit:5898](https://github.com/fluent/fluent-bit/pull/5898) | ||
| * Enhancement - Resolve Fluent Bit networking hangs affecting CloudWatch plugin by migrating to async networking + sync core scheduler [fluent-bit:6339](https://github.com/fluent/fluent-bit/pull/6339) |
There was a problem hiding this comment.
this hsould be called out as a Bug entry
CHANGELOG.md
Outdated
| Compared to `2.28.4` this release adds the following feature that we are working on getting accepted upstream: | ||
|
|
||
| * Feature - Kinesis FireHose and Streams nanoseconds and milliseconds `time_key_format` support [fluentbit:2831](https://github.com/fluent/fluent-bit/issues/2831) | ||
| * Bug - Use log timestamp as s3 file timestamp [aws-for-fluent-bit:460](https://github.com/aws/aws-for-fluent-bit/issues/460) |
There was a problem hiding this comment.
nit: Use log timestamp for s3 key timestamp is more clear IMO
There was a problem hiding this comment.
Blocking this merge until @Claych PRs are approved and tested. If we want to still release, we need to remove those cherry picks.
matthewfala
force-pushed
the
bump-2.29.0
branch
3 times, most recently
from
6c0c3f6 to
8587f96
Compare
matthewfala
force-pushed
the
bump-2.29.0
branch
from
8587f96 to
acd4853
Compare
|
@PettitWesley I split the release commits. 2.29.0 -> Fluent Bit 1.9.10 with no cherry-picks Please see 2.29.1 for the cherry-picks This way if the cherry-picked code has unforseen issues we'll still have a stable image with the cloudwatch hang resolution. Working with Clay on testing the changes |
There was a problem hiding this comment.
@matthewfala Good idea 💪, splitting up many changes into two releases; I should've thought of that myself.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.