Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / lerna/lerna issues and pull requests

#2402 - [command:version] Version number in related peerDependencies don't update

Issue - State: open - Opened by BioPhoton about 5 years ago - 6 comments

#2381 - Copy local package files to node_modules instead create symlink

Issue - State: closed - Opened by Soufraz about 5 years ago - 17 comments

#2378 - Results of `lerna diff` and `lerna changed` are inconsistent

Issue - State: closed - Opened by taozi0818 about 5 years ago - 6 comments

#2359 - Version command --no-push-tags | Publish command --push-tags

Issue - State: open - Opened by inakiarroyo about 5 years ago - 3 comments
Labels: type: feature

#2345 - Filter flag combination for dependencies or dependents only?

Issue - State: open - Opened by morewry about 5 years ago - 9 comments

#2341 - How to make jest tests that involve components imported from other packages?

Issue - State: closed - Opened by skywickenden about 5 years ago - 2 comments

#2341 - How to make jest tests that involve components imported from other packages?

Issue - State: closed - Opened by skywickenden about 5 years ago - 2 comments

#2340 - bootstrap --hoist: no bin symlink

Issue - State: closed - Opened by sveyret about 5 years ago - 1 comment
Labels: scope: package management

#2340 - bootstrap --hoist: no bin symlink

Issue - State: closed - Opened by sveyret about 5 years ago - 1 comment
Labels: scope: package management

#2337 - Version/publish based on tags only?

Issue - State: open - Opened by mmkal about 5 years ago - 3 comments

#2329 - [proposal] lerna publish with uncommitted changes

Issue - State: open - Opened by Filipoliko over 5 years ago - 11 comments

#2326 - How to prevent Lerna from automatically updating dependencies versions?

Issue - State: open - Opened by rfgamaral over 5 years ago - 17 comments

#2326 - How to prevent Lerna from automatically updating dependencies versions?

Issue - State: open - Opened by rfgamaral over 5 years ago - 21 comments

#2326 - How to prevent Lerna from automatically updating dependencies versions?

Issue - State: open - Opened by rfgamaral over 5 years ago - 18 comments

#2302 - Question - lerna publish stable version after alpha (preid)

Issue - State: closed - Opened by vikas027 over 5 years ago - 3 comments

#2302 - Question - lerna publish stable version after alpha (preid)

Issue - State: closed - Opened by vikas027 over 5 years ago - 3 comments

#2302 - Question - lerna publish stable version after alpha (preid)

Issue - State: closed - Opened by vikas027 over 5 years ago - 3 comments

#2302 - Question - lerna publish stable version after alpha (preid)

Issue - State: closed - Opened by vikas027 over 5 years ago - 3 comments

#2302 - Question - lerna publish stable version after alpha (preid)

Issue - State: closed - Opened by vikas027 over 5 years ago - 3 comments

#2302 - Question - lerna publish stable version after alpha (preid)

Issue - State: closed - Opened by vikas027 over 5 years ago - 3 comments

#2302 - Question - lerna publish stable version after alpha (preid)

Issue - State: closed - Opened by vikas027 over 5 years ago - 3 comments

#2302 - Question - lerna publish stable version after alpha (preid)

Issue - State: closed - Opened by vikas027 over 5 years ago - 3 comments

#2302 - Question - lerna publish stable version after alpha (preid)

Issue - State: closed - Opened by vikas027 over 5 years ago - 3 comments

#2302 - Question - lerna publish stable version after alpha (preid)

Issue - State: closed - Opened by vikas027 over 5 years ago - 3 comments

#2271 - Clarification needed for package lock files

Issue - State: closed - Opened by simllll over 5 years ago - 4 comments
Labels: scope: package management

#2271 - Clarification needed for package lock files

Issue - State: closed - Opened by simllll over 5 years ago - 4 comments
Labels: scope: package management

#2248 - CHANGELOGS not generated correctly when using "--conventional-graduate"

Issue - State: open - Opened by kelvincy over 5 years ago - 9 comments

#2237 - Use lerna exec to run a command in the root scope

Issue - State: closed - Opened by rheaditi over 5 years ago - 4 comments

#2237 - Use lerna exec to run a command in the root scope

Issue - State: closed - Opened by rheaditi over 5 years ago - 4 comments

#2237 - Use lerna exec to run a command in the root scope

Issue - State: closed - Opened by rheaditi over 5 years ago - 4 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 7 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 7 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 7 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 7 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 7 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 7 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 8 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 7 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 7 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 7 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 8 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 7 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 7 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 8 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 7 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 7 comments

#2218 - Lerna version not triggering CI with more than three tags at once

Issue - State: open - Opened by iurykrieger over 5 years ago - 8 comments

