Releasebot
Docs Latest Create account

Cloud Hosting and Deployment Release Notes

Updates for hosting platforms and services that build, deploy, and run applications.

Get this feed:

Products (7)

Latest Cloud Hosting and Deployment Updates

  • Nov 10, 2026
    • Date parsed from source:
      Nov 10, 2026
    • First seen by Releasebot:
      Nov 11, 2026
    Heroku logo

    Heroku

    .NET 8.0.134, 8.0.428, 9.0.124, 9.0.321, 10.0.115, 10.0.404 and 11.0.100 SDKs are now available

    Heroku adds updated .NET 8, 9, 10, and 11 SDKs and runtimes for builds.

    Change effective on 10 November 2026

    .NET 8.0.134, 8.0.428, 9.0.124, 9.0.321, 10.0.115, 10.0.404 and 11.0.100 SDKs have been made available for builds on Heroku.

    The .NET 8.0 SDKs include .NET Runtime 8.0.34 and ASP.NET Core Runtime 8.0.34. The .NET 9.0 SDKs include .NET Runtime 9.0.23 and ASP.NET Core Runtime 9.0.23. The .NET 10.0 SDKs include .NET Runtime 10.0.15 and ASP.NET Core Runtime 10.0.15. The .NET 11.0 SDK includes .NET Runtime 11.0.0 and ASP.NET Core Runtime 11.0.0.

    For additional information, please see our article on .NET support.

    Original source
  • Nov 10, 2026
    • Date parsed from source:
      Nov 10, 2026
    • First seen by Releasebot:
      Nov 11, 2026
    Heroku logo

    Heroku

    Go 1.27.4 and 1.26.11 are now available

    Heroku now supports Go 1.27.4 and 1.26.11, with version aliases updated to resolve to the latest patch releases.

    Go 1.27.4 and 1.26.11 are now available for use by Go apps on Heroku.

    In addition, we have updated the Go 1.27 and 1.26 version aliases to resolve to these new Go patch versions.

    See Go Versions for details on how to configure the Go version for your app.

    Original source

  • All of your release notes in one feed

    Join Releasebot and get updates from Heroku and hundreds of other software products.

    Create account
  • Nov 10, 2026
    • Date parsed from source:
      Nov 10, 2026
    • First seen by Releasebot:
      Nov 11, 2026
    Heroku logo

    Heroku

    Changes to when Automated Certificate Management renews certificates

    Heroku ACM now uses Let’s Encrypt renewal recommendations to time certificate renewals, including earlier renewals when suggested. The staged rollout requires no action, and current certificates remain active until replacements are ready.

    Starting November 16, 2026, Automated Certificate Management (ACM) checks with Let’s Encrypt when to renew each certificate. It uses ACME Renewal Information (ARI), a standard way for Let’s Encrypt to suggest a renewal time for each certificate (RFC 9773). We’re rolling out this change to apps in stages. No action is required.

    ACM still renews certificates one month before they expire. If Let’s Encrypt suggests renewing sooner, for example before it revokes certificates, ACM renews in the suggested time. Some certificates renew earlier than before. Each domain keeps serving its current certificate until the new one is ready.

    To see when your app’s certificates expire, run the command:

    $ heroku certs -a example-app

    For more information, see the Certificate Renewal section for ACM.

    Original source
  • Nov 10, 2026
    • Date parsed from source:
      Nov 10, 2026
    • First seen by Releasebot:
      Nov 11, 2026
    Heroku logo

    Heroku

    Changes to how Automated Certificate Management retries failing certificates

    Heroku updates Automated Certificate Management on November 11, 2026, adding a six-hour wait between failed custom-domain renewal checks and stopping attempts after seven days without a valid certificate. Users can correct DNS settings and manually retry with a CLI command.

    Starting November 11, 2026, Automated Certificate Management (ACM) changes how it retries certificate renewals for custom domains.

    • When a custom domain fails a check, for example because its DNS isn’t set up, ACM waits at least 6 hours before it tries again. To retry sooner, use the heroku certs:auto:refresh command.
    • After 7 days without a valid certificate and ACM still can’t issue one, ACM stops trying the domain. It sends a reminder about once a week while the domain stays in this state.

    To get a certificate, fix the domain’s setup by pointing it at the DNS target that heroku domains shows. Then, run the command to try again:

    $ heroku certs:auto:refresh -a example-app

    For each failure reason and how to fix it, see the Troubleshooting section for ACM.

    Original source
  • Nov 10, 2026
    • Date parsed from source:
      Nov 10, 2026
    • First seen by Releasebot:
      Nov 11, 2026
    Netlify logo

    Netlify

    Netlify Server is now available in Early Access

    Netlify launches Netlify Server in Early Access, bringing long-lived Node.js backends that handle concurrent requests, keep database pools and caches warm, support WebSockets and run popular Node.js frameworks. It scales with demand and is free during Early Access.

    Netlify Server lets you run your application’s backend as a long-lived Node.js server. Netlify provisions it, scales it with demand and scales it down to zero when nothing is using it.

    Whereas, functions handle one request per instance and finish when they respond, some backends need more. Netlify Server keeps running between requests so that it can:

    • Handle many requests at once in a single instance.
    • Keep warm database connection pools and in-memory caches.
    • Hold WebSocket and Server-Sent Events connections open, for things like live chat and real-time collaboration.
    • Run an existing Express, Hono, Fastify or Koa app as-is, without additional adapters.

    A server is a single file at netlify/server/index.ts. Here’s a simple way to get started without any framework, with the same signature as a Netlify function:

    import type { Context } from '@netlify/server';

