القائمة
Cut a release - CHANGELOG finalization, GitHub Release with a MinVer semver tag, and NuGet publish verification. Use when asked to release, tag, or publish a new version (stable or preview).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Run the BenchmarkDotNet suites in Example.Benchmarks and compare before/after results. Use when a change touches crypto hot paths (LogWriter, Writers/, Core) or when asked to benchmark or update README performance numbers.
Guardrailed checklist for introducing a new on-disk format version (e.g. v3). Use when a change cannot avoid altering the encrypted log wire format - new fields, different AAD, header changes, new record types.
Generate and register a frozen on-disk format fixture (encrypted .log + .expected.txt pair) for backward-compatibility testing. Use before a format-version bump to freeze the outgoing format, or when a new compat scenario needs a pinned fixture.
Verify the frozen v1 fixtures are untouched and still decrypt byte-exact. Use after any change to Decrypt/Core code, before merging a branch that touches readers or the on-disk format, or when asked to check v1 backward compatibility.
استنادا إلى تصنيف SOC المهني
| name | release |
| description | Cut a release - CHANGELOG finalization, GitHub Release with a MinVer semver tag, and NuGet publish verification. Use when asked to release, tag, or publish a new version (stable or preview). |
Versioning is MinVer: the version comes from the git tag on the released commit. Tags are
bare semver with NO v prefix (5.0.0, 6.0.0-preview.1) — ignore the ancient v*
tags in history. Publishing is fully automated: creating a GitHub Release triggers
.github/workflows/publish.yaml → dotnet make publish → nuget.org (OIDC key, no secrets
to handle). Never hand-edit version numbers anywhere.
Preconditions — confirm before anything else:
main, up to date, clean tree; CI green for HEAD (gh run list --branch main -L 3).gh release list -L 5 to see the latest version; pick the next one per semver
(breaking → major; preview suffix -preview.N for pre-releases).CHANGELOG (stable releases): change ## [X.Y.Z] - Unreleased to the release date
(## [X.Y.Z] - YYYY-MM-DD). Follows Keep a Changelog. Commit via PR if branch protection
requires it. Previews can release with the section still Unreleased.
Confirm with the user the exact version and target commit — a release is public and publishes to nuget.org; it cannot be quietly undone.
Create the release (this creates the tag):
gh release create <version> --title "<version>" --notes "<summary or CHANGELOG excerpt>"
Add --prerelease for -preview.N versions. Add --target <sha> if not releasing HEAD.
Verify the publish: gh run watch the publish.yaml run, then confirm the packages
(Encrypt, Decrypt, Cli, Core) show the new version:
dotnet package search Serilog.Sinks.File.Encrypt --exact-match --prerelease
gh run rerun <id>); do
not delete/recreate tags — nuget.org versions are immutable once pushed.MinVerSkip is set for Debug builds — version checks must use Release builds.