Skip to content

Revert "Use sync-exec for node 0.10"#242

Merged
hzoo merged 1 commit intomasterfrom
revert-220-sync-exec
Jun 23, 2016
Merged

Revert "Use sync-exec for node 0.10"#242
hzoo merged 1 commit intomasterfrom
revert-220-sync-exec

Conversation

@hzoo
Copy link
Copy Markdown
Contributor

@hzoo hzoo commented Jun 22, 2016

Reverts #220

https://github.com/nodejs/LTS - v0.10 maintenance is going to be over soon (same with 0.12) so it seems ok to drop support. We're in beta and a new tool as well

@hzoo hzoo merged commit 7eb4763 into master Jun 23, 2016
@hzoo hzoo deleted the revert-220-sync-exec branch June 23, 2016 00:25
gigabo added a commit to gigabo/lerna that referenced this pull request Jun 24, 2016
hzoo pushed a commit that referenced this pull request Jun 24, 2016
* Revert "Revert "Use sync-exec for node 0.10" (#242)"

This reverts commit 7eb4763.

* Node 0.10 compatibility for the `import` command
LoicMahieu added a commit to LoicMahieu/lerna that referenced this pull request Jun 28, 2016
* feature/pkg-main:
  Bootstrap: copy `main` property from package.json
  2.0.0-beta.23
  fix execSync use
  Add `onlyExplicitUpdates` flag so that only packages that have changed have version bumps rather than all packages that depend on the updated packages (lerna#241)
  Re-introduce node 0.10 support (lerna#248)
  2.0.0-beta.22
  Consistent naming in README `import` section (lerna#243) [skip ci]
  Lerna import (lerna#173)
  Revert "Use sync-exec for node 0.10" (lerna#242)
  Revert "Fix bootstrap install to use quotes around versions (lerna#235)"
  2.0.0-beta.21
  Fix bootstrap install to use quotes around versions (lerna#235)
  typo [skip ci]

# Conflicts:
#	src/commands/BootstrapCommand.js
rygine pushed a commit to awakesecurity/lerna that referenced this pull request Jun 28, 2016
* Revert "Revert "Use sync-exec for node 0.10" (lerna#242)"

This reverts commit 7eb4763.

* Node 0.10 compatibility for the `import` command
@lock
Copy link
Copy Markdown

lock bot commented Dec 28, 2018

This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant