chore: prepare release v1.4.2#74
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| <!-- NuGet Package Metadata --> | ||
| <PackageId>TriasDev.Templify</PackageId> | ||
| <Version>1.4.1</Version> | ||
| <Version>1.4.2</Version> |
There was a problem hiding this comment.
Version is bumped to 1.4.2 here, but CHANGELOG.md still has 1.4.1 as the latest entry and the [Unreleased] compare link points to v1.4.1. For a release prep PR, update CHANGELOG.md to add a 1.4.2 section and advance the compare links so the changelog stays consistent with the published package version.
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.
Summary
Release Notes
Fixed
True/False/TRUE/FALSEare now correctly compared regardless of case, while preserving case-sensitive string comparisons (fix: case-sensitive boolean comparison in ConditionalEvaluator.AreEqual #72, fix: case-insensitive boolean comparison in ConditionalEvaluator #73)Test Coverage
Test plan