export default async (req: Request, context: Context) => {
  return Response.json({ message: `Hello from ${context.geo.city}` });
};

    Every deploy, including branch deploys and Deploy Previews, runs its own version of your server. The server can use other platform primitives, such as Netlify Database, Netlify Blobs and the AI Gateway, with no setup.

    Full-stack frameworks such as Next.js, Astro and Nuxt don’t run on Netlify Server yet, so for now we recommend using a server in projects that don’t use one of these frameworks.

    Early Access

    Netlify Server is available on credit-based plans and on Enterprise plans with credits enabled. Its APIs and behavior might change during Early Access.

    In Agent Runners, we’re releasing Netlify Server gradually over the coming days, so your agent runs might not use it right away.

    Limits

    These are the main limits during Early Access:

    • A server scales up to 3 instances, or 1 instance on credit-based Free and Personal plans.
    • An instance always scales to zero after 5 minutes without requests. After Early Access, you’ll be able to keep a minimum number of instances running, so infrequent requests won’t need to wait for your server to start.

    The limits page has the full list.

    Pricing

    Netlify Server is free to use during Early Access. When it reaches General Availability, usage will be charged in credits based on two meters: reserved memory (in GB-hours) and active CPU time (in vCPU-hours). We’ll announce the cost in credits before then. If your usage during Early Access suggests you’ll need to upgrade your plan or buy more credits, we’ll let you know.

    Other metered features in your project are billed as usual, and every request your server handles counts toward the web requests meter. Learn more about pricing.

    To get started, read the Netlify Server docs and follow the guide to create your first server.

    Original source
  • Nov 10, 2026
    • Date parsed from source:
      Nov 10, 2026
    • First seen by Releasebot:
      Nov 11, 2026
    Netlify logo

    Netlify

    Netlify Visual Editor deprecation and end of life timeline

    Netlify is retiring Visual Editor in February 2027, while offering Agent Runners as a prompt-based way to edit projects with side-by-side previews before publishing. Existing Visual Editor users can continue until its end-of-life date.

    Netlify Visual Editor is deprecated as of November 10, 2026, and will reach end of life on February 8, 2027. After that date, Visual Editor will no longer be available or supported.

    Your sites stay live and your content stays right where it is. The only thing that changes is how you make edits.

    Timeline

    • Date: November 10, 2026
      • What happens: Visual Editor is deprecated. No new teams or projects can enable it.
    • Date: February 8, 2027
      • What happens: Visual Editor reaches end of life and is no longer available or supported.

    If your team already has Visual Editor enabled, you can keep using it until February 8, 2027, and the Visual Editor docs still apply until then. No new teams or projects can enable Visual Editor.

    How to keep editing

    The Visual Editor, previously called "Netlify Create", was designed before prompting updates was a common way people worked. Depending on how your team works, here’s how to keep editing:

    • Using a CMS? Keep editing there. Nothing changes for you.
    • Already using Claude or Codex? Point your agent to netlify.ai to get the skills and tools it needs to work with your project.
    • Want to edit with a prompt in Netlify? Open your project and tell Agent Runners what to change. There’s nothing to install, configure, or connect first. You’ll see the result in a side-by-side preview, and nothing goes live until you publish.

    Edit with Agent Runners

    Agent Runners runs on credits, so you need a credit-based plan or an Enterprise plan that uses credits. If you’re on a legacy plan, compare plans or learn how to change your pricing plan.

    A few things you can ask Agent Runners for:

    • Edit content: “Update the homepage headline and swap the hero image.”
    • Fix a layout: “The pricing cards stack badly on mobile. Fix the spacing.”
    • Add a page: “Add an About page with our team and a contact form.”

    Share feedback and get help

    We’ll keep adding to what Agent Runners can do, and we want to hear what you’d like next. Tell us in the Netlify Discord, where the team and other builders are around to help and swap tips.

    Learn more in the Agent Runners docs, or reach out to Netlify Support with any questions.

    Original source
  • Nov 10, 2026
    • Date parsed from source:
      Nov 10, 2026
    • First seen by Releasebot:
      Nov 11, 2026
    DigitalOcean logo

    DigitalOcean

    Now Available: Claude Fable 5.2

    DigitalOcean adds Anthropic’s Claude Fable 5.2 to Serverless Inference, Inference Router preview, model synthesis, and Evaluations for eligible customers in supported regions, with reported faster output and lower token pricing than Fable 5.1.

    Claude Fable 5.2, which Anthropic calls its most capable generally available model for technical work, is now available through Serverless Inference, Inference Router (Public Preview - no SLA; may change), model synthesis, and Evaluations to eligible customers in supported regions. Anthropic reports that, in its own testing as of November 2026, it generates output up to 30% faster than Claude Fable 5.1, at $8 / $40 per million input / output tokens, lower than Fable 5.1’s $10 / $50 (USD, excluding taxes subject to change), actual results vary by workload and configuration. It runs on the same DigitalOcean account, API, and invoice you already use for serverless inference billed by DigitalOcean.

    Anthropic and Claude are trademarks of Anthropic, PBC. DigitalOcean is not affiliated with, and this announcement is not endorsed by, Anthropic.

    Access the model now ->

    Original source
  • Nov 10, 2026
    • Date parsed from source:
      Nov 10, 2026
    • First seen by Releasebot:
      Nov 11, 2026
    Cloudflare logo

    Developer Platform by Cloudflare

    Flagship - Evaluate Flagship feature flags from Rust

    Developer Platform releases an official Rust SDK for evaluating Flagship feature flags in asynchronous server applications through OpenFeature, with support for targeting, percentage rollouts, local evaluation, caching, and telemetry hooks.

    Flagship now has an official Rust SDK. Use it to evaluate feature flags from async Rust server applications through OpenFeature, with the same targeting rules and percentage rollouts as the other Flagship SDKs.

    Install the cloudflare-flagship ↗︎ crate

    cargo add cloudflare-flagship

    Register the provider and evaluate a flag

    let options = FlagshipClientOptions::builder()
    .app_id("<APP_ID>")
    .account_id("<ACCOUNT_ID>")
    .auth_token("<API_TOKEN>")
    .build()?;
