Skip to content

The version goes to 0.2.0, and a tag now cuts a release - #7

Merged
alex1075 merged 1 commit into
mainfrom
release/0.2.0
Aug 25, 2026
Merged

alex1075 merged 1 commit into
mainfrom
release/0.2.0

Conversation

@alex1075

Copy link
Copy Markdown
Member

The package changed shape in #6. It lost its server, its runtime and its FLIMKit adapter, and now declares flimkit-bridge instead, so it earns a number rather than shipping as 0.1.0 with different contents.

Two workflows it did not have. release.yml creates the GitHub release, which is what the Zenodo hook archives; without it a tag would produce no record. publish.yml puts the package on PyPI, which it has never been on, so that needs a pending publisher registering before the tag.

The setup instructions in the README also install flimkit-bridge now. Without it pip install -e '.[test]' cannot resolve the add-on, which is the same failure that took out CI on the other two repos.

🤖 Generated with Claude Code

The package changed shape in #6: it lost its server and declares
flimkit-bridge instead, so it earns a number rather than shipping as
0.1.0 with different contents.

release.yml creates the GitHub release the Zenodo hook archives, and
publish.yml puts the package on PyPI, which it has never been on. The
setup instructions install flimkit-bridge, without which pip cannot
resolve the add-on.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@alex1075
alex1075 merged commit d515683 into main Aug 25, 2026
2 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