Align build cycle and CI/CD with canonical protocol - #2
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
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.
Align
Icod.Timingwith the canonical Icod C#/.NET development lifecycle while preserving its net7.0/net8.0/net9.0/net10.0 library contract.Base:
main@9364b93d3bbca2e19a3be5fae850e2b77bcb39f1Lifecycle
build.cmd/build.sh:DebugStagingon Windows/Linux/macOSmain: validation-only six-runnerReleasev<semver>tags whose commit is contained inmain:ReleasepublicationPackaging
Icod.Timing.nupkg+ matching.snupkgverificationnet7.0,net8.0,net9.0, andnet10.0Icod.Timing.csprojis packedDebug information
Debug,Staging, andReleaseall explicitly use portable debug information. This is set in the library, test, and sample projects so the repository does not depend on SDK defaults.Publication safety
The old
push-main.yamlpublished on ordinary pushes tomain; it is removed.main.yamlis validation-only. Publication now occurs only fromrelease.yamlafter tag/main-containment and exactPackageVersionchecks.NuGet.org and GitHub Packages consume the same validated package and publish in parallel. GitHub Release is the final rendezvous.
README
The root README now includes
PR Staging buildandMain Release validationbadges and documents the Debug → Staging → Release → tagged-publication lifecycle.Validation
PR workflow run
33593598660succeeded on head6f8ebdb2b4b00d69d8915cd4283b50d5d218d9cb:.nupkg+.snupkgproduction: successThe tag-only publication graph will receive its first runtime execution on the next normal immutable release tag.