Skip to content

CI: Creating release tag should trigger stable pipeline - #572

Merged
Eduardo Villalpando Mello (edvilme) merged 2 commits into
mainfrom
ci-improve-release
Oct 7, 2026
Merged

Eduardo Villalpando Mello (edvilme) merged 2 commits into
mainfrom
ci-improve-release

Conversation

@edvilme

Copy link
Copy Markdown
Collaborator

Currently, creating a new release involves manually creating a branch and manually running a pipeline. Instead, the stable release pipeline could be automatically triggered via a GitHub release.

The pipeline would still require approvals for publishing, but it would reduce the number of manual steps to be executed.

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Test Coverage Report (Linux)

Result: ✅ Within regression budget

Metric PR Baseline Delta
Lines 85.589% 85.589% +0.000pp
Functions 88.400% 88.400% +0.000pp

Allowed numerical tolerance: 0.01 percentage points.

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Performance Report (macOS)

Result: ✅ Within regression budgets

Metric PR Baseline Delta Change Blocking budget Status
Server startup P50 99ms 132ms -33ms -25.0% >100ms and >50% ✅
Server startup P95 942ms 833ms +109ms +13.1% >750ms and >100% 🔺
Discovery duration P50 146ms 160ms -14ms -8.8% >100ms and >50% ✅
Discovery duration P95 243ms 247ms -4ms -1.6% >300ms and >100% ✅
Startup-to-first environment P50 136ms 153ms -17ms -11.1% >150ms and >50% ✅
Startup-to-first environment P95 171ms 174ms -3ms -1.7% >250ms and >100% ✅
Cold discovery duration P50 313ms 421ms -108ms -25.7% >250ms and >50% ✅
Refresh round-trip P50 147ms 161ms -14ms -8.7% >250ms and >50% ✅
Refresh round-trip P95 245ms 251ms -6ms -2.4% >300ms and >100% ✅
Request-to-first environment P50 43ms 41ms +2ms +4.9% >50ms and >50% 🔺
Request-to-first environment P95 75ms 55ms +20ms +36.4% >100ms and >100% 🔺
Cold refresh round-trip P50 314ms 421ms -107ms -25.4% >600ms and >50% ✅
Workload PR Baseline
Environments 10 10
Managers 1 1

A regression must exceed both the documented absolute and relative budget. Environment and manager inventories must match exactly within the same inventory schema.

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Test Coverage Report (Windows)

Result: ✅ Within regression budget

Metric PR Baseline Delta
Lines 83.130% 83.130% +0.000pp
Functions 85.791% 85.791% +0.000pp

Allowed numerical tolerance: 0.01 percentage points.

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Performance Report (Linux)

Result: ✅ Within regression budgets

Metric PR Baseline Delta Change Blocking budget Status
Server startup P50 1ms 1ms +0ms +0.0% >5ms and >100% ➖
Server startup P95 1ms 1ms +0ms +0.0% >50ms and >200% ➖
Discovery duration P50 52ms 49ms +3ms +6.1% >25ms and >30% 🔺
Discovery duration P95 55ms 51ms +4ms +7.8% >50ms and >50% 🔺
Startup-to-first environment P50 11ms 10ms +1ms +10.0% >20ms and >100% 🔺
Startup-to-first environment P95 13ms 12ms +1ms +8.3% >25ms and >100% 🔺
Cold discovery duration P50 116ms 108ms +8ms +7.4% >100ms and >50% 🔺
Refresh round-trip P50 52ms 49ms +3ms +6.1% >25ms and >30% 🔺
Refresh round-trip P95 55ms 51ms +4ms +7.8% >50ms and >50% 🔺
Request-to-first environment P50 10ms 9ms +1ms +11.1% >20ms and >100% 🔺
Request-to-first environment P95 12ms 11ms +1ms +9.1% >25ms and >100% 🔺
Cold refresh round-trip P50 116ms 108ms +8ms +7.4% >100ms and >50% 🔺
Workload PR Baseline
Environments 5 5
Managers 1 1

A regression must exceed both the documented absolute and relative budget. Environment and manager inventories must match exactly within the same inventory schema.

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Performance Report (Windows)

Result: ✅ Within regression budgets

Metric PR Baseline Delta Change Blocking budget Status
Server startup P50 10ms 9ms +1ms +11.1% >10ms and >50% 🔺
Server startup P95 14ms 13ms +1ms +7.7% >50ms and >100% 🔺
Discovery duration P50 174ms 162ms +12ms +7.4% >150ms and >50% 🔺
Discovery duration P95 190ms 171ms +19ms +11.1% >250ms and >100% 🔺
Startup-to-first environment P50 29ms 22ms +7ms +31.8% >25ms and >50% 🔺
Startup-to-first environment P95 42ms 29ms +13ms +44.8% >100ms and >100% 🔺
Cold discovery duration P50 169ms 158ms +11ms +7.0% >150ms and >50% 🔺
Refresh round-trip P50 174ms 162ms +12ms +7.4% >150ms and >50% 🔺
Refresh round-trip P95 190ms 171ms +19ms +11.1% >250ms and >100% 🔺
Request-to-first environment P50 18ms 12ms +6ms +50.0% >25ms and >50% 🔺
Request-to-first environment P95 31ms 19ms +12ms +63.2% >100ms and >100% 🔺
Cold refresh round-trip P50 170ms 159ms +11ms +6.9% >150ms and >50% 🔺
Workload PR Baseline
Environments 8 8
Managers 1 1

A regression must exceed both the documented absolute and relative budget. Environment and manager inventories must match exactly within the same inventory schema.

This comment was marked as resolved.

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot review overview

🟢 Approval recommended

The trigger, validation, and documentation consistently implement the intended release-tag workflow.

Review effort: Balanced
Findings: None

Resolved since last review (1)

@edvilme
Eduardo Villalpando Mello (edvilme) merged commit fd72ff3 into main Oct 7, 2026
40 of 41 checks passed
@edvilme
Eduardo Villalpando Mello (edvilme) deleted the ci-improve-release branch October 7, 2026 19:08
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.

4 participants