chore: release 1.2.0 - #32
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
1 participant
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.
Releases 1.2.0: bumps
pubspec.yamlto 1.2.0 and renames## Unreleasedto## 1.2.0inCHANGELOG.md. No other changes.Contents: #20, #23 and #26. That's llama.cpp 7fe450e1 parity fixes for macros, unary operators, whitespace,
strftime_now, loops,caller()and filters on none, plus the new README and pub.dev metadata. It's a minor release because it adds public API (BlankExpression, theformatfilter) and some templates that used to render now throw, as in llama.cpp. The changelog lists each case.Input-marking follow-ups #30 and #31 are not included.
Gates at
fbe9f6e: format 0 changed,analyze --fatal-infosclean, VM 1069 pass (11 skipped), Chrome CI lane 967 pass (11 skipped),pub publish --dry-run0 warnings.After merge, tag the merge commit
v1.2.0to publish.