#2188 - support ignore "**Note:** Version bump only for package" when generate changelog.md in independent mode

Issue - State: open - Opened by hardfist over 5 years ago - 5 comments
Labels: type: feature

#2188 - support ignore "**Note:** Version bump only for package" when generate changelog.md in independent mode

Issue - State: open - Opened by hardfist over 5 years ago - 5 comments
Labels: type: feature

#2188 - support ignore "**Note:** Version bump only for package" when generate changelog.md in independent mode

Issue - State: open - Opened by hardfist over 5 years ago - 5 comments
Labels: type: feature

#2188 - support ignore "**Note:** Version bump only for package" when generate changelog.md in independent mode

Issue - State: open - Opened by hardfist over 5 years ago - 5 comments
Labels: type: feature

#2188 - support ignore "**Note:** Version bump only for package" when generate changelog.md in independent mode

Issue - State: open - Opened by hardfist over 5 years ago - 5 comments
Labels: type: feature

#2188 - support ignore "**Note:** Version bump only for package" when generate changelog.md in independent mode

Issue - State: open - Opened by hardfist over 5 years ago - 5 comments
Labels: type: feature

#2188 - support ignore "**Note:** Version bump only for package" when generate changelog.md in independent mode

Issue - State: open - Opened by hardfist over 5 years ago - 5 comments
Labels: type: feature

#2188 - support ignore "**Note:** Version bump only for package" when generate changelog.md in independent mode

Issue - State: open - Opened by hardfist over 5 years ago - 5 comments
Labels: type: feature

#2188 - support ignore "**Note:** Version bump only for package" when generate changelog.md in independent mode

Issue - State: open - Opened by hardfist over 5 years ago - 5 comments
Labels: type: feature

#2188 - support ignore "**Note:** Version bump only for package" when generate changelog.md in independent mode

Issue - State: open - Opened by hardfist over 5 years ago - 5 comments
Labels: type: feature

#2134 - lerna pack <...args> to generate local tarballs

Issue - State: open - Opened by indexzero over 5 years ago - 13 comments

#2116 - lerna version/publish creates duplicate versions + extra whitespace in change log

Issue - State: closed - Opened by jednano over 5 years ago - 13 comments

#2069 - lerna version --force modifier (feature request)

Issue - State: closed - Opened by nmccready almost 6 years ago - 6 comments

#2060 - lerna publish --canary publishes broken packages

Issue - State: open - Opened by bimbiltu almost 6 years ago - 15 comments

#2048 - npm outdated doesn't work

Issue - State: closed - Opened by simoneb almost 6 years ago - 3 comments
Labels: scope: package management

#2048 - npm outdated doesn't work

Issue - State: closed - Opened by simoneb almost 6 years ago - 3 comments
Labels: scope: package management

#2005 - Option - Use root `package.scripts` for `lerna run`

Issue - State: closed - Opened by jagretz almost 6 years ago - 5 comments

#2005 - Option - Use root `package.scripts` for `lerna run`

Issue - State: closed - Opened by jagretz almost 6 years ago - 5 comments

#2005 - Option - Use root `package.scripts` for `lerna run`

Issue - State: closed - Opened by jagretz almost 6 years ago - 5 comments

#2005 - Option - Use root `package.scripts` for `lerna run`

Issue - State: closed - Opened by jagretz almost 6 years ago - 5 comments

#2005 - Option - Use root `package.scripts` for `lerna run`

Issue - State: closed - Opened by jagretz almost 6 years ago - 5 comments

#1997 - lerna run prints "success" next to failed packages

Issue - State: closed - Opened by DanielSWolf almost 6 years ago - 17 comments

#1957 - Releasing on protected branch

Issue - State: open - Opened by lukasjuhas almost 6 years ago - 20 comments

#1957 - Releasing on protected branch

Issue - State: open - Opened by lukasjuhas almost 6 years ago - 20 comments

#1957 - Releasing on protected branch

Issue - State: open - Opened by lukasjuhas almost 6 years ago - 20 comments

#1955 - [feature request]run lerna script against staged-files

Issue - State: closed - Opened by mortenko almost 6 years ago - 6 comments

#1955 - [feature request]run lerna script against staged-files

Issue - State: closed - Opened by mortenko almost 6 years ago - 6 comments

#1840 - [Feature]: scope by package folder

Issue - State: open - Opened by veeramarni about 6 years ago - 18 comments

#1833 - `lerna changed` to include `from-package` option

Issue - State: open - Opened by darrenjennings about 6 years ago - 9 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments

#1433 - Correct way to use conventional-commits and canary / prerelease

Issue - State: closed - Opened by GordonSmith over 6 years ago - 26 comments