Skip to content

Release 9.1.0#228

Merged
StephenWakely merged 3 commits intomasterfrom
release/9.1.0
Apr 28, 2026
Merged

Release 9.1.0#228
StephenWakely merged 3 commits intomasterfrom
release/9.1.0

Conversation

@StephenWakely
Copy link
Copy Markdown
Contributor

@StephenWakely StephenWakely commented Apr 27, 2026

Release 9.1.0

Changelog and version bump for the 9.1.0 NuGet release.

Checklist

  • Changelog entries are accurate
  • Version numbers are correct
  • PR approved and ready to merge

Once merged, run /publish-release to tag, build, and push to NuGet.

@StephenWakely StephenWakely requested a review from a team as a code owner April 27, 2026 11:14
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f265e42c4c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread CHANGELOG.md Outdated

## Changes

* [FEATURE] Add synchronous mode for serverless environments. Set `StatsdConfig.SynchronousMode = true` to bypass the async background worker and send metrics directly on the calling thread, eliminating metric loss on sandbox freeze in AWS Lambda and similar runtimes. See [#227][].
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Document the required Flush call for synchronous mode

When users enable this in a serverless handler and emit only a small batch of metrics, StatsdConfig.SynchronousMode = true does not by itself send every metric immediately: the builder still keeps the default client-side aggregators and SynchronousSender.Send only routes into BufferBuilder, so data stays buffered until Flush() (or a full packet) forces it out. The existing API docs mention calling Flush() at the end of each invocation, but this release note says setting the flag alone eliminates sandbox-freeze loss, which can lead Lambda users to drop metrics on freeze.

Useful? React with 👍 / 👎.

<PackageId>DogStatsD-CSharp-Client</PackageId>
<TargetFrameworks>net461;netstandard2.0;netcoreapp3.1;net6.0</TargetFrameworks>
<LangVersion>latest</LangVersion>
<PackageVersion>9.1.0</PackageVersion>
Copy link
Copy Markdown
Contributor Author

@StephenWakely StephenWakely Apr 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do not bump <Version> as per here.

Comment thread CHANGELOG.md
Comment on lines +294 to +296
[#209]: https://github.com/DataDog/dogstatsd-csharp-client/issues/209
[#211]: https://github.com/DataDog/dogstatsd-csharp-client/issues/211
[#213]: https://github.com/DataDog/dogstatsd-csharp-client/issues/213
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these just commits that were missing from other change log entries?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, they are from 9.0.0.

@carlosroman carlosroman self-requested a review April 28, 2026 10:15
@StephenWakely StephenWakely merged commit 0fdff60 into master Apr 28, 2026
27 checks passed
StephenWakely added a commit that referenced this pull request Apr 28, 2026
Largely following the release process outlined
[here](https://datadoghq.atlassian.net/wiki/spaces/AM/pages/2523399106/DogStatsD-CSharp-Client)
add a couple of skills.

1. prepare the release (#228 is the first example of this)
2. push the new release to nuget
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants