Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
99 changes: 99 additions & 0 deletions changelog.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,12 +7,111 @@

Each entry links to the original announcement in our [changelog discussions](https://github.com/orgs/datum-cloud/discussions/categories/changelog), where you can ask questions and leave feedback. To see what is coming next, read the [roadmap](/platform/roadmap).

<Update label="November 16, 2026" description="Cloud Portal" tags={["AX/DX/UX"]}>
## Onboard your coding agent from project home

The project home page in the [Cloud Portal](https://cloud.datum.net) can now set up a coding agent for your project with one paste.

- **Onboard your agent to Datum:** click the pill on project home to copy a one-sentence setup prompt. Paste it into Claude Code, Codex, Cursor, Copilot, or another coding agent.
- **Ready in the right context:** the prompt names your organization and project. The agent installs `datumctl` and every official plugin, connects the Datum MCP server, the Docs MCP server, and the Datum skills, signs in, and switches to your project.
- **Easier to read:** each resource list is a card with a **View all** link, one status strip names the project's VPC, and next steps show as tiles with an **Ask Patch** card underneath.
- **Empty projects:** a project with nothing in it shows the **Ask Patch** box in place of search.
- **No layout jump:** the page keeps its shape while it loads.
- **Fixed:** services your project isn't entitled to no longer appear in the sidebar, home cards, or header. Before, clicking one led to "Service not found".

See [Agents overview](/agents/overview).

Details: [Add 'Onboard your agent to Datum' copy-prompt pill to project home](https://github.com/datum-cloud/cloud-portal/issues/1797) (#1797)
</Update>

<Update label="November 16, 2026" description="Organizations" tags={["Fix"]}>
## Invitations last seven days, and editors can enable services

People you invite have time to create a Datum account before the invitation runs out, and editors no longer need an owner to turn on a service.

- **Seven-day invitations:** invitations now expire after seven days instead of 24 hours. Before, invitees new to Datum often lost the invitation before they finished signing up.
- **Expiry you can see:** pending invitations on the team page show when they expire, such as "Expires in 6 days", and expired ones show an **Expired** badge.
- **Dead links explain themselves:** opening an expired or replaced invitation says "This invitation has expired" and asks you to get a new one from the person who invited you, instead of a generic error. Links that were already accepted or declined say so.
- **Editors can enable services:** organization editors can now enable, update, and turn off services such as Compute in their organization's projects, from the portal or `datumctl`. Before, the request was refused and an owner had to do it. Enabling a service starts billing for it.
- **Owner-only settings:** only organization owners can change an organization's general, contact, and delete settings. Other members see the settings with the note "Only organization owners can make changes."

See [Team management](/organizations/team-management).

Details: [Invitations expire before new users can sign up and accept them](https://github.com/datum-cloud/cloud-portal/issues/1823) (#1823), [Let organization editors manage service entitlements](https://github.com/datum-cloud/datum/pull/330) (#330)
</Update>

<Update label="November 16, 2026" description="Organizations" tags={["AX/DX/UX"]}>
## Let colleagues join by email domain

Organization owners can let anyone with a work email at their company's domains join the organization without an invitation.

- **Allowed email domains:** in the organization's **General** settings, owners pick domains from the verified [Domains](/domain-dns/domains) in the organization's projects, and choose the role people get when they join.
- **Clear status:** a badge shows whether joining is **On**, **Paused**, or **Checking**. When joining is paused, a warning gives the reason.
- **Offers, not automatic membership:** people at an allowed domain see an offer in the notification bell, such as "Your **acme.com** email address lets you join **Acme** organization as Viewer". New users see it during onboarding. Nobody joins without accepting.

Check warning on line 50 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L50

Did you really mean 'onboarding'?
- Public email providers can't be used as allowed domains.
- Owners can turn joining off at any time.

Details: [Let people join an organization by email domain, and email owners when someone joins](https://github.com/datum-cloud/cloud-portal/issues/1709) (#1709)
</Update>

<Update label="November 16, 2026" description="datumctl" tags={["Fix"]}>
## Console works with organization-wide contexts

Two `datumctl console` bugs reported by a customer are fixed.

- **No false permission errors:** with an organization-wide context, lists such as Workloads showed `forbidden ... at the cluster scope` for every role, including owners. The console now lists the organization's own resources, and the quota banner shows the organization's quota instead of an error.
- **Context switches apply under `--session`:** with `--session` or `DATUM_SESSION` set, picking a context in the switcher changed the header but not the requests. Requests now go to the context you pick, and nothing is written to your saved config.
- **No stray stack traces:** opening the context switcher late in a session no longer prints a stack trace over the console.

See [Interactive console](/datumctl/console).

Details: [List the org namespace in org-wide console mode and stop stray stack traces](https://github.com/datum-cloud/datumctl/pull/365) (#365), [Follow console context switches under a session override](https://github.com/datum-cloud/datumctl/pull/366) (#366)
</Update>

<Update label="November 13, 2026" description="gVPC" tags={["Fix"]}>
## Fewer network dropouts for instances

Instances on a gVPC network keep their internet access and DNS lookups through two failures that used to interrupt them.

Check warning on line 74 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L74

Did you really mean 'lookups'?

- **No repeated egress blackouts:** replies from the internet to an instance could be dropped for several seconds at a time, over and over, while every component reported healthy. DNS lookups to public resolvers timed out and other internet traffic stalled. Datum now delivers those replies while it relearns the route back to the instance.

Check warning on line 76 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L76

Did you really mean 'lookups'?
- **Moved instances keep DNS:** when an instance was recreated on a different host, its DNS lookups could be denied for minutes. Datum now removes the old host's record of the instance when the instance stops there.

Check warning on line 77 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L77

Did you really mean 'lookups'?

See [gVPC troubleshooting](/galactic-vpc/troubleshooting).

Details: [NAT replies to a tenant node drop for seconds when the kernel collects its next hop's neighbor entry](https://github.com/datum-cloud/galactic/issues/1392) (#1392), [Attachment status flips between nodes after an instance moves, dropping its routes](https://github.com/datum-cloud/galactic/issues/1385) (#1385)
</Update>

<Update label="November 13, 2026" description="Billing" tags={["AX/DX/UX"]}>
## See how and when contract fees are billed

The **Contract** section of a billing account in the [Cloud Portal](https://cloud.datum.net) now shows how often each fee is charged and which invoices are coming.

- **Fee terms:** each recurring fee shows its amount per month, quarter, or year, such as "$20,000 / quarter", how often it's charged, and whether it's billed in advance or in arrears.
- **Fees with a set term** say how long they run and when they end, such as "For 3 years, until November 12, 2029".
- **Upcoming invoices:** the next invoice, plus any in the coming year that charges a one-time, quarterly, or annual fee. Each lists its fees, their total ("plus usage" when usage is billed), and its due date from your payment terms.
- Upcoming invoices are estimates, before discounts and tax.

See [Contracts](/organizations/billing#contracts).

Details: [Show customers how and when their contract's fees are billed](https://github.com/datum-cloud/cloud-portal/pull/1815) (#1815)
</Update>

<Update label="November 13, 2026" description="DNS" tags={["Fix"]}>
## Add DKIM and other underscore records in the portal

- **Fixed:** adding a DNS record whose name has an underscore after a dot, such as a DKIM record at `<selector>._domainkey`, no longer fails with "A lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters". The record keeps its name exactly as you typed it, underscores included.

See [Authoritative DNS](/domain-dns/dns).

Details: [Let DKIM and other underscore records be added](https://github.com/datum-cloud/cloud-portal/pull/1817) (#1817)
</Update>

<Update label="November 12, 2026" description="datumctl" tags={["Fix"]}>
## Pick the right private zone with `--vpc`

The `datumctl dns` plugin no longer guesses when several zones share a domain, so a record can't land in another VPC's zone.

Check warning on line 112 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L112

Did you really mean 'VPC's'?

- **Ambiguous zones are refused:** every VPC's default private zone is `datum.internal`. When more than one zone matches the domain you typed, the command stops and lists each zone's object name and the VPCs that use it.

Check warning on line 114 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L114

Did you really mean 'VPC's'?

Check warning on line 114 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L114

Did you really mean 'VPCs'?
- **New `--vpc <name>` flag:** uses the zone that VPC resolves. It works on every `record` command and on `zone describe`, `delete`, `nameservers`, `import`, and `export`, for private zones only.
- **Name a zone directly:** pass a zone's object name in place of the domain, for example `datumctl dns record list managed-3f9c2a`.
- Deleting a private zone asks you to confirm with its object name.
Expand All @@ -30,10 +129,10 @@

- **Answers follow your instances:** when an instance is deleted, its old answers disappear within 1 to 2 seconds. A replacement's new address answers about 4 seconds after the instance is ready. Answers are cached for 30 seconds.
- **First lookup answers right away:** new instances get an answer to their first lookup immediately. Before, DNS gave no answer for 0 to 11 seconds after a deploy or restart, and apps that looked up a name at startup failed with `Temporary failure in name resolution`.
- **No failed lookups during rollouts:** DNS stays up through platform restarts, software updates and edge reboots, because servers drain traffic before they stop. Before, a single rollout caused about 75 seconds of failed lookups. Staging rollouts with steady lookups now lose none.

Check warning on line 132 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L132

Did you really mean 'lookups'?

Check warning on line 132 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L132

Did you really mean 'rollouts'?

Check warning on line 132 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L132

Did you really mean 'lookups'?

Check warning on line 132 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L132

Did you really mean 'rollouts'?

Check warning on line 132 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L132

Did you really mean 'lookups'?
- **Several servers per resolver address:** several healthy DNS servers share one resolver address, with health checks, in all three regions. A lost host or edge affects only the instances on that host. Requests to a server on another host now get replies instead of timing out.
- **Status you can trust:** zone status shows within seconds whether your records are being served.
- **Isolation between VPCs:** each VPC's answers are isolated from every other VPC. Removing a zone from a VPC returns `NXDOMAIN`, and deleting a VPC withdraws its access from every DNS server. Only the platform can change which DNS a VPC uses.

Check warning on line 135 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L135

Did you really mean 'VPCs'?

Check warning on line 135 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L135

Did you really mean 'VPC's'?

Private DNS is in preview. See [Private DNS](/domain-dns/private-dns).

Expand Down Expand Up @@ -71,7 +170,7 @@
<Update label="November 10, 2026" description="Application Load Balancer" tags={["Fix"]}>
## New load balancers serve traffic sooner

- **Fixed:** a new ALB no longer returns `503` for several minutes when its compute workload runs in a different location than the edge serving the request. Datum now rebuilds the load balancer's routing as soon as it learns which network the workload is on.

Check warning on line 173 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L173

Did you really mean 'balancer's'?

See [ALB troubleshooting](/alb/troubleshooting).

Expand Down Expand Up @@ -103,7 +202,7 @@
- **Fixed:** deleting a listener works on the first try.
- **Fixed:** the **Add listener** dialog no longer flashes a warning as it closes.

NLBs are early access. See [Network services](/galactic-vpc/networks/network-services).

Check warning on line 205 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L205

Did you really mean 'NLBs'?

Details: [Give the NLB page a traffic path layout](https://github.com/datum-cloud/network-services-operator/pull/890) (#890)
</Update>
Expand Down Expand Up @@ -234,7 +333,7 @@
- **Managed zone:** every network gets its own `datum.internal` zone. Compute publishes each Instance at `<instance-name>.instances.datum.internal`. See [Private DNS for Compute](/compute/private-dns).
- **Your own private zones:** associate private zones with a network for internal names. The zone class is now optional for private zones.
- **Network isolation:** a network can't be pointed at another network's private DNS, and the same names can be reused across networks without leaking answers.
- **Availability:** lookups go only to healthy DNS servers, so server updates no longer stall lookups until they time out.

Check warning on line 336 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L336

Did you really mean 'lookups'?

Check warning on line 336 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L336

Did you really mean 'lookups'?
- **Regions:** a private zone is served only in the regions its networks use, and is withdrawn from regions it leaves.
- **Fixed:** a CNAME that points into another private zone now returns the target's answer over UDP, not just the CNAME.
- **Fixed:** the managed `datum.internal` zone can't be deleted while its network uses it. Deleting a project still removes it.
Expand All @@ -251,11 +350,11 @@
Publish a network service on a public TCP or UDP port with a network load balancer (NLB).

- **Addresses and hostnames:** each location gets a public IPv6 address and a generated hostname you can point a CNAME at. IPv4 is available for single-port listeners where Datum has enabled it.
- **Health checks:** NLBs actively check backends and send new connections only to healthy ones.

Check warning on line 353 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L353

Did you really mean 'NLBs'?
- **UDP ports:** network services now accept UDP ports, and the create-service dialog has a TCP/UDP selector per port. A UDP listener also needs a TCP port on the backend for its health check.
- **Portal:** create an NLB, copy its hostname and address, and add, edit, or delete listeners in the [Cloud Portal](https://cloud.datum.net).

NLBs are early access. TLS listeners aren't supported yet, but a TCP listener forwards TLS traffic unchanged to your backend. Each route serves one backend. An ALB that points at a UDP port now reports a clear unsupported-protocol error.

Check warning on line 357 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L357

Did you really mean 'NLBs'?

See [Network services](/galactic-vpc/networks/network-services).

Expand All @@ -281,7 +380,7 @@
When a custom hostname's DNS is hosted outside Datum, the [Cloud Portal](https://cloud.datum.net) now shows whether it points at your ALB.

- **DNS Ready** appears once Datum sees the CNAME or matching IPs pointing at the ALB.
- **Awaiting DNS** appears until then, with a tooltip that names the record to add. The chip no longer spins indefinitely.

Check warning on line 383 in changelog.mdx

View check run for this annotation

Mintlify / Mintlify Validation (datum-4926dda5) - vale-spellcheck

changelog.mdx#L383

Did you really mean 'tooltip'?
- **Fixed:** an ALB whose single backend carries the Host override can now be edited in the portal instead of showing **Managed with datumctl**.

See [Custom domains](/alb/operations/custom-domains).
Expand Down
Loading