chore(release): witan-core 0.37.1 - #370
Closed
blarghmatey wants to merge 1 commit into
Closed
blarghmatey wants to merge 1 commit into
blarghmatey wants to merge 1 commit into
Conversation
Releases #363, which keeps dropped OTLP batches out of Sentry. Neither server's witan-core floor moves, because neither uses anything new from it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SAvFi2rNtKeoZZUAjR8wCj
Contributor
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The release metadata is consistent and correctly triggers the established publishing workflow.
Review effort: Balanced
Findings: None
What changed in this PR
Releases witan-core 0.37.1, packaging the Sentry filtering fix from #363.
Changes:
- Aligns package, bumpversion, lockfile, and changelog versions.
- Documents the OTLP dropped-batch filtering change.
| File | Description |
|---|---|
uv.lock |
Updates the workspace package version. |
packages/witan-core/pyproject.toml |
Sets release and bumpversion metadata to 0.37.1. |
packages/witan-core/CHANGELOG.md |
Adds the dated 0.37.1 release heading. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What are the relevant tickets?
Releases #363 (witan task
tk-low-volume-witan-server-lifecycle-errors-in-sent-1f017f).Description (What does it do?)
Bumps witan-core to 0.37.1. The only change since 0.37.0 is #363, which keeps the OTLP exporters' dropped-batch errors out of Sentry. The 0.37.0 version bump landed in #357, and
packages/witan-corehas one commit since then (#363).The witan-council and witan-code floors stay at
witan-core>=0.37, because #363 only adds private names intelemetry.pyand neither server uses them.How can this be tested?
just check-versions: versions consistent across 5 packages.uv.lockmoves only witan-core.publish-witan-core.ymlshould publish 0.37.1 to PyPI.Additional Context
The deployed witan image builds witan-core from the repo (
uv sync --frozen --all-packagesindocker/witan.Dockerfile), so the service picks up #363 on its next image build from main whether or not this is merged. This release is for installs from PyPI.🤖 Generated with Claude Code
https://claude.ai/code/session_01SAvFi2rNtKeoZZUAjR8wCj