let mut api = OpenFeature::default();
api.set_provider(FlagshipServerProvider::new(options)?).await;
let context = EvaluationContext::default().with_targeting_key("user-42");
let enabled = api
    .create_client()
    .get_bool_value("new-checkout", Some(&context), None)
    .await
    .unwrap_or(false);

    The provider evaluates flags over HTTP by default. Turn on local evaluation to download flag definitions and evaluate flags in-process, without a network request per evaluation. The SDK also supports structured evaluation context, an optional response cache, and logging and telemetry hooks.

    The SDK requires Rust 1.88 or later and a Tokio runtime. For setup and configuration options, refer to the Rust SDK documentation.

    Original source
  • Nov 10, 2026
    • Date parsed from source:
      Nov 10, 2026
    • First seen by Releasebot:
      Nov 11, 2026
    Cloudflare logo

    Developer Platform by Cloudflare

    Stream - Faster MP4 downloads from Cloudflare Stream

    Developer Platform now generates Cloudflare Stream MP4 downloads up to 40% faster, especially for on-demand videos longer than one minute. The improvement requires no implementation changes and works through the Dashboard, CLI, or API.

    Generating MP4 downloads from Cloudflare Stream is now up to 40% faster, with no changes to your implementation required. This improvement is most impactful for on-demand videos over 1 minute in duration.

    You can generate an MP4 download in the Dashboard, with the cf, the Cloudflare CLI CLI, or by sending a POST request.

    cf clishcf stream videos downloads create default --identifier "$VIDEO_UID"

    Create download

    curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/stream/$IDENTIFIER/downloads/default" \
  --request POST \
  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN"

    Both of these response include the download URL and processing progress:

    {
  "result": {
    "default": {
      "status": "inprogress",
      "percentComplete": 75.0,
      "url": "https://customer-&lt;CODE&gt;.cloudflarestream.com/&lt;VIDEO_UID&gt;/downloads/default.mp4"
    }
  },
  "success": true,
  "errors": [],
  "messages": []
}

    For more information, refer to Generate downloadable MP4 files.

    Original source
  • Nov 10, 2026
    • Date parsed from source:
      Nov 10, 2026
    • First seen by Releasebot:
      Nov 11, 2026
    Cloudflare logo

    Developer Platform by Cloudflare

    Workers, Pages - Workers Builds and Pages now list GitHub repositories based on your GitHub account

    Developer Platform updates GitHub repository selection for Workers Builds and Pages to show accounts, organizations, and repositories users can access. Existing connected projects remain unaffected and continue building.

    When you connect a GitHub repository to Workers Builds or Pages, the accounts and repositories you can pick from are now based on your own GitHub account, so the list reflects the repositories you work with on GitHub. Previously, the list was based on the Cloudflare Workers & Pages GitHub App installations linked to your Cloudflare account, so it could include repositories that you cannot access on GitHub.

    The list now shows:

    • Your own GitHub account, if the app is installed on it.
    • GitHub organizations that have the app installed, where you can access at least one repository.
    • The repositories you can access in each of them.
    • GitHub accounts that belong to other users are no longer listed, even if they have given you access to one of their repositories.

    What this means for you:

    • Authorizing the app and installing it are two separate steps on GitHub. For more details, refer to Install and authorize the app for Workers Builds and Pages.
    • If you have already authorized the app with your GitHub user: Nothing changes. You can check on the Authorized GitHub Apps page ↗︎ on GitHub.
    • If you have not: The next time you connect a repository, Cloudflare sends you to GitHub to authorize the app. You only need to do this once, even if someone else on your Cloudflare account already connected GitHub.
    • If the app is not installed on any GitHub account you can access: After you authorize, install the app on your own GitHub account or an organization, the same as before.
    • If an account or organization is missing from the list: Select Add GitHub account and install the app on it.
    • Projects that are already connected to a repository are not affected and keep building.

    For more information, refer to Repository access for Workers Builds and Pages.

    Original source