Skip to content

fix: a release no longer fails when the version file already holds its version (EAI-475) - #1

Merged
0-vortex merged 4 commits into
mainfrom
eai-475-version-check
Nov 11, 2026
Merged

0-vortex merged 4 commits into
mainfrom
eai-475-version-check

Conversation

@0-vortex

@0-vortex 0-vortex commented Nov 11, 2026 •

Copy link
Copy Markdown
Member

A release no longer fails when deno.json or pyproject.toml already holds the version being released. Each block checks for its one version line: without it, it warns and skips the replacement; with it, it replaces the version without requiring the file to change.

Linear: EAI-475

Deviations

  • results doesn't keep "numMatches": 1 alone: the plugin compares results with isEqual (dist/index.js:79) against { file, hasChanged, numMatches, numReplacements }, so it would fail every release. The one-line check covers the single match.

@0-vortex

Copy link
Copy Markdown
Member Author

LGTM! 👍

@0-vortex
0-vortex merged commit ba1d16c into main Nov 11, 2026
4 checks passed
@0-vortex
0-vortex deleted the eai-475-version-check branch November 11, 2026 19:58
github-actions Bot pushed a commit that referenced this pull request Nov 11, 2026
## [1.0.4](v1.0.3...v1.0.4) (2026-11-11)

### 🐛 Bug Fixes

* a release no longer fails when the version file already holds its version (EAI-475) ([#1](#1)) ([ba1d16c](ba1d16c))
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