Skip to content

Prepare conformance 0.6.2 and combine documentation deployment - #465

Merged
imran-siddique merged 2 commits into
mainfrom
conformance-final-cutover
Oct 3, 2026
Merged

imran-siddique merged 2 commits into
mainfrom
conformance-final-cutover

Conversation

@imran-siddique

@imran-siddique imran-siddique commented Oct 2, 2026 •

Copy link
Copy Markdown
Member

The remaining trace-tests cutover needs its next package release and a documentation deployment from the canonical repository. Prepare agentrust-trace-tests 0.6.2 with the merged, attributed anchor vectors, and build the specification and conformance sites into one Pages artifact: specification at the root, conformance at /conformance/. A single deployment preserves the root CNAME and removes the nested site's CNAME.

Pull requests build and upload the combined site without deploying. Main/manual docs runs deploy the combined artifact. The separate conformance publisher and package identity remain in place; merging this PR does not publish a package. Production PyPI binding and the matching environment were verified separately. Existing tests-domain deployment and publisher stay available until new-site and release verification succeed.

Review fixes isolate each PR's documentation concurrency from the main deployment queue, refresh the landing page to 0.6.2, and align documentation badge/link labels with the new URL. GitHub Pages settings were inspected: deployment from gh-pages, / (root), custom domain trace.agentrust-io.com. GitHub currently reports a TLS certificate provisioning error; HTTPS and the deployed site must be verified before the old tests site is retired.

Validation: the original commit passed package install/build, combined documentation build, Python tests, actionlint, CodeQL and fuzzing. On updated commit 402b204, actionlint has passed; remaining checks are running. No local Python build was run. The 0.6.2 release requires normal independent review and a conformance-v0.6.2 release matching the merged package version. DNS redirect and retirement of old services remain separate cutover steps. No TestPyPI publication is required.

@imran-siddique
imran-siddique requested review from a team, lywinged and rajnisht7 as code owners October 2, 2026 23:44
@imran-siddique

Copy link
Copy Markdown
Member Author

@lywinged - can you please review?

@lywinged

lywinged commented Oct 3, 2026

Copy link
Copy Markdown
Collaborator

I read the diff, both workflows at 7bdb7ca and the CI runs. The combined build, the CNAME handling and the version bump look right to me. The changelog counts match the vectors from #463 (27 files, 9 expected to pass TR-ANC-002 and 18 to fail), and the attribution matches the README there.

One thing I would change before merge. docs.yml now runs on pull_request, but its concurrency group is still the fixed docs-deploy. GitHub cancels a pending run in a group when a new one is queued, so a pull request touching conformance/**, docs/** or mkdocs.yml that arrives while a main deploy is waiting takes its place, and that deploy never runs. Pull requests also wait behind deploys and cancel each other's pending builds. Keeping pull requests out of the deploy group would fix it, for example:

concurrency:
  group: ${{ github.event_name == 'pull_request' && format('docs-pr-{0}', github.ref) || 'docs-deploy' }}
  cancel-in-progress: ${{ github.event_name == 'pull_request' }}

actionlint is clean on the workflow with that change.

Two smaller things, neither blocking:

  • conformance/index.md still says 0.6.1 at lines 19 and 107, which the new /conformance/ site will show after 0.6.2 is released.
  • In conformance/README.md the badge label and the documentation row's link text still read tests.agentrust-io.com, while the link now goes to trace.agentrust-io.com/conformance/.

I could not read the repository's Pages settings, so I am assuming the site is still served from the gh-pages branch that mkdocs gh-deploy wrote to, which is where ghp-import pushes.

Copy link
Copy Markdown
Member Author

@lywinged your three points are fixed in 402b204: PR docs builds have their own concurrency groups, the landing page says 0.6.2, and the README badge/link labels match the new documentation URL. I also verified Pages is configured for gh-pages at / (root). GitHub reports a certificate provisioning error, which remains a cutover check before retiring the old site.

The updated package build, Python tests, combined docs build, actionlint and CodeQL checks passed; fuzzing is still running. Please review the updated commit and approve when ready.

@lywinged lywinged left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, all three are in 402b204. Approving.

@imran-siddique
imran-siddique merged commit aa5c350 into main Oct 3, 2026
15 checks passed
@imran-siddique
imran-siddique deleted the conformance-final-cutover branch October 3, 2026 04:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants