Skip to content

Merge main into development after v0.2.0 - #7

Merged
levidurfee merged 1 commit into
developmentfrom
main
Oct 16, 2026
Merged

levidurfee merged 1 commit into
developmentfrom
main

Conversation

@levidurfee

Copy link
Copy Markdown
Contributor

Merges main back into development after the v0.2.0 release, so that development holds the release merge commit and the next release PR starts from the same history. No content changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01NTEjHbdKp83qgQgmqR1BJ6

@levidurfee
levidurfee merged commit 312d9f1 into development Oct 16, 2026
7 checks passed
levidurfee added a commit that referenced this pull request Nov 5, 2026
After a release, CONTRIBUTING.md asks to merge `main` back into
`development` when `main` has commits that `development` lacks. Here
that is only the merge commit of #9 (34cddeb, tagged v0.3.0). The two
trees are identical, so this changes no file.

Merge it with a merge commit, as #7 was after v0.2.0.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01NYjhaGCRVp9GXLUuUZv8g1
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