Skip to content

Comments

Updated CI runner to 26.2.0#2307

Merged
AlexSkrypnyk merged 1 commit intomainfrom
feature/update-ci-runner-26.2.0
Feb 19, 2026
Merged

Updated CI runner to 26.2.0#2307
AlexSkrypnyk merged 1 commit intomainfrom
feature/update-ci-runner-26.2.0

Conversation

@AlexSkrypnyk
Copy link
Member

@AlexSkrypnyk AlexSkrypnyk commented Feb 19, 2026

Closes #

Summary by CodeRabbit

  • Chores
    • Updated CI/CD pipeline runner images to a newer canary release to enable more frequent infrastructure updates across automated testing and deployment workflows.

@coderabbitai
Copy link

coderabbitai bot commented Feb 19, 2026

No actionable comments were generated in the recent review. 🎉


Walkthrough

Updated CI workflows to bump the drevops/ci-runner container image from 26.1.0@sha256:1fd1a2bc... to 26.2.0@sha256:fe1561c2... in CircleCI and GitHub Actions files; no other logic, steps, or environment changes.

Changes

Cohort / File(s) Summary
CircleCI config
.circleci/config.yml
Bumped runner image from drevops/ci-runner:26.1.0@sha256:1fd1a2bc... to drevops/ci-runner:26.2.0@sha256:fe1561c2.... No other edits.
GitHub Actions — build/test/deploy
.github/workflows/build-test-deploy.yml
Updated three job runner image references to drevops/ci-runner:26.2.0@sha256:fe1561c2...; steps and control flow unchanged.
GitHub Actions — common tests
.github/workflows/vortex-test-common.yml
Updated two job runner image references to drevops/ci-runner:26.2.0@sha256:fe1561c2...; no logic changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested labels

AUTOMERGE

Poem

🐇 I hopped through YAML, nibbling tags so spry,

New runner crumbs now gleam — 26.2 in my eye.
No logic disturbed, just a soft little shove,
CI hums along like a burrowing love.
🥕✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Updated CI runner to 26.2.0' directly and specifically describes the main change: updating the CI runner container image from version 26.1.0 to 26.2.0 across multiple configuration files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/update-ci-runner-26.2.0

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In @.circleci/config.yml:
- Around line 40-45: The CircleCI job is using a floating image tag
"drevops/ci-runner:canary" which risks drift; change the image reference in the
config from "drevops/ci-runner:canary" to a pinned tag or digest (e.g.,
"drevops/ci-runner:<stable-version>" or "drevops/ci-runner@sha256:<digest>") and
update any related documentation that references "drevops/ci-runner" or "canary"
to the chosen pinned value; verify the change by searching for occurrences of
"drevops/ci-runner", "canary", or the chosen version/digest and ensure all CI
configs and docs are consistent.

In @.github/workflows/build-test-deploy.yml:
- Around line 456-459: The workflow uses a floating image tag
"drevops/ci-runner:canary" in the container stanza; replace that with the same
pinned tag or digest used elsewhere (e.g., the exact
"drevops/ci-runner:<pinned-tag-or-digest>" value referenced in other CI
configs/docs) so the deploy job matches the stable image version; update the
image value in the container: image: entry to the canonical pinned tag/digest
and run the provided rg command to verify all CI docs and workflow files are
consistent.
- Around line 182-185: The workflow uses a floating image tag
"drevops/ci-runner:canary" in the container.image block; replace it with the
same pinned tag or digest used in other CI configs (e.g., the referenced
"26.2.0" tag or the exact image digest) so the build job matches other jobs and
avoids canary drift—update the string "drevops/ci-runner:canary" to the
canonical pinned value and ensure any docs/config references are consistent.

In @.github/workflows/vortex-test-common.yml:
- Around line 123-127: Replace the floating canary image reference used in the
workflow (the container image declaration "image: drevops/ci-runner:canary")
with a pinned tag or immutable digest (e.g., "drevops/ci-runner:26.2.0" or
"drevops/ci-runner@sha256:..."); update the workflow's container.image value
accordingly and ensure the verification/search examples in docs/ci.md and CI
configs (the ripgrep pattern referencing "drevops/ci-runner|26.2.0|canary") are
updated to reflect the chosen pinned tag or digest so tests and docs remain
consistent.
- Around line 24-28: The workflow uses a floating image tag
"drevops/ci-runner:canary" which risks drift; replace that image reference with
a pinned tag or digest (e.g., drevops/ci-runner:<explicit-version> or
drevops/ci-runner@sha256:<digest>) in the container.image field of the workflow,
update any documentation references (docs/ci.md and other CI configs) to match,
and run the provided verification search (rg for
"drevops/ci-runner|26.2.0|canary") to ensure no other CI files still reference
the floating tag.

@github-actions

This comment has been minimized.

@AlexSkrypnyk
Copy link
Member Author

Code Coverage Report:
  2026-02-19 06:14:15

 Summary:
  Classes:  0.00% (0/1)
  Methods:  0.00% (0/2)
  Lines:   94.65% (177/187)

@AlexSkrypnyk
Copy link
Member Author

Code Coverage Report:
  2026-02-19 06:14:51

 Summary:
  Classes:  0.00% (0/1)
  Methods:  0.00% (0/2)
  Lines:   94.65% (177/187)

@codecov
Copy link

codecov bot commented Feb 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.09%. Comparing base (2183229) to head (f363cf4).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2307      +/-   ##
==========================================
- Coverage   78.62%   78.09%   -0.53%     
==========================================
  Files         124      117       -7     
  Lines        6404     6245     -159     
  Branches       44        0      -44     
==========================================
- Hits         5035     4877     -158     
+ Misses       1369     1368       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@AlexSkrypnyk AlexSkrypnyk force-pushed the feature/update-ci-runner-26.2.0 branch from de5417f to f363cf4 Compare February 19, 2026 22:22
@github-actions
Copy link

Code Coverage Report:
  2026-02-19 22:29:08

 Summary:
  Classes:  0.00% (0/1)
  Methods:  0.00% (0/2)
  Lines:   94.65% (177/187)

@AlexSkrypnyk
Copy link
Member Author

Code Coverage Report:
  2026-02-19 22:30:01

 Summary:
  Classes:  0.00% (0/1)
  Methods:  0.00% (0/2)
  Lines:   94.65% (177/187)

@AlexSkrypnyk
Copy link
Member Author

Code Coverage Report:
  2026-02-19 22:33:46

 Summary:
  Classes:  0.00% (0/1)
  Methods:  0.00% (0/2)
  Lines:   94.65% (177/187)

@AlexSkrypnyk
Copy link
Member Author

Code Coverage Report:
  2026-02-19 22:33:49

 Summary:
  Classes:  0.00% (0/1)
  Methods:  0.00% (0/2)
  Lines:   94.65% (177/187)

@AlexSkrypnyk AlexSkrypnyk merged commit 7088bd2 into main Feb 19, 2026
28 checks passed
@AlexSkrypnyk AlexSkrypnyk deleted the feature/update-ci-runner-26.2.0 branch February 19, 2026 23:12
@github-project-automation github-project-automation bot moved this from BACKLOG to Release queue in Vortex Feb 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Release queue

Development

Successfully merging this pull request may close these issues.

1 participant