Document release publication, and align repository layout - #9
Merged
Merged
Conversation
The release and catalog notification guide moves from .github/RELEASE.md to Documentation/Reference/Release.md. It now describes the actual publication steps: tag, commit-bound draft, release.yml promotion of the CI artifacts, and publish. It also names the credentials the notification workflow reads, CATALOG_APP_CLIENT_ID and CATALOG_APP_PRIVATE_KEY. CHANGELOG.md records the published releases, and the one-off 0.2.1 release notes page is removed because the GitHub Release holds them. Workflows are renamed to ci.yml and release.yml with unchanged job names. The release workflow and the Windows artifact check accept source runs from ci.yml. The unused optionalBoundedInt helper is removed. CODEOWNERS is added, AGENTS.md follows the current canonical agent guide, CONTRIBUTING lists the checks CI runs, the documentation index covers every page, and public docs state current facts without edit history or local agent directories.
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.
Docs
.github/RELEASE.mdmoves toDocumentation/Reference/Release.md, which now spells out the real publication flow: signed tag, commit-bound draft,release.ymlpromotion of both CI artifacts, publish. It names the credentialsnotify-catalog.ymlactually reads (vars.CATALOG_APP_CLIENT_ID,secrets.CATALOG_APP_PRIVATE_KEY); the old text namedCATALOG_DISPATCH_TOKEN.CHANGELOG.mdcovering 0.1.0 through 0.3.0, taken from the GitHub Releases. RemovesDocumentation/Reference/ReleaseNotes-0.2.1.md; the GitHub Release holds those notes.VersioningAndRelease.mdlinks the changelog and the release guide.README.mdandPackage.mdstate current facts instead of edit history. Public docs no longer point to.agent/.CONTRIBUTING.mdlists the checks CI runs, andAGENTS.mdfollows the current canonical template.CI
validate.ymltoci.ymlandupload-release.ymltorelease.yml; job names are unchanged. The release workflow's source-run check andScripts/check-windows-artifact.ps1now expect.github/workflows/ci.yml. After this merges, a release must come from aci.ymlrun..github/CODEOWNERS.Code
optionalBoundedIntfromCodexAppServerProvider.swift.Validation: locally,
version.py check,Package.resolvedunchanged after resolve,import-schema.mjs --check, the schema-import node test, strict format lint,swift build --build-testsand 38 Python tests all pass.