docs(changelog): an Unreleased section, so that the release bot publishes what 0.1.11 could not #53
No reviewers
Labels
No labels
ansible
bug
ci
dependencies
digest
docker
documentation
duplicate
enhancement
fix
go
good first issue
help wanted
invalid
javascript
major
minor
patch
php
python
question
released
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
dawid/langchain-memvid!53
Loading…
Reference in a new issue
No description provided.
Delete branch "release-0.1.11-again"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
v0.1.11was tagged by the release bot, but its release job failed in the tests: the logging tests fail under pytest 9.1, fixed on main after the tag (035f278). So 0.1.11 never reached PyPI, and retrying the tag cannot work (run #7). Since the tag, onlytestandcicommits came, which call for no release.This adds a hand-written
## Unreleasedwith### Fixed, so that the bot's next release (or Release on the repository's page after merging) makes 0.1.12, which publishes 0.1.11's changes with the fixed tests.