Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Expand builds-and-runs docs to clarify tag behavior across versions

Aperta
  • Qualcosa non va?
#2,520 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@TC-MO ci sta già lavorando.

Dal 26/5/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

documentation t-docs

Reported on Slack: tag behavior on Actor builds is documented in fragments, with no single place explaining the full picture. Users hit confusing edge cases:

  • Two builds across different versions can share the same tag name (e.g., both 0.0 and 0.1 tagged latest). When the Actor runs, it picks whichever was built last.
  • The auto-tagging dialog reinforces the impression that tags are version-specific, when in practice the effective build for a tag is whichever was built and tagged most recently.

Current docs only state that tags are exclusive across all builds and versions, and that they move when another build is tagged the same.

They do not explain:

  • That tags can be set on builds via the Console UI and via the API (not only at build time).
  • How build numbers are constructed from MAJOR.MINOR by appending .BUILD.
  • That multiple versions can in theory share the same tag, that each new build overrides the tag, and that this is not practical, so different tags should be used for different versions.

Proposed changes

Expand https://docs.apify.com/platform/actors/development/builds-and-runs/builds#tags to:

  1. Document that tags can be set on existing builds through the Console UI and via the API, not only during build creation.
  2. In the Versioning section, explain build number construction (MAJOR.MINOR.BUILD).
  3. Add an explicit note that multiple versions can technically share the same tag, that each build overrides the tag, and that this is not a recommended pattern. Recommend distinct tags per version.
Lingua principale
JavaScript
Stelle
82
Fork
240
Merge medio
4g 3h
PR unite (30g)
40

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apify/apify-docs

Tutte le issue di apify/apify-docs

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.