Skip to content

Keep docs builder and publisher pins synchronized - #10

Merged
tony merged 2 commits into
masterfrom
docs-publisher-maintenance
Sep 30, 2026
Merged

tony merged 2 commits into
masterfrom
docs-publisher-maintenance

Conversation

@tony

@tony tony commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

The docs checkout and reusable publisher must use the same reviewed commit. Renovate now discovers both pins and groups their updates into one pull request. GitHub Actions references retain full SHA pins, and automatic merging is disabled. Contributor guidance explains the separate IAM approval required before a new publisher revision can publish.

The included pin update uses the current reviewed docs main revision. The publisher workflow and provenance validator match the previously approved bytes; the imported port catalog changes cover browser links and descriptions. Its IAM approval is committed in tony/tf-config.

Verification:

  • Renovate 44.115.10 validates the configuration, resolves both dependencies through GitHub, and groups them into renovate/docs-publisher. Its replacement engine generated the exact two-line pin update.
  • The existing workflow test fails when only the checkout pin changes. The matching pair passes.
  • Ruby mid and outer checks pass in 8.01 and 36.02 seconds; the final pin update passes outer in 35.42 seconds.

Scheduled maintenance still requires Renovate to be enabled for this repository. The local updater checks do not establish that a hosted bot opened a PR or that a recurring run succeeded. Hosted docs build and preview publication must pass before merge.

Hosted validation: the docs build and preview publication passed in run 36674893903. The compatibility run passed all 36 cells after retrying one unchanged macOS terminal-draw test that missed its 0.5-second deadline on the first attempt.

why: The docs checkout and reusable publisher must advance together.
Bare commit pins are not enough for Renovate to discover branch updates.

what:
- Enable GitHub Actions updates and exact digest pinning
- Extract the custom docs checkout ref and group it with the publisher
- Keep automatic merges disabled and document the IAM review step

Verification: Renovate 44.115.10 validates the config and resolves both
pins into one update. Its replacement engine changes both references.
The existing workflow test rejects a mismatched pair. Mid and outer
checks pass in 8.01 and 36.02 seconds. Scheduled execution still needs
Renovate enabled for this repository.
why: The docs builder and publisher need the current reviewed source
revision while retaining exact commit pins.

what:
- Apply the paired update produced by Renovate 44.115.10
- Use bc037e77a78977a32de7a18890dcaed2188826e1 for both references
- Preserve the main branch annotations for later digest updates

The Renovate CLI resolved both dependencies into renovate/docs-publisher;
its replacement engine produced this exact two-line update. The local
outer gate passes in 35.42 seconds. Hosted documentation validation and
publication remain required before merge.
@tony
tony deployed to docs-preview September 30, 2026 05:49 — with GitHub Actions Active
@tony
tony merged commit cf8cc25 into master Sep 30, 2026
77 of 79 checks passed
@tony
tony deployed to docs-preview-cleanup September 30, 2026 06:06 — with GitHub Actions Active
tony added a commit that referenced this pull request Sep 30, 2026
what:
- Group docs builder and publisher updates through Renovate
- Refresh both pins to the reviewed docs revision
- Keep automatic merges disabled and document IAM approval

why:
Paired updates keep rendered documentation and publication on the same
reviewed revision. The docs build, preview publication, and compatibility
matrix validate the coordinated update.

This branch was successfully deployed

2 active deployments
docs-preview-cleanup — 6cb7e564 Deployed Sep 30, 2026 by tony via cleanup #8
docs-preview — 6cb7e564 Deployed Sep 30, 2026 by tony via publish (pr-10, pr, false, docs-preview, true) / publish #21
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.

1 participant