Release 0.14.0 - #677
Merged
Merged
Conversation
A new package_manager option installs an Ember application's NodeJS dependencies with pnpm, Yarn, or npm, and deprecates yarn: true; the Heroku generator identifies pnpm projects to the buildpack and pins the NodeJS and package manager versions the applications declare, and no longer adds rails_12factor to the Gemfile. Co-Authored-By: Claude Fable 5.1 <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
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.14.0, carrying the changes merged since 0.13.2:
package_manageroption to install an application's NodeJS dependencies with pnpm (package_manager: :pnpm), yarn, or npm.pnpm_pathimplies pnpm the wayyarn_pathimplies yarn. The package manager is read through the newEmberCli::App#package_managerandEmberCli::App#pnpm?(Add a package_manager option with pnpm support #676)yarn: truein favour ofpackage_manager: :yarn. The shorthand still selects yarn, with a deprecation warning, and will be removed in1.0(Add a package_manager option with pnpm support #676)rails generate ember:heroku, with a root-levelpnpm-lock.yaml, and pin the package manager version in the generatedpackage.jsonfrom thepackageManagerthe Ember applications declare, read through the newEmberCli::App#package_manager_spec(Add a package_manager option with pnpm support #676)rails_12factorto theGemfilefromrails generate ember:heroku. Rails serves the twelve-factor behaviour the gem backported natively since5.0, and every Rails version this gem supports is>= 5.2. To upgrade, removerails_12factorfrom your project'sGemfile(Stop injecting rails_12factor from the Heroku generator #672)EmberCli::App#yarn_enabled?withEmberCli::App#yarn?(Detect Yarn the same way the installer does #673)package.jsonthatrails generate ember:herokuwrites, from theengines.nodethe Ember applications declare, read through the newEmberCli::App#node_engine. Applications that declare different versions are left unpinned (Pin the Heroku build's NodeJS version to what the app requires #674)Bumps
EmberCli::VERSIONfrom0.13.2to0.14.0and retitles the unreleased CHANGELOG section accordingly. A minor bump rather than a patch: the release adds an option, deprecates one, renamesApp#yarn_enabled?, and changes what the Heroku generator writes.After merging
Per
RELEASING.md: tagv0.14.0on the merge, push the tag, thengem build ember-cli-rails.gemspec && gem push ember-cli-rails-0.14.0.gem.Generated by Claude Code