Skip to content

docs: keep CI token captures private - #1129

Open
zlareb1 wants to merge 5 commits into
mainfrom
docs/headless-ci-private-token
Open

zlareb1 wants to merge 5 commits into
mainfrom
docs/headless-ci-private-token

Conversation

@zlareb1

@zlareb1 zlareb1 commented Nov 21, 2026 •

Copy link
Copy Markdown
Member

Changelog category

  • Documentation

Changelog entry

Not required.

Why

Shell redirection creates a token file using the current umask and retains the permissions of an existing file. The CI recipe needs to set private permissions before the token reaches that file.

Scope and risk

One guide creates the capture file with mode 600 before the existing token command. The recipe overwrites the capture file, as the existing redirection does. Capture runs only when file preparation succeeds. The local documentation checks minted no token and contacted no deployment.

Compatibility, rollout and rollback

  • Wire and defaults: none.
  • Operator steps: the documented CI recipe uses install to prepare its token file.
  • Rollback: removes that preparation step. No server data or generated files change.

Tests

  • Single-page formatting, source and body prose checks, and diff checks: passed.
  • Full hosted CI: all 54 checks are terminal: 52 passed and the documentation deployment and indexing checks were skipped on the pull request. All 43 core CI jobs passed, including every unit shard and both Postgres versions. Earlier failed runs remain recorded.
  • This composition includes the merged SCIP fixture correction and analysis-isolation setup publication checks. No Postgres cause or repair is claimed.
  • An earlier translation-check worker exited with signal 11; its cause remains unknown. No full suite ran locally.
  • Token minting and the complete CI authentication flow: not run; the change sets capture-file permissions and preserves the token command.

AI assistance in the code

  • AI-generated: Codex wrote the documentation change. The file-permission behavior, command ordering and diff scope were reviewed.

  • I can explain every line of this diff and how it interacts with the rest of Loom.

Checklist

  • Full formatting, lint, type and unit gates pass in hosted CI.
  • No generated file, schema, SDK, plugin or runtime behavior changes.
  • Documentation describes the recipe and its operator step.
  • Public wording contains no private deployment details.
  • Commits are signed off.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
@vercel

vercel Bot commented Nov 21, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
loom-docs Ready Ready Preview Nov 22, 2026 1:18pm UTC

Request Review

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>

This branch has not been deployed

No deployments
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