`release --dry-run a` actually changes version.txt (and bumped only that file)

[acsr]

Issue

When running repoplone version 1.0.0a7 the first time creating a test release, when I use the --dry-run option the version file ./version.txt is actually bumped for the next alpha version.

Other files mentioned in the execution progress not changed.

My command and shell outputs

To Reproduce

Steps to reproduce the behavior:

1. Go to VScode in the local repo
2. Open a new terminal in the root
3. run repoplone without install using uvx
4. run uvx repoplone options and commands to check if it is working

                   Current versions                 
   ┏━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┓
   ┃ Section    ┃ Name             ┃ Version       ┃
   ┡━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━┩
   │ Repository │ acsr-plone       │ 1.0.0a0       │
   │ Backend    │ acsr.plone       │ 1.0.0a0       │
   │ Frontend   │ volto-acsr-plone │ 1.0.0-alpha.0 │
   └────────────┴──────────────────┴───────────────┘
   

   Full Next versions output skipped

                                     Possible next version                                  
   ┏━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━┓
   ┃ Current Version ┃ Desidered Version ┃ Repository    ┃ Backend       ┃ Frontend        ┃
   ┡━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━┩
   ...
   │ 1.0.0a0         │ a                 │ 1.0.0a1       │ 1.0.0a1       │ 1.0.0-alpha.1   │
   

             Dependencies versions           
   ┏━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┓
   ┃ Section  ┃ Name              ┃ Version ┃
   ┡━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━┩
   │ Backend  │ Products.CMFPlone │ 6.1.1   │
   │ Frontend │ @plone/volto      │ 18.11.1 │
   │ Frontend │ @plone/volto      │ 18.11.1 │
   └──────────┴───────────────────┴─────────┘
   

5. run uvx repoplone release --dry-run a

Release my-repo

1/8 Next version
   - Bump version from 1.0.0a0 to 1.0.0a1
   Continue? [y/n] (y): 

2/8 Display Changelog
   ==================================================
   ## 1.0.0a1 (2025-09-17)

   ### Backend
   No significant changes.
   
   ### Frontend
   No significant changes.

   ### Project
   No significant changes.
   ==================================================
   Continue? [y/n] (y): 

3/8 Update repository components
   - Updated [repopath]/version.txt file
   - Updated [repopath]/docker-compose.yml file

4/8 Release backend
   - Released my-repo: 1.0.0a1

5/8 Release frontend
   - Released volto-my-repo: 1.0.0-alpha.1

6/8 Commit changes, create tag
   - Skipped creating tag 1.0.0a1

7/8 Create GitHub release
   - Skipping GitHub release creation

8/8 Goodbye
   - Completed the release of version 1.0.0a1
   Continue? [y/n] (y): 

Result

Instead of a dry run the version string in ./version.txt was actually bumped from 1.0.0a0 to 1.0.0a1

NOTE: same result if you either answer 8/8 with y or n!

Expected behavior

Do nothing with existing files

---

Software:

• repoplone version 1.0.0a7
• OS: macOS Sequoia 15.6.1
• Plone Version 6.1.1
• Volto Version 18.11.1
• Plone REST API Version 9.13.3

Additional context

Not tested with other target types (beta etc.)!

• This happened during an initial test of repoplone
• Changelog lists no significant changes, changelog in issue was trimmed manually to remove empty lines to keep it short
• I have no target or API Token set to release on PyPi
• I have no npm auth set (and no intention to publish there)
• I do not publish this project publicly on github
• I use github for this monorepo and github actions to deploy to a server
• I plan to move that project to our private gitlab