Skip to content

Fix next-release folder recreation after release - #71

Merged
raulgomis merged 1 commit into
masterfrom
fix/next-release-folder-recreation
Jun 7, 2026
Merged

raulgomis merged 1 commit into
masterfrom
fix/next-release-folder-recreation

Conversation

@raulgomis

Copy link
Copy Markdown
Owner

Description

Reusing the same core instance programmatically across multiple releases raised a FileNotFoundError when adding subsequent changesets.

Steps to reproduce

    releaser = Semversioner(path=directory_name)
    releaser.add_change("minor", "First")
    releaser.release()
    releaser.add_change("patch", "Second")

Fix

To resolve this, we updated the create_changeset method in storage.py to check for the directory's existence and recreate it if necessary just-in-time.

@raulgomis raulgomis self-assigned this Jun 7, 2026
@raulgomis
raulgomis merged commit 1c639a2 into master Jun 7, 2026
8 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.

1 participant