5 PM Technology News Recap: OpenAI Decisions, GitHub Secrets, Actions Networks, Google’s Grid, and BioWare (October 22, 2026)

OpenAI makes its Decisions API generally available, GitHub expands secret monitoring and Actions endpoints, Google backs a 1-gigawatt virtual power plant, and BioWare closes.

Reader ratingRate this article

Loading reader rating…

Privacy-conscious voting uses a signed random browser identifier and a short-lived network hash; the rating tables contain no raw IP-address column.

Thursday’s 5 PM technology recap connects faster software decisions with the controls—and consequences—around them. OpenAI has moved its Decisions API to general availability; GitHub added two operational updates for security and Actions networks; Google and Voltus announced a much larger virtual power plant; and a landmark game studio is closing.

Reporting cutoff: October 22, 2026, 5:04 p.m. EDT (2026-10-22T21:04:26Z). All five selected developments were published after the prior 5 PM cutoff. Product performance, eligibility, capacity, and implementation claims remain attributed to their publishers; the BioWare closure is reported by The Associated Press and its syndication partner.[1][2][3][4][5][6]

Listen to the broadcast-ready recap

This KittenTTS Bella narration was synthesized locally from the same checked facts as the article.

1. OpenAI’s Decisions API reaches general availability

OpenAI’s October 22 release says the Decisions API is now generally available. Its documentation says the endpoint evaluates text, images, and JSON and returns typed predicate, choice, or score answers; OpenAI describes it as about 10 times faster than the Responses API for this narrow work.[1][2]

The API currently supports only gpt-6-luna. OpenAI lists up to 400 questions per request, prompt caching, conversation-history input, usage reporting, Private Link, and native GPT-Live integration among the additions since beta.[2]

How we know—and what remains unknown: these are OpenAI’s product and benchmark claims. “10 times faster” is not an independent workload benchmark, and a typed answer remains a model output rather than a guaranteed correct business decision.

Practical guidance: use a narrow decision endpoint for low-authority classification or routing first; keep hard authorization, spending, deletion, and safety gates in deterministic application logic.

Good: typed, constrained outputs can simplify high-volume routing and prioritization.
Caution: lower latency can multiply a bad rubric or biased policy just as quickly as a good one.

2. GitHub extends public-secret monitoring to data-residency customers

GitHub says public monitoring is now in public preview for GitHub Enterprise Cloud with data residency. The feature watches public commits on github.com and attributes exposed credentials to an enterprise in real time.[3]

For data-residency environments, GitHub says attribution uses verified-domain matching rather than sharing enterprise membership rosters across the isolation boundary. Alerts are encrypted and delivered to the enterprise dashboard within its designated geography.[3]

Scope matters: this is a public preview, requires GitHub Advanced Security or GitHub Secret Protection, and is included with one of those active licenses. Domain matching can identify relevant public commits, but it does not prevent the original secret from being exposed.

Practical guidance: verify enterprise domains, define who receives alerts, and rehearse revocation and rotation before enabling the preview.

Good: earlier attribution can shorten the time between a public leak and revocation.
Caution: detection is not containment; exposed credentials still need immediate invalidation and impact review.

3. Strict GitHub Actions allowlists may need new blob-storage hosts

GitHub added new Actions blob-storage endpoints to its meta API. Organizations that allow individual hosts need to add the inclusive ranges productionresultssa30 through productionresultssa49.blob.core.windows.net and productionresultssa100 through productionresultssa199.blob.core.windows.net to avoid interruptions to job summaries and logs.[4]

GitHub says no change is needed when an organization already allows the wildcard productionresultssa*.blob.core.windows.net. It also points administrators to the live meta API for the current endpoint list.[4]

Why this matters: a narrow egress policy can fail even while source checkout and the runner itself still appear healthy. That makes logs and summaries an easy-to-miss operational symptom.

Practical guidance: compare the live meta API with firewall policy, test from a representative runner, and document whether policy allows a wildcard or explicit hosts before changing production egress.

Good: GitHub published the exact host ranges and an authoritative machine-readable source.
Caution: broad wildcard access is simpler but may exceed an organization’s least-privilege policy.

