Skip to content

release: 0.2.1#103

Merged
chaoming0625 merged 1 commit into
mainfrom
worktree-release-0.2.1
Jun 18, 2026
Merged

release: 0.2.1#103
chaoming0625 merged 1 commit into
mainfrom
worktree-release-0.2.1

Conversation

@chaoming0625

@chaoming0625 chaoming0625 commented Jun 18, 2026

Copy link
Copy Markdown
Collaborator

Summary

Prepare the 0.2.1 maintenance release.

  • Bump braintrace/_version.py from 0.2.00.2.1.
  • Add a ## Version 0.2.1 section to changelog.md.

0.2.1 is a maintenance release that restores compatibility with the latest
brain-ecosystem dependencies and toolchain (brainstate 0.5, saiunit/
brainunit 0.5.1, pytest 9.1), shipped in #102. There are no functional
or public-API changes
— code written against 0.2.0 works unchanged.

The Publish workflow verifies the release tag matches braintrace/_version.py,
so this bump is required before tagging v0.2.1.

Verification

From #102, verified locally: full suite 1367 passed (2 xfailed), mypy clean
across 51 files, and wheel + sdist build with py.typed shipped (PEP 561).

Summary by Sourcery

Prepare the 0.2.1 maintenance release to restore compatibility with updated brain-ecosystem dependencies and testing/tooling stack.

Bug Fixes:

  • Restore compatibility with brainstate 0.5, saiunit/brainunit 0.5.1, and pytest 9.1 without changing public APIs or behavior.

Enhancements:

  • Document the 0.2.1 maintenance release details, including dependency compatibility updates and verification status, in the changelog.

Build:

  • Bump the internal package version from 0.2.0 to 0.2.1 for the new release.

Bump version to 0.2.1 and add changelog entry for the brainstate 0.5 /
pytest 9.1 dependency-compatibility maintenance release (#102).
@sourcery-ai

sourcery-ai Bot commented Jun 18, 2026

Copy link
Copy Markdown

Reviewer's Guide

Prepares the 0.2.1 maintenance release by bumping the internal version constant and documenting the dependency-compatibility fixes and verification details in the changelog, without introducing any functional or public-API changes.

Sequence diagram for publish workflow version verification

sequenceDiagram
    participant Developer
    participant GitTag as Git_tag_v0_2_1
    participant Repo as braintrace_repo
    participant CI as Publish_workflow

    Developer->>Repo: Update __version__ to 0.2.1
    Developer->>Repo: Update changelog Version_0_2_1 section
    Developer->>GitTag: Create tag v0.2.1
    GitTag->>CI: Trigger publish workflow
    CI->>Repo: Read braintrace/_version.py __version__
    CI->>GitTag: Read tag name v0.2.1
    CI-->>CI: [compare version to tag]
    CI-->>Developer: Publish release if versions match
Loading

File-Level Changes

Change Details Files
Bump the package version constant to 0.2.1 to align with the planned release tag and publish workflow checks.
  • Update the hard-coded version string from 0.2.0 to 0.2.1
  • Keep version_info derived from the updated version without other logic changes
braintrace/_version.py
Document the 0.2.1 maintenance release, focusing on dependency compatibility fixes and test/typing verification, while clarifying that there are no behavior or API changes.
  • Add a new 'Version 0.2.1' section at the top of the release notes
  • Describe restored compatibility with brainstate 0.5, saiunit/brainunit 0.5.1, and pytest 9.1
  • Summarize internal typing, convolution validation, and pytest parametrize-id adjustments that were done in a prior PR and validated for this release
  • Record verification details (test suite, mypy, and build checks) for the release
changelog.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@chaoming0625 chaoming0625 merged commit 5286b30 into main Jun 18, 2026
6 checks passed

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@chaoming0625 chaoming0625 deleted the worktree-release-0.2.1 branch June 18, 2026 02:43
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.

1 participant