Repository navigation
Tags
Tags
ci(signing): use ssign for certum packages - Replace SimplySign desktop automation with the reference ssign signing job. - Add checksum-pinned ssign and Jsign setup with Java 21 and .NET verification. - Reuse existing Certum secrets and remove the private session cache on exit. - Require each package signature to match the configured certificate before upload.
Fix sign job failure: python3 missing in certum-signer container (#392) * Initial plan * Fix sign job: ensure python3 is available before OTP generation Co-authored-by: ChrisPulman <4910015+ChrisPulman@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: ChrisPulman <4910015+ChrisPulman@users.noreply.github.com>
feat(hosting): add direct plugins, WPF factories, and structured logs (… …#367) * feat(hosting): add direct plugins, WPF factories, and structured logs Add direct IPlugin registration for both host builders and the Reactive package, preserving builder-specific timing and caller-owned instance lifetimes. Add deferred WPF application factories with DI-backed singleton aliases, plus typed Log4Net message-template properties for layouts and appenders. Document the new APIs and add TUnit coverage for normal/Reactive plugins, WPF factory behavior, and structured logging fields. * Update ReactiveUI package versions Bump the ReactiveUI.Primitives packages and related dependency versions to 7.4.0 to stay aligned with the current ReactiveUI stack. This also rolls back Tmds.DBus.Protocol to 0.95.1 to match the repository's resolved dependency set and avoid version drift.
fix(build): skip symbols packages during NuGet publish (#268) * fix(build): skip symbols packages during NuGet publish Release workflow: - Filter signed publish inputs so legacy *.symbols.nupkg artifacts are not pushed to NuGet as primary packages. - Add --skip-duplicate so reruns after partial publishes continue with remaining packages. Validation: - Simulated the publish package selection with primary and symbols packages. - Ran git diff --check. * fix(build): stop producing legacy symbol packages Release packaging: - Remove the shared IncludeSymbols property that caused legacy *.symbols.nupkg packages to be emitted by dotnet pack. - Exclude legacy symbols packages from unsigned and signed release artifacts before the signing and publishing jobs. - Simplify the NuGet publish loop now that signed artifacts contain only primary .nupkg files. Validation: - Packed Extensions.Hosting.Avalonia for net8.0 and confirmed only the primary .nupkg was produced. - Checked effective MSBuild properties for IncludeSymbols, SymbolPackageFormat, DebugType, and EmbedUntrackedSources. - Ran git diff --check.
Update deps: bump versions, add security package, TUnit (#208) * Update deps: bump versions, add security package, TUnit Bump CoreVersion to 10.0.7 and AvaloniaVersion to 12.0.2 in Directory.Build.props. Add System.Security.Cryptography.Xml v10.0.7 to the Sqlite and SqlServer EF project files to address security advisories (GHSA-37gx-xxp4-5rgx and GHSA-w3x6-4m5h-cxqf). Normalize spacing in TUnit Using entries and update TUnit to version 1.43.11 in the test project. * Update Extensions.Hosting.Maui.Example.csproj
PreviousNext