feat: Submit Pipeline Tags on Runs

[camielvs]

Description

Pipeline Tags will now be submitted alongside a Run as run annotations and will be shown on the Run List and in a run's context panel, similar to the pipeline editor (but Run Tags cannot be edited or removed).

(I also did a little cleanup on RunSection while in the file)

Related Issue and Pull requests

Closes https://github.com/Shopify/oasis-frontend/issues/472

Type of Change

• New feature

Checklist

• I have tested this does not break current pipelines / runs functionality
• I have tested the changes on staging

Screenshots (if applicable)

Test Instructions

• Submit a run for a pipeline that has tags

Confirm that:

• The tags show on the run list on the homepage for that run
• The tags show on the run's context panel

Additional Comments

The tags in the run's context panel are sourced from the pipeline component spec, not the run annotations (as might be expected). Currently the content of the two is the same at time of submission. Sourcing the tags from the run annotations requires and additional API call. hence, I chose (for now) to source them fromt he component spec. If there should be reason in the future for the two sources to diverge then we can switch it over to sourcing from the run annotations API.

[camielvs]

• chore: Add onEnter and onEscape to Input Component #1850
• feat: Submit Pipeline Tags on Runs #1849 👈 (View in Graphite)
• feat: Pipeline Tags #1848
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

🎩 To tophat this PR:

You can add the following URL parameter to your browser to tophat this PR:

`?tophat_location=02-23-feat_submit_pipeline_tags_on_runs/5288e9e`

---

[maxy-shpfy]

Is it expected, that I cant see tags in a Runs list?

Screen Recording 2026-03-04 at 8.16.00 PM.mov (uploaded via Graphite)

[maxy-shpfy]

^
Seems that we cant push ANY values to annotations:

{
    "error_code": 500,
    "error_message": "(pymysql.err.DataError) (1406, \"Data too long for column 'value' at row 1\")\n[SQL: INSERT INTO pipeline_run_annotation (pipeline_run_id, `key`, value) VALUES (%(pipeline_run_id)s, %(key)s, %(value)s)]\n[parameters: {'pipeline_run_id': '019cbc36f07ca9b730a3', 'key': 'tags', 'value': 'Multi-Node,A,B,LongnameLongname-1,LongnameLongname-2,LongnameLongname-3,LongnameLongname-4,LongnameLongname-5,LongnameLongname-6,LongnameLongname-7,L ... (207 characters truncated) ... ngname-18,LongnameLongname-19,LongnameLongname-20,LongnameLongname-21,LongnameLongname-22,LongnameLongname-23,LongnameLongname-24,LongnameLongname-25'}]\n(Background on this error at: https://sqlalche.me/e/20/9h9h)"
}

[maxy-shpfy]

We should not send request if tags are empty.

[camielvs]

Tag limit of 10 should fix the issue.

I also changed it so we do not submit tags if there are none.

[camielvs]

Merge activity

• Mar 5, 10:46 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Mar 5, 11:08 PM UTC: Graphite rebased this pull request as part of a merge.
• Mar 5, 11:21 PM UTC: Graphite couldn't merge this PR because it was not satisfying all requirements (Failed CI: 'Linting').
• Mar 5, 11:25 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Mar 5, 11:26 PM UTC: Graphite rebased this pull request as part of a merge.
• Mar 5, 11:31 PM UTC: @camielvs merged this pull request with Graphite.