<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://sengi.run/changelog/feed.xml</id>
  <title>Sengi changelog</title>
  <link rel="self" href="https://sengi.run/changelog/feed.xml" type="application/atom+xml" />
  <link rel="alternate" href="https://sengi.run/changelog" />
  <author>
    <name>Sengi</name>
  </author>
  <updated>2026-11-17T00:00:00Z</updated>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-terms-and-privacy-page-in-the-account-area</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-terms-and-privacy-page-in-the-account-area" />
    <title>Terms and Privacy page in the account area</title>
    <summary>Signed-in users now have a Terms and Privacy page under Account and security, also reachable from the account dropdown. It links to the terms of service, the privacy policy and a way to request source code.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-spending-cap-stop-new-jobs-at-a-monthly-amount</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-spending-cap-stop-new-jobs-at-a-monthly-amount" />
    <title>Spending cap: stop new jobs at a monthly amount</title>
    <summary>On the Billing page you can now set a monthly spending cap: a usage alert with the option to stop new jobs when the amount is reached.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-renamed-and-moved-repositories-no-longer-stall-jobs</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-renamed-and-moved-repositories-no-longer-stall-jobs" />
    <title>Renamed and moved repositories no longer stall jobs</title>
    <summary>A repository that is renamed, recreated under its old name, or moved to another GitHub installation in the same Sengi project is now matched correctly. A repository that still conflicts is set aside on its own and the rest of the installation keeps running.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-refreshed-alternatives-cheapest-runners-and-pricing-guides</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-refreshed-alternatives-cheapest-runners-and-pricing-guides" />
    <title>Refreshed alternatives, cheapest-runners and pricing guides</title>
    <summary>Four guide pages were reworked to answer the question first: two alternatives pages, the cheapest hosted runners page, and the runner pricing page.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-public-benchmarks-page-sengi-runners-and-githubs-runner</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-public-benchmarks-page-sengi-runners-and-githubs-runner" />
    <title>Public benchmarks page: Sengi runners and GitHub's runner</title>
    <summary>sengi.run now has a public benchmarks page that times open-source projects' CI jobs on GitHub's runner and on Sengi Basic and Premium, with the data as JSON and CSV.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-one-benchmark-page-for-each-project</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-one-benchmark-page-for-each-project" />
    <title>One benchmark page for each project</title>
    <summary>Each of the 12 benchmarked projects now has its own page under /benchmarks, with the same figures as the main benchmarks page.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-free-jobs-on-accounts-without-a-card-stop-after-2-hours</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-free-jobs-on-accounts-without-a-card-stop-after-2-hours" />
    <title>Free jobs on accounts without a card stop after 2 hours</title>
    <summary>A job that runs on free minutes in a project with no payment method on file is stopped once it has run for 2 hours. The project gets an email, sent at most once a day.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-fix-for-queued-jobs-left-without-a-runner</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-fix-for-queued-jobs-left-without-a-runner" />
    <title>Fix for queued jobs left without a runner</title>
    <summary>Each queued job now gets its own runner. Before, a job could be left without one when GitHub reported it as queued after another job had already started on a runner made for it, or when GitHub sent several queued notices for one job.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-fix-for-jobs-stuck-as-queued-after-the-nov-1-clock-change</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-fix-for-jobs-stuck-as-queued-after-the-nov-1-clock-change" />
    <title>Fix for jobs stuck as queued after the Nov 1 clock change</title>
    <summary>Jobs that ran on Sengi runners during the daylight saving clock change on November 1, 2026 could stay marked as queued, with their minutes not recorded. Sengi now accepts the one-hour timestamp difference GitHub sent in that hour.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-fix-for-jobs-stuck-after-a-deleted-repos-name-is-reused</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-fix-for-jobs-stuck-after-a-deleted-repos-name-is-reused" />
    <title>Fix for jobs stuck after a deleted repo's name is reused</title>
    <summary>Deleting a repository and creating a new one with the same name could stop Sengi runners for every repository on that GitHub installation. Sengi now releases the old name so the new repository is set up and its jobs run.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-fix-for-jobs-left-in-progress-after-lost-github-events</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-fix-for-jobs-left-in-progress-after-lost-github-events" />
    <title>Fix for jobs left in progress after lost GitHub events</title>
    <summary>Some jobs on Sengi runners could stay marked in progress, and go unbilled, when GitHub's job event arrived out of step or was lost during a network interruption. Both cases are now handled.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-email-when-your-free-minutes-for-the-month-run-out</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-email-when-your-free-minutes-for-the-month-run-out" />
    <title>Email when your free minutes for the month run out</title>
    <summary>Accounts now get one email a month when they use up their 3,000 free minutes. The email says whether new jobs are paused until the next month or keep running and are billed to a card on file.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-customers-outside-the-us-can-add-a-payment-method</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-customers-outside-the-us-can-add-a-payment-method" />
    <title>Customers outside the US can add a payment method</title>
    <summary>Customers in supported countries outside the US can now add a payment method on the Billing page and run paid jobs. Billing starts as soon as the payment setup succeeds, and countries not on the supported list keep using free minutes.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-cache-keeps-recently-used-entries-links-last-one-hour</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-cache-keeps-recently-used-entries-links-last-one-hour" />
    <title>Cache keeps recently used entries; links last one hour</title>
    <summary>When a repository is over its cache storage limit, Sengi now removes the least recently used entries first. Cache upload and download links now last one hour instead of 15 minutes.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-banner-when-github-actions-or-webhooks-is-having-trouble</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-banner-when-github-actions-or-webhooks-is-having-trouble" />
    <title>Banner when GitHub Actions or Webhooks is having trouble</title>
    <summary>Signed-in Sengi pages now show a banner while GitHub's status page lists Actions or Webhooks as degraded or down, with a link to that status page.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-api-endpoint-to-check-a-projects-github-connection</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-api-endpoint-to-check-a-projects-github-connection" />
    <title>API endpoint to check a project's GitHub connection</title>
    <summary>The API has a new endpoint that shows whether a repository is connected to Sengi and why its jobs would be refused, so a coding agent can check without asking a person. The Sengi agent prompt now uses it.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-account-owners-get-an-email-when-an-account-is-suspended</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-account-owners-get-an-email-when-an-account-is-suspended" />
    <title>Account owners get an email when an account is suspended</title>
    <summary>When an account is suspended, its owner is now emailed the reason and what the suspension means. A suspended account cannot start new jobs, and nothing is deleted.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-17-a-card-on-file-raises-the-runner-vcpu-limit</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-17-a-card-on-file-raises-the-runner-vcpu-limit" />
    <title>A card on file raises the runner vCPU limit</title>
    <summary>New projects without a payment method can run up to 12 vCPUs of runners at the same time. Adding a card, or having an active paid subscription, raises that limit, and free projects that wait on the limit get one email suggesting a card.</summary>
    <published>2026-11-17T00:00:00Z</published>
    <updated>2026-11-17T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-16-public-status-page-for-sengi-run</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-16-public-status-page-for-sengi-run" />
    <title>Public status page for sengi.run</title>
    <summary>sengi.run now links to a public status page from the home page footer, and /status goes to it.</summary>
    <published>2026-11-16T00:00:00Z</published>
    <updated>2026-11-16T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-16-new-pages-comparing-hosted-runner-services</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-16-new-pages-comparing-hosted-runner-services" />
    <title>New pages comparing hosted runner services</title>
    <summary>Three head-to-head pages compare pairs of other hosted GitHub Actions runner services on prices and plans, and a new alternatives page covers one more runner service.</summary>
    <published>2026-11-16T00:00:00Z</published>
    <updated>2026-11-16T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-13-the-sengi-label-in-runs-on-can-come-from-an-expression</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-13-the-sengi-label-in-runs-on-can-come-from-an-expression" />
    <title>The Sengi label in runs-on can come from an expression</title>
    <summary>The guide and docs now say the Sengi label in runs-on can come from a GitHub Actions expression or variable, so one variable can choose the runner for many workflows. The service terms say the same.</summary>
    <published>2026-11-13T00:00:00Z</published>
    <updated>2026-11-13T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-13-terms-list-the-basic-and-premium-runner-labels</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-13-terms-list-the-basic-and-premium-runner-labels" />
    <title>Terms list the Basic and Premium runner labels</title>
    <summary>Section 1.2 of the service terms now lists the six Basic and Premium runner labels instead of only the older sengi-standard labels.</summary>
    <published>2026-11-13T00:00:00Z</published>
    <updated>2026-11-13T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-13-new-guide-on-switching-github-actions-runners</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-13-new-guide-on-switching-github-actions-runners" />
    <title>New guide on switching GitHub Actions runners</title>
    <summary>A new article, "Done Paying GitHub So Much for Actions? Switch Your Runners to Sengi", answers what to switch to when GitHub Actions costs too much, and the Claude Code bill article is refreshed.</summary>
    <published>2026-11-13T00:00:00Z</published>
    <updated>2026-11-13T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-13-new-blog-index-page-at-blog</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-13-new-blog-index-page-at-blog" />
    <title>New blog index page at /blog</title>
    <summary>sengi.run now has a /blog page that lists every article, newest first, with its date and a one-line summary, and a Blog link in the site navigation and footers.</summary>
    <published>2026-11-13T00:00:00Z</published>
    <updated>2026-11-13T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/changelog/2026-11-13-guide-a-checklist-for-choosing-low-cost-runners</id>
    <link rel="alternate" href="https://sengi.run/changelog/2026-11-13-guide-a-checklist-for-choosing-low-cost-runners" />
    <title>Guide: a checklist for choosing low-cost runners</title>
    <summary>A new article lists what to check when comparing low-cost GitHub Actions runners: price per minute, measured build performance, workflow fit and isolation.</summary>
    <published>2026-11-13T00:00:00Z</published>
    <updated>2026-11-13T00:00:00Z</updated>
  </entry>
</feed>
