Release 1.1.0: Maintenance & Safety - #1
Merged
Merged
Conversation
Closes 14 known vulnerabilities (1 critical, 8 high severity). No API changes; all templates render correctly.
- net9.0 -> net10.0 in MTC, tests, and all 7 template projects - Update framework-coupled packages: Spectre.Console 0.54.0 -> 0.57.2 - CI: dotnet-version 9.0.x -> 10.0.x - Integration tests locate binary dynamically, not hardcoded framework
- mtc new ConsoleApp MyApp: name now positional argument - Default name resolves correctly (no literal '.') - Commands exit 1 on error, not 0 - Don't share Argument/Option instances across commands - Remove debug output from Program.cs
- Reference-typed properties get 'required' modifier (CS8618 fix)
- Control whitespace with {{~ ~}} so indentation is hand-written style
- Introduce Property.IsValueType to detect value types
- Expand field type aliases: long, short, byte, float, double, char, dateonly, timeonly
- Template packages pinned to 10.0.10; Microsoft.OpenApi pinned to 2.11.0
- ScaffoldingService plans all writes before touching disk (all-or-nothing) - Conflicting files abort the entire operation; nothing partial is written - New --force flag for all generate commands (new, add feature, add value-object, add dto) - Path traversal protection: rendered names cannot escape output directory - All architecture branches (direct, via temp, CleanArch copy) protected equally
Workflow triggers on v*, V* but only parsed V. prefix. Tags v1.1.0, V1.1.0, V.1.1.0, and 1.1.0 all now produce valid Debian versions.
- 13 new tests for type mapping and value-type detection - 11 new tests for scaffolding: overwrite detection, path traversal, all-or-nothing writes - Remove empty UnitTest1.cs placeholder files - Total test count: 8 -> 31 (across unit and integration)
- README refocused on 'add feature' as the core value proposition - CONTRIBUTING: setup guide, code map, template authoring rules - CHANGELOG: Keep a Changelog format, SemVer, full history for 1.0.x and 1.1.0 - Explain --force flag and write-safety model
- MTC.csproj: 1.0.2 -> 1.1.0 - publish.sh: VERSION=1.0.2 -> 1.1.0
JuansesDev
added a commit
that referenced
this pull request
Aug 4, 2026
Release 1.1.0: Maintenance & Safety
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.
Summary
Maintenance release after 8 months. Targets .NET 10, patches critical Scriban vulnerabilities, and eliminates silent file overwrites.
Security
Major Changes
mtc newnow accepts project name as positional argument--force; all-or-nothing generationrequiredmodifier)Test Coverage
Docs
Changes
9 commits distributed across January–April 2025, release tag today.
Test plan