Release 0.13.0 - #659
Merged
Merged
Conversation
Serve Vite-based applications from Vite's development server in development, require ember-cli-rails-assets >= 0.9.0 for the development-server asset helpers, and add the dev_server origin option. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
2 participants
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.
Summary
Release 0.13.0, carrying the development-server work now on main:
development(Serve Vite-based Ember apps from development server #653)ember-cli-rails-assets >= 0.9.0, which serves theinclude_ember_script_tagsstartup tags from the development server (Document asset helpers serving from the development server #654)originoption todev_server, separating the browser-facing origin from the bind address (Separate the browser-facing origin from the dev server's bind address #658)Bumps
EmberCli::VERSIONfrom0.13.0.beta1to0.13.0and retitles the unreleased CHANGELOG section accordingly. The0.13.0.beta1section stays as its own released entry — that version is already on rubygems (2026-08-22) and predates the development-server work, which is why this release needs a new version number.