fsm

What's Changed

• Deadlock calling Event in after-event callback when current state == dst by @kuzmig in https://github.com/looplab/fsm/pull/104

New Contributors

• @kuzmig made their first contribution in https://github.com/looplab/fsm/pull/104

Full Changelog: https://github.com/looplab/fsm/compare/v1.0.1...v1.0.2

What's Changed

• race fixes by @eminden in https://github.com/looplab/fsm/pull/94

New Contributors

• @eminden made their first contribution in https://github.com/looplab/fsm/pull/94

Full Changelog: https://github.com/looplab/fsm/compare/v1.0.0...v1.0.1

What's Changed

• fix: typo on comments by @noneback in https://github.com/looplab/fsm/pull/74
• Add linter and fix simple linter warnings by @majst01 in https://github.com/looplab/fsm/pull/85
• Highlight current state in Graphviz visualizer by @baw-benji in https://github.com/looplab/fsm/pull/84
• Add context to Event method, callback handlers and canceling an event by @annismckenzie in https://github.com/looplab/fsm/pull/82
• Allow transitions in callbacks by @annismckenzie in https://github.com/looplab/fsm/pull/88
• Add ability to delete from fsm metadata by key by @abramlab in https://github.com/looplab/fsm/pull/93

New Contributors

• @noneback made their first contribution in https://github.com/looplab/fsm/pull/74
• @majst01 made their first contribution in https://github.com/looplab/fsm/pull/85
• @baw-benji made their first contribution in https://github.com/looplab/fsm/pull/84
• @annismckenzie made their first contribution in https://github.com/looplab/fsm/pull/82
• @abramlab made their first contribution in https://github.com/looplab/fsm/pull/93

Full Changelog: https://github.com/looplab/fsm/compare/v0.3.0...v1.0.0

• Support for metadata #63
• mermaid: Use stateDiagram-v2 to beautify state diagram. #65
• Fix / Use GitHub Actions #66

• Add mermaid graph output #50 #54 #56
• Fix mutex unlock error on callback panic #55
• Bump to Go 1.13 #51
• Fix doc typo #58
• Fix to use ReplaceAll #52

This is the first tagged release of FSM!
However the API is not stable yet, which is reflected by the <v1.0 version.