Skip to content

chore(main): release 0.16.0 - #45

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--nextdeploy
Open

chore(main): release 0.16.0#45
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--nextdeploy

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.16.0 (2026-07-31)

⚠ BREAKING CHANGES

  • prepare: provision over static Go agent; fix deploy correctness - Fix silent failures, security path traversal, stale artifacts, domain collisions - BREAKING: prepare uses Go agent by default; app.name restricted to ^[a-z0-9-]+$

Features

  • Cloudflare SSR runtime, resource adoption, environments and shared CI (4fe82fb)
  • prepare: provision Caddy, the daemon service and Doppler in agent mode (d2aaf87)
  • prepare: provision over static Go agent; fix deploy correctness - Fix silent failures, security path traversal, stale artifacts, domain collisions - BREAKING: prepare uses Go agent by default; app.name restricted to ^[a-z0-9-]+$ (18591d1)

Bug Fixes

  • cloudflare: rollback now picks active version and purges cache (b08afea)
  • prepare: add caddy to the nextdeploy group so it can read app assets (a9c0c6f)
  • ship: point the DNS guide at the server's address, not its config name (05a43fc)

Performance Improvements

  • caddy: serve public/ from Caddy instead of proxying it to Node (115f9b5)

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot changed the title chore(main): release 0.15.2 chore(main): release 0.16.0 Jul 28, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--nextdeploy branch from 720b02c to 10a52c3 Compare July 28, 2026 23:07
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--nextdeploy branch from 10a52c3 to f69b600 Compare July 31, 2026 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants