Skip to content

upd: atualiza CHANGELOG - #5

Merged
brunobrown merged 1 commit into
mainfrom
dev
Mar 6, 2026
Merged

upd: atualiza CHANGELOG#5
brunobrown merged 1 commit into
mainfrom
dev

Conversation

@brunobrown

@brunobrown brunobrown commented Mar 6, 2026

Copy link
Copy Markdown
Owner

Summary by Sourcery

Documentation:

  • Revise CHANGELOG to reflect version 0.1.1 and remove outdated 0.1.0 release link.

@sourcery-ai

sourcery-ai Bot commented Mar 6, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the changelog to reflect a new patch version 0.1.1 released on 2026-03-05 and removes the explicit link reference for version 0.1.0.

File-Level Changes

Change Details Files
Bump documented version from 0.1.0 to 0.1.1 in the changelog header.
  • Change the changelog section header to use version 0.1.1 instead of 0.1.0 while keeping the same date.
CHANGELOG.md
Clean up trailing reference link for version 0.1.0 in the changelog.
  • Remove the bottom-of-file markdown reference definition for [0.1.0].
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

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.56%. Comparing base (160402d) to head (c18d805).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #5   +/-   ##
=======================================
  Coverage   78.56%   78.56%           
=======================================
  Files          35       35           
  Lines        4643     4643           
=======================================
  Hits         3648     3648           
  Misses        995      995           
Flag Coverage Δ
unittests 78.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@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 found 1 issue

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="CHANGELOG.md" line_range="34" />
<code_context>
 - **Dart control-flow filtering** — false method matches from `catch`/`finally`/`then` patterns are excluded from generation.
 - **Test suite** — 383 tests covering models, type map, downloader, analyzer, generators, pipeline, scaffolder, CLI, validators, and coverage.
 - **CI/CD** — GitHub Actions workflows for `dev` and `main` branches with ruff, ty, pytest, and mkdocs build.
-
-[0.1.0]: https://github.com/brunobrown/flet-pkg/releases/tag/v0.1.0
</code_context>
<issue_to_address>
**question (typo):** Clarify whether `ty` is the intended tool name in the CI/CD description.

In the CI/CD bullet, is `ty` the intended tool name, or a typo for something else? If it is correct, consider defining or expanding it somewhere so readers know what it refers to.
</issue_to_address>

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.

Comment thread CHANGELOG.md
@@ -32,5 +32,3 @@
- **Dart control-flow filtering** — false method matches from `catch`/`finally`/`then` patterns are excluded from generation.
- **Test suite** — 383 tests covering models, type map, downloader, analyzer, generators, pipeline, scaffolder, CLI, validators, and coverage.
- **CI/CD** — GitHub Actions workflows for `dev` and `main` branches with ruff, ty, pytest, and mkdocs build.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

question (typo): Clarify whether ty is the intended tool name in the CI/CD description.

In the CI/CD bullet, is ty the intended tool name, or a typo for something else? If it is correct, consider defining or expanding it somewhere so readers know what it refers to.

@brunobrown
brunobrown merged commit bff1e69 into main Mar 6, 2026
3 checks passed
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