Release#131
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 23, 2026 13:36
4351c9b to
7bbf0b6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@bunny.net/cli@0.11.0
Minor Changes
9696434Thanks @jamie-at-bunny! - feat(sites): newbunny sitesnamespace for static-site hosting.sites createprovisions a storage zone + pull zone + middleware router per site (zones are namedsites-<name>-<random id>so globally-taken names can't block the create; commands take the clean site name), prompting for the name (directory-name suggestion) and a custom domain when run interactively (Bunny DNS record, nameserver guidance, DNS wait + SSL);sites deployuploads immutable deploys (git-sha or content-hash IDs, no-op when unchanged) to preview URLs, and--production/--prodpublishes the live site by flipping the router'sCURRENT_DEPLOYenv var + purging the cache;sites deployments list/publish/prunecover rollback and cleanup;sites domainsattaches custom domains plus a*.preview.<domain>wildcard for per-deploy preview URLs;sites ci init(also offered bysites createon GitHub repos) scaffolds a GitHub Actions workflow with framework detection: previews on PRs, production on merges to main;sites link/unlink/show/upgrade/deleteround out the lifecycle. Concurrent deploys merge remote state records instead of overwriting. Site state lives at_bunny/site.jsoninside the storage zone (403-blocked by the router). The shared hostnames factory gains optionalonAdded/onRemovedhooks.Patch Changes
#120
3c3373aThanks @jamie-at-bunny! - fix(storage): shared TTY detection, non-interactive guard and cancel handling for zones update, aligned --force semantics, and linked-zone fallback for domains commands#120
3c3373aThanks @jamie-at-bunny! - fix(storage): type-to-confirm zone deletion, new storage unlink command, offer-to-link from the zone picker, and the replication confirmation now defaults to no#120
3c3373aThanks @jamie-at-bunny! - fix(storage): canonical plural command paths in hints, consistent decline handling in zones add, and --custom-404-path "" now clears the custom 404@bunny.net/cli-darwin-arm64@0.11.0
@bunny.net/cli-darwin-x64@0.11.0
@bunny.net/cli-linux-arm64@0.11.0
@bunny.net/cli-linux-x64@0.11.0
@bunny.net/cli-windows-x64@0.11.0
@bunny.net/config@0.1.3
Patch Changes
9696434Thanks @jamie-at-bunny! - rename@bunny.net/app-configto@bunny.net/configand add a top-levelsitesblock (name,dir,build) to the bunny.jsonc schema; the rootBunnyConfigSchemamakesappandsitesoptional so app-only, sites-only, and combined files all validate against the generated JSON Schema