deploybase Release Notes
101 release notes curated from 1 source by the Releasebot Team. Last updated: Oct 21, 2026
- Oct 19, 2026
- Date parsed from source:Oct 19, 2026
- First seen by Releasebot:Oct 21, 2026
Connecting a private GitLab repository is guided
deploybase simplifies private GitLab setup with push-based or manual deploys, prefilled token forms, self-hosted support, and clearer token errors.
Connecting a private GitLab repository now starts with one question: deploy every push, or only when you click Deploy. You then get three steps and a link to a GitLab token form that opens filled in. Self-hosted GitLab is recognised and gets a token for just that project. Deploy tokens work too, with their username. If GitLab turns a token down, the message says why and what to tick.
Original source - Oct 18, 2026
- Date parsed from source:Oct 18, 2026
- First seen by Releasebot:Oct 21, 2026
See exactly which commit was built
deploybase links deployments to their checked-out commits, shows commit details in build logs, and retries builds against the same commit.
The build log now names the commit it checked out, and a deployment's page links that commit on your Git host. A retry rebuilds the same commit.
Original source All of your release notes in one feed
Join Releasebot and get updates from deploybase and hundreds of other software products.
- Oct 18, 2026
- Date parsed from source:Oct 18, 2026
- First seen by Releasebot:Oct 18, 2026
Your AI agent signs in with your account
deploybase now lets AI agents sign in through a browser and access a team, with one-click revocation while API keys remain available for CI.
You can now connect Claude Code, Cursor, Codex or another AI agent without creating an API key. The agent opens a browser window, you sign in and pick the team it may work in, and it works as you from then on, with at most the Member role. Agents you already connected with a key keep working, and keys remain the way to deploy from CI. Every signed-in agent is listed under Settings, API keys, where you can revoke it in one click.
Original source - Oct 17, 2026
- Date parsed from source:Oct 17, 2026
- First seen by Releasebot:Oct 18, 2026
A current Hugo, with Dart Sass
deploybase now builds Hugo sites with a current Hugo release and Dart Sass, while keeping its other build images up to date.
Hugo sites now build with a current Hugo release, with Dart Sass included. The other build images are up to date too, and from now on they follow new releases. Details are in the Hugo guide at docs.deploybase.eu/guides/hugo.
Original source - Oct 17, 2026
- Date parsed from source:Oct 17, 2026
- First seen by Releasebot:Oct 18, 2026
Removed team members stay removed
deploybase fixes team access so removed or departed members can’t rejoin automatically, and advises rotating their API keys.
Fixed a member you removed, or one who left, getting back into your team the next time they signed in. This could happen to the person who created the team and to members who joined through single sign-on. A removed person now lands in another team they belong to, or on a page saying they no longer have access, until someone invites them again. Team API keys keep working after a member leaves, so rotate any key they had.
Original source Similar to deploybase with recent updates:
- Smokeball release notes147 release notes · Latest Oct 2, 2026
- Cosmolex release notes20 release notes · Latest Jul 30, 2025
- PracticePanther release notes36 release notes · Latest Aug 11, 2026
- Salesforce release notes83 release notes · Latest Oct 1, 2026
- Microsoft release notes1046 release notes · Latest Oct 21, 2026
- Zoom release notes221 release notes · Latest Oct 19, 2026
- Oct 17, 2026
- Date parsed from source:Oct 17, 2026
- First seen by Releasebot:Oct 18, 2026
Viewers no longer see personal data or build logs
deploybase limits viewer access to sensitive submissions, logs, team emails, and invoices across the app, API, and AI agents.
Viewers on your team, such as a client's staff, still see projects, deployments and domains, but no longer see form submissions, the addresses a form notifies, build logs, function runs or other members' email addresses. Invoices are now visible to admins and owners only. The same limits apply in the API and to AI agents, and a viewer sees a short note where a panel is hidden. If a viewer needs any of this, give them the Member role under Settings, Members.
Original source - Oct 17, 2026
- Date parsed from source:Oct 17, 2026
- First seen by Releasebot:Oct 18, 2026
See your sites at a glance
deploybase adds private, post-publish production screenshots to project pages, making live sites easier to identify.
The projects page and each project's overview now show a screenshot of your site as it is live in production, so you can tell your sites apart without reading their names. A new screenshot is taken a minute or two after each publish, and only your team can see it. A site that never finishes loading keeps its framework icon instead.
Original source - Oct 17, 2026
- Date parsed from source:Oct 17, 2026
- First seen by Releasebot:Oct 17, 2026
Visitor requests answered in the EEA by default
deploybase now routes site, preview and new custom-domain requests through CDN locations in the EU, Iceland and Norway, keeping visitor IP handling within the EEA. Existing custom domains remain worldwide until changed by an admin, and updated documents clarify the serving options and seven-day server log retention.
Requests to your sites, previews and new custom domains are now answered only by CDN locations in the EU, Iceland and Norway, so your visitors' IP addresses are handled inside the EEA. Visitors elsewhere still reach your site, from the nearest EEA location.
Custom domains added before this update stay on worldwide delivery until an admin switches them under Domains, in the Serving region card, where any custom domain can also be set to worldwide.
The privacy policy, data processing agreement and subprocessors page now describe this, and the agreement now says server logs are kept 7 days, not 30.
Original source - Oct 15, 2026
- Date parsed from source:Oct 15, 2026
- First seen by Releasebot:Oct 16, 2026
Fixes and improvements
deploybase now lets users add their own records for any record type on domains with DNS it hosts.
Adding your own records to a domain whose DNS deploybase hosts works for every record type.
Original source - Oct 14, 2026
- Date parsed from source:Oct 14, 2026
- First seen by Releasebot:Oct 16, 2026
Longer build time limits, with an early warning
deploybase now counts user-caused failed or timed-out builds toward minutes, extends build limits, and flags slow steps before failures.
Builds that time out or fail in your own build step now count toward build minutes, as successful builds always have. A failure on the platform's side and a cancelled build still never count.
In return, a build can now run for 15 minutes on Free and 30 on every paid plan, up from 10. A build that uses 70% of its limit is flagged on its deployment page with its slowest step, so you hear about it before a build fails. A build that does reach the limit names the step that was running and how to speed it up.
Original source - Oct 12, 2026
- Date parsed from source:Oct 12, 2026
- First seen by Releasebot:Oct 12, 2026
Read the caller's IP address in a function
deploybase adds context.clientAddress to HTTP functions for rate limiting and abuse blocking.
HTTP functions can now read the IP address a request came from as
context.clientAddress, for rate limiting or blocking abusive callers.The platform sets it, so a caller cannot fake it with headers of their own. It is null on queued calls and scheduled runs.
Original source - Oct 12, 2026
- Date parsed from source:Oct 12, 2026
- First seen by Releasebot:Oct 12, 2026
Fixes and improvements
deploybase improves sign-in safety and asks users to sign in again after the update.
Signing in is safer.
If you were signing in while this update went out, sign in once more.
Original source - Oct 11, 2026
- Date parsed from source:Oct 11, 2026
- First seen by Releasebot:Oct 12, 2026
See what each API key did
deploybase adds API key activity tracking and 90-day request history visibility.
You can now see what each API key has been doing.
API keys shows a key's last action in plain words, such as "Created a deployment of Repro Site, via MCP, 20 min ago", next to its requests over the last 7 days. Select that count for every request it made in the past 90 days, refused ones included. Requests made before this update may show without the project they touched.
Original source - Oct 11, 2026
- Date parsed from source:Oct 11, 2026
- First seen by Releasebot:Oct 12, 2026
Agent API keys expire after 90 days
deploybase adds expiring agent keys, one-click rotation, and clearer API key management.
Keys made on the Connect your agent screen now expire after 90 days, so an agent you forgot about does not keep access forever. Agent keys you already have get the full 90 days, counted from this update, and keys you create on the API keys page still never expire. Rotating a key is now one click: same name, new secret, and the old one stops working at once. API keys now lists agent keys apart from CI keys and flags any that are about to expire or have not been used in 30 days.
Original source - Oct 10, 2026
- Date parsed from source:Oct 10, 2026
- First seen by Releasebot:Oct 11, 2026
Set up your AI agent with one prompt
deploybase now supports one-prompt AI agent setup for fast project deployment across Claude Code, Cursor, VS Code and Codex.
You can now hand deploybase to Claude Code, Cursor, VS Code, Codex or any other AI agent by pasting one prompt: it reads a setup page, connects itself and deploys your project. Creating the API key still takes a person, so an agent without one asks you to sign up and make it, and signing up brings you back to the connect screen. Copy the prompt from the homepage or the agents page, or from Connect your agent when you start a new project, where it already includes a fresh key.
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official release notes from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.