Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean GitHub Actions has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 4 scoped observations for GitHub Actions. The baseline covers GitHub-hosted job execution time, Self-hosted job execution time, Artifact storage, Default artifact and log retention. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| GitHub-hosted job execution timeA job is terminated and fails when it reaches the limit. | 6 hours | All GitHub-hosted runners | GitHubAug 22, 2026 |
| Self-hosted job execution timeDistinct from the total workflow run time limit. | 5 days | Self-hosted runners | GitHubAug 22, 2026 |
| Artifact storagePlan-level included artifact storage shown in the Actions limits table. | 500 MB | GitHub Free / Free for organizations | GitHubAug 22, 2026 |
| Default artifact and log retentionPublic repositories can configure 1–90 days; private repositories can configure 1–400 days, subject to organization or enterprise limits. | 90 days | Repository setting | GitHubAug 22, 2026 |
Tracked constraints and impact
Job duration, workflow, concurrency, artifact, and cache limits. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
GitHub Actions job duration
Current GitHub-hosted and self-hosted job execution ceilings, workflow-run scope, and timeout diagnostics.
GitHub Actions artifacts
Current artifact storage by plan, default retention, repository controls, and the difference between artifacts and dependency caches.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current GitHub Actions baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Execution, concurrency, and storage limits
Artifact and log retention period