Skip to content

Conversation

@mnmkng
Copy link
Member

@mnmkng mnmkng commented Jan 18, 2026

See https://apify.slack.com/archives/CQ96RHG2U/p1768757339018769

  • Added section explaining Docker image tag naming convention (e.g., 22-1.52.0 for Node.js 22 with Playwright 1.52.0)
  • Added direct links to Docker Hub tags pages for discovering available versions
  • Added guidance on pinning Playwright/Puppeteer versions for reproducible builds
  • Clarified that using * as version is a legacy approach, with pinning now preferred

Note

Updates docker.md with guidance to improve reproducibility and clarity around base images.

  • Image tag naming convention for Node.js and Python images, including {runtime-version}-{library-version} tags with examples
  • Finding available tags via Docker Hub links and a curl/jq snippet
  • Version pinning recommendations: pin Node/Python and Playwright/Puppeteer/Selenium versions; Dockerfile and package.json examples provided
  • Warning on mismatched versions triggering extra downloads and incompatibilities; notes that using * is legacy and pinning is preferred

Written by Cursor Bugbot for commit 11df06f. Configure here.

…dance

- Added section explaining Docker image tag naming convention (e.g., `22-1.52.0` for Node.js 22 with Playwright 1.52.0)
- Added direct links to Docker Hub tags pages for discovering available versions
- Added guidance on pinning Playwright/Puppeteer versions for reproducible builds
- Clarified that using `*` as version is a legacy approach, with pinning now preferred
@mnmkng mnmkng requested a review from TC-MO as a code owner January 18, 2026 17:40
@apify-service-account
Copy link

Preview for this PR was built for commit 11df06f and is ready at https://pr-2185.preview.docs.apify.com!

Copy link
Contributor

@TC-MO TC-MO left a comment

Choose a reason for hiding this comment

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

Few thoughts and changes requested

Thanks for the fixes!

Co-authored-by: Michał Olender <92638966+TC-MO@users.noreply.github.com>
mnmkng added a commit that referenced this pull request Jan 21, 2026
Add .claude/rules/writing-style.md with documentation writing guidelines
for AI assistants. Based on Apify style guide and TC-MO's technical
writer feedback from PR #2185.

Includes:
- Core principles (simple, factual, technical)
- Formatting rules (headings, bold, lists)
- Grammar guidelines (articles, Oxford comma)
- Terminology standards (Actor capitalization, word choice)
- Common mistakes to avoid

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@apify-service-account
Copy link

Preview for this PR was built for commit 1020ed2b and is ready at https://pr-2185.preview.docs.apify.com!

Copy link
Contributor

@TC-MO TC-MO left a comment

Choose a reason for hiding this comment

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

LGTM

@mnmkng mnmkng merged commit 25837b9 into master Jan 21, 2026
15 checks passed
@mnmkng mnmkng deleted the claude/slack-improve-state-persistence-docs-uuU84 branch January 21, 2026 20:46
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.

6 participants