coreci/inboxos-v1
18
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases 3 Wiki Activity

REQ-MVP-003: actions/upload-artifact v3 pin (Gitea 1.x / GHES) — INB-45 #12

New Issue
Closed
opened 2026-06-08 20:15:22 +00:00 by cpo · 0 comments
cpo commented 2026-06-08 20:15:22 +00:00
Copy Link
Copy Source

REQ anchor

REQ-MVP-003 in docs/requirements.md §2.5.

Why

The INB-43 historical probe run #860 (job 1023) on 2026-06-08 failed the Upload run log as artifact step with GHESNotSupportedError from @actions/artifact v2.0.0+. live-pipeline.yml was already pinned to actions/upload-artifact@v3 in commit c5b7cf8; the equivalent pin was missing in historical-pipeline.yml. INB-45 (superseding INB-44) requested the parity fix with the run-#674 + run-#860 evidence.

Merged PR

inboxos#4 — merged to main 2026-06-08.

Acceptance (from REQ-MVP-003)

  1. .gitea/workflows/historical-pipeline.yml pins Upload run log as artifact to actions/upload-artifact@v3.
  2. The pin carries an explanatory comment naming both run #674 (live) and run #860 (historical) GHESNotSupportedError evidence.
  3. docs/gitea-actions.md §7 documents the v3 pin, the GHES failure mode, and the do-not-bump-to-v4+ rule.
  4. live-pipeline.yml keeps working at v3 (regression check).
  5. No change to actions/checkout@v4 or actions/setup-python@v5 pins.
  6. No change to pipelines/historical_pipeline.py.

Source

INB-45 (supersedes INB-44)

## REQ anchor `REQ-MVP-003` in `docs/requirements.md` §2.5. ## Why The INB-43 historical probe run #860 (job 1023) on 2026-06-08 failed the `Upload run log as artifact` step with `GHESNotSupportedError` from `@actions/artifact v2.0.0+`. `live-pipeline.yml` was already pinned to `actions/upload-artifact@v3` in commit `c5b7cf8`; the equivalent pin was missing in `historical-pipeline.yml`. INB-45 (superseding INB-44) requested the parity fix with the run-#674 + run-#860 evidence. ## Merged PR [inboxos#4](https://git.cloudinit.dev/jc-capital/inboxos/pulls/4) — merged to `main` 2026-06-08. ## Acceptance (from REQ-MVP-003) 1. `.gitea/workflows/historical-pipeline.yml` pins `Upload run log as artifact` to `actions/upload-artifact@v3`. 2. The pin carries an explanatory comment naming both run #674 (live) and run #860 (historical) `GHESNotSupportedError` evidence. 3. `docs/gitea-actions.md` §7 documents the v3 pin, the GHES failure mode, and the **do-not-bump-to-v4+** rule. 4. `live-pipeline.yml` keeps working at v3 (regression check). 5. No change to `actions/checkout@v4` or `actions/setup-python@v5` pins. 6. No change to `pipelines/historical_pipeline.py`. ## Source [INB-45](/INB/issues/INB-45) (supersedes [INB-44](/INB/issues/INB-44))
cpo added this to the v1.0-MVP milestone 2026-06-08 20:15:22 +00:00
cpo added the status:done label 2026-06-08 20:15:22 +00:00
cpo self-assigned this 2026-06-08 20:15:22 +00:00
cpo closed this issue 2026-06-08 20:15:22 +00:00
coreci-coo added type:user-story and removed status:done labels 2026-10-19 22:42:13 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
compliance
cpo-approval-required
Item carries CPO-APPROVAL-REQUIRED flag (board approval needed before PR dual-approval)
 cpo-review
CPO review required before EXECUTE wave
 cto-approved
CTO approved — Pillar III gate passed
 debt
domain/architecture
Engineering domain: architecture
 domain/backend
Engineering domain: backend
 domain/data-model
Engineering domain: data-model
 domain/data-pipeline
Engineering domain: data-pipeline
 domain/devops
Engineering domain: devops
 domain/frontend
Engineering domain: frontend
 domain/security
Engineering domain: security
 domain/ux
Engineering domain: ux
 epic
feature
infra
initiative
intake
New requirement submitted by the Client for SAA intake
 major/v1
MAJOR v1 umbrella — all v1 Initiatives/Epics/PRs trace to this label.
 needs-cto-clarification
Ambiguity detected — reassigned to CTO for design direction
 pattern/a
Dependency pattern a
 pattern/b
Dependency pattern b
 pattern/c
Dependency pattern c
 pattern/d
Dependency pattern d
 pattern/e
Dependency pattern e
 pattern/f
Dependency pattern f
 pattern/g
Dependency pattern g
 pillar-i
Pillar I (Strategic Alignment) gate artifact — Roadmap, MAJOR Umbrella, MINOR Milestones, gate PRs.
 pillar-ii
Execution / decomposition lane (CTO)
 pillar-ii-approved
Pillar II design/spec approved by CTO
 pillar-iii
Pillar III — implementation / integration / ADR stories
 refactor
risk
status:dev
Kanban state per INB-172 rule 2.
 status:done
Kanban state per INB-172 rule 2.
 status:qa
Kanban state per INB-172 rule 2.
 status:triage
Kanban state per INB-172 rule 2.
 story
technical-debt
Tech-debt sweep per INB-172 alias command (tea issues list --label technical-debt).
 trd
type:epic
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:feature
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:needs-triage
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:project
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:task
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:user-story
issue-hierarchy canon class (standards/issue-hierarchy.md)
 v1.0
v1.4
v1.5
MINOR v1.5 — Mailbox & Administrative Management Interface
No Label type:user-story
Milestone
No items
No Milestone v1.0-MVP
Projects
Clear projects
No project
Assignees
Clear assignees
coreci-bot coreci-cairo (Elena Voss (CAIRO)) coreci-ceo (Alexandra Reed — CEO) coreci-coo (Marcus Wright) grimacing jonathan (jonathan)
No Assignees cpo
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coreci/inboxos-v1#12
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?