4. Google and Voltus plan a 1-gigawatt virtual power plant

Google and Voltus announced an expanded agreement for a 1-gigawatt virtual power plant across the PJM grid region, which serves 67 million people in 13 states and Washington, D.C.[5]

Google says Voltus will aggregate flexible capacity from smart thermostats, batteries, industrial assets, and other participating homes and businesses. During peak demand, those resources would temporarily reduce energy use; participating customers are promised economic benefits such as bill savings or cash payments.[5]

How to read the number: this is an announced distributed-capacity target, not a new 1-gigawatt power station and not proof that the full amount is already enrolled or dispatchable. Google calls it a 10-fold expansion of an earlier 100-megawatt agreement.

Practical context: flexible-load programs can support grid reliability, but customers should examine device control, opt-out rules, compensation, privacy, and comfort or operational limits before enrolling.

Good: coordinated demand reduction can add capacity without waiting for one large new plant.
Caution: the real value depends on enrollment, availability during peaks, customer consent, and verified delivery.

5. BioWare closes after more than three decades

The Associated Press reports that Electronic Arts is shutting down BioWare and that the next Mass Effect game has been canceled. The report was updated at 6:38 a.m. UTC on October 22 and says BioWare announced the closure on social media the previous day.[6]

AP says Bloomberg reported 400 layoffs across EA, including about 50 at BioWare; EA representatives had not responded to AP’s request for comment on those layoff figures. BioWare was founded in 1995 and acquired by EA in 2007.[6]

Evidence boundary: the studio closure and game cancellation are reported as confirmed. The 400-person and BioWare-specific layoff figures are attributed to Bloomberg through AP, not independently confirmed by EA in the checked report.

Practical context: players should treat any unofficial release dates, preorder claims, or “leaked” replacement projects as unconfirmed unless EA publishes them through a verified channel.

Good: BioWare’s catalog and three-decade influence remain part of game history.
Caution: the closure ends an established studio and leaves workers and an announced franchise project affected.

What to do next

  1. API teams: keep model decisions bounded by deterministic authority rules.
  2. Security teams: make public-secret alerts trigger a rehearsed revoke-and-review workflow.
  3. GitHub administrators: compare runner egress policy with the current meta API before logs disappear.
  4. Energy-program customers: read control, compensation, privacy, and opt-out terms before enrolling devices.
  5. Players: rely on verified publisher channels for future Mass Effect news.

Need help securing, fixing, or planning your technology? Schedule The IT Guys

Frequently asked questions

Is OpenAI’s Decisions API still a beta?

No. OpenAI’s October 22 documentation says it is generally available, although the supporting model list is currently limited to gpt-6-luna.[2]

Does GitHub public monitoring stop a secret leak?

No. It is designed to detect and attribute exposed credentials in public commits; response teams still need to revoke, rotate, and investigate.[3]

Does every GitHub Actions customer need a firewall change?

No. GitHub says customers already allowing productionresultssa*.blob.core.windows.net need no change.[4]

Is Google building a new 1-gigawatt power plant?

Not in the conventional sense. The announcement describes a virtual power plant that coordinates flexible capacity from distributed devices and industrial assets.[5]

Is the next Mass Effect still in development?

No. AP reports that the upcoming game was canceled as BioWare closed.[6]

Sources checked for this edition

  1. OpenAI — Build more responsive apps with the Decisions API
  2. OpenAI API documentation — Decisions
  3. GitHub Changelog — Public monitoring now available with data residency
  4. GitHub Changelog — Meta API endpoints updated for Actions blob storage
  5. Google — We are working with Voltus to build a 1-gigawatt virtual power plant
  6. Associated Press — Video game developer BioWare shuts down, next ‘Mass Effect’ canceled amid broader layoffs at EA

Source state checked through October 22, 2026, 5:04 p.m. EDT / 2026-10-22T21:04:26Z. OpenAI, GitHub, and Google product or capacity claims are first-party statements. The AP page blocked automated direct retrieval, so its exact timestamp and body were cross-checked through an attributed Cox Media Group syndication copy while retaining AP’s canonical URL.

Bottom line: speed and scale are useful only when authority, evidence, network dependencies, customer consent, and human consequences remain visible.