-
-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.14.0 changelog (WIP) #384
Comments
Nice work @SBoudrias. lgtm Lets do another RC after we've merged the current 3 PRs. |
Yeah, there's also #387 who's a breaking change we should fix IMO. |
Agreed |
SGTM. In the changelog, for anything we're removing which has the potential to break existing generators could we add a note calling that out? For the most part the changelog appears to be additions and fixes otherwise. |
I added marks to what is a breaking change, and updated the changelog with the latest change (which was only fixing a regression). I think we should release 0.14 once #377 is merged. |
@SBoudrias agreed |
Merged #377 yesterday evening. Should be good for a release; cc @passy @sindresorhus @addyosmani |
Let's spend a little time testing this further against master on some of our generators. Assuming everything works as expected, release away! |
oh, and great work, Simon! :) |
We're currently at RC2 for the generator system. I'd love to cut and tag a release for 0.14.0 final at the weekend as I haven't seen any major blockers to date. Do we currently feel we're stable enough to do this? |
What should be fixed:
|
Reported bug been fixed. There've been a cosmetic issue about paths in the conflicters not being relative anymore - I'm not sure this is an issue as relative path are error prone (CWD can change and be inexact). Anyway, this issue is addressed in PR #409, we'll have to see what we do about it. |
Yo 1.0.5 got released using the unstable 0.14 and the rc2 holded a bug fixed this week. yeoman/yo#104 I think we should either release 0.14 or 0.14.0-rc3 as soon as possible. |
Is there anything holding us back from releasing generator master as 0.14? |
I think we should be good after merging the relative path PR for conflicts. |
Ok, so, my guess is we're ready for pushing 0.14.0 out of the gate RC-1 and 2 have been tested on the outside and we had some bug reports, all are fixed. |
Changelog moved here: https://github.com/yeoman/generator/releases/tag/v0.14.0 |
Generator system
New Features
generators.bulkCopy
andgenerators.bulkDirectory
) have been added to allow large folder being copied without template and conflict processing on each contained file. (example use case: transferring every file in the Wordpress repo) (Yeoman Generetor Crashes Because of endless recursion #350)this.src
andthis.dest
who're scoped file utility relative to thesourceRoot
anddestinationRoot
. The file utility is based on theGrunt.file
interface but add scope and filters (write filters to beautify, transcode, etc and validate filters to check conflicts). (For examples and discussion see Add scoped helpers environments from file-utils #378 and Improvement to core file utility #313)Bugs
end
event to be triggered multiple time (Bug 'end' emitted multiple times on overwriting files. #302 -> Fix Adding failing tests for end event firing multiple times when copying a file more than once. #402)runHook
are now cloned, so the hooked generator won't modify the state of these objects in the main one.generators
fetching methods likeextract
,fetch
,tarball
now rely on the NPMdownload
module.Runner system (Environment)
env.help
output (Help weirdness #364 and Help improvements #398)npm link
)env.register
now only take a string (filepath or NPM module name) to make sure the metadata it assign to the generator are relevant (namespace
,resolved
). If you want to register a stubbed generator for easy testing, then useenv.registerStub
, but know the metadata might be missing or erroneous.env.remote
andenv.engine
. This shouldn't change anything as they were broked or not used.Maintenance
See all: v0.13.4...v0.14.0-rc.2
The text was updated successfully, but these errors were encountered: