Repository navigation
Terminal core: prism-term-core core-v0.28.0 (Prism 0.100.0) - #342
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Opened automatically by PrismTerminal's
core-releaseworkflow: the shared terminal core released core-v0.28.0, and Prism pinnedgithub:Maxaubert/PrismTerminal#core-v0.27.1. This bumps the pin and makes Prism 0.100.0 (minor).What changed in the core: https://github.com/Maxaubert/PrismTerminal/commits/main/core
The checks on this PR are the proof: typecheck, lint, the unit suite, and terminal-gate, which builds the app on a Windows runner and drives every scenario the terminal can break, real dictation included.
If the repo variable
PRISM_AUTO_MERGEin PrismTerminal istrue, this merges itself once every check is green and Prism releases 0.100.0. Otherwise it waits here for a person. A red check never merges.