Skip to content

v0.2.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 04 Aug 22:04
· 48 commits to main since this release
v0.2.2
df09598

v0.2.2 (2026-08-04)

This release is published under the MIT License.

Bug Fixes

  • Report the update in the verb that ran it (d534189)

The command is update, and --check and the daily notice both say "update", but the success and failure lines said "upgraded" and "upgrade failed". One command, one vocabulary.

Chores

  • Add .planning to gitignore (d10f941)

  • config: Adopt the standard pyright section (2bc0aa8)

Synced from forge pyproject template. With no [tool.pyright] section the editor LSP settings applied, and their ignore = ["*"] suppressed every diagnostic. A config file takes precedence over those settings, so basedpyright now reports against the same "standard" mode as the rest of the portfolio instead of reporting nothing.

  • config: Record the keys the pyproject sync owns (1f3e5a9)

forge now writes [tool.forge] managed, listing the exact keys the standard sets. Deletion on a later sync is scoped to that record, so dropping a key from the template retracts it here without having to guess which settings belong to this project.

Purely additive: nothing else in this file changed.

  • toolchain: Adopt the generated configs and CI (d0be7cf)

Brings the repo onto forge toolchain manifest 11.

bandit, refurb and pyupgrade drop out: pyupgrade is ruff's UP rules, already selected, and the other two are the manifest's deliberate narrowing to the rule set every repo actually runs.

Documentation

  • Flush dormant markdownlint violations (faa11a2)

markdownlint only runs on the files a commit touches, so unmodified docs accumulate violations invisibly. The toolchain sync bumps markdownlint to v0.47, which added MD060, and runs --all-files — surfacing every one of them at once, in the middle of an unrelated change.

Table separators are normalized to the compact | --- | style MD060 expects, which --fix cannot repair; everything else is markdownlint --fix.

  • Format the composed-update example as ruff wants it (9842930)

CI runs ruff format --check ., which formats python blocks inside markdown; the pre-commit hook only sees .py files, so aligned comments in a README example pass locally and fail there.

  • Stop normalizing the generated CHANGELOG (109706e)

semantic-release regenerates CHANGELOG.md on every release, so a markdownlint fix there is undone on the next one and comes back as a conflict when a local commit rebases onto the release.

Detailed Changes: v0.2.1...v0.2.2

Assets 2
Loading