Skip to content

Conversation

@pofl
Copy link

@pofl pofl commented Dec 8, 2025

Type of Change

  • Bugfix
  • Enhancement / new feature
  • Refactoring
  • Documentation

Description

These runners have one vCPU and 5 GBs RAM. When using these runners, your actions workflows execute inside of a container rather than a dedicated VM instance, enabling cost-effective, performant execution of automation tasks across GitHub. Each container provides hypervisor level 2 isolation, and the container is automatically decomissioned when a job is completed. Jobs that use this runner type are limited to 15 minutes of execution time. Jobs exceeding this limit will be terminated and fail.

If you think any actions should not run in this slim version please flag it. GitOps comes to mind because building Dockerfiles might be heavy.

Checklist

  • Add relevant labels (for example type of change or patch/minor/major)
  • Make sure not to introduce some mistakes
  • Update documentation
  • Review the Contributing Guideline and sign CLA
  • Reference relevant issue(s) and close them after merging

@pofl pofl requested review from a team as code owners December 8, 2025 10:00
update_release_draft:
name: update release draft
runs-on: ubuntu-24.04
runs-on: ubuntu-slim
Copy link
Member

Choose a reason for hiding this comment

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

I wouldn't use the slim thing here since this is on the release production path and therefore time to market will be decreased when change this.

Copy link
Author

Choose a reason for hiding this comment

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

To my intuition this shouldn't become slower. The release-drafter action is a nodejs action which means it runs single-threaded anyway. So the switch to 1vCPU shouldn't matter 🤔 ?

If ubuntu-slim runs in a container instead of a VM we might even experience faster cold starts 🤔

This line of thinking applies to all actions you commented on.
Wdyt?

Copy link
Member

Choose a reason for hiding this comment

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

This sounds reasonable. 👍
One thought: NodeJS allows spawning child processes which are then decoupled from the parent event loop and therefore the assumption "it's nodejs it will def. only use one CPU" is not correct.

@pofl pofl changed the title Switch all workflows to ubuntu-slim Switch all workflows to ubuntu-slim except GitOps Dec 8, 2025
@sbmars sbmars self-requested a review December 9, 2025 03:22
Copy link
Member

@stefanmeschke stefanmeschke left a comment

Choose a reason for hiding this comment

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

We need to monitor this change ofc. 😊

From my point of view there are labels missing on this PR in order to mark this PR as major change etc.

@flaxel flaxel added enhancement New feature or request major Pull requests with breakable changes labels Jan 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request major Pull requests with breakable changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants