Skip to content
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

fix: Pin @oclif/command to 1.5.16 #319

Merged
merged 2 commits into from
Aug 6, 2019
Merged

fix: Pin @oclif/command to 1.5.16 #319

merged 2 commits into from
Aug 6, 2019

Conversation

Robdel12
Copy link
Contributor

@Robdel12 Robdel12 commented Aug 6, 2019

What is this?

v1.5.17 introduces type changes that breaks our build (even though the code is fine and the same): oclif/command@v1.5.16...v1.5.17

Until we can unbreak TS, we'll stick to this version.

1.5.17 introduces type changes that breaks our build (even though the code is
fine and the same):
oclif/command@v1.5.16...v1.5.17#diff-53649f4ba3d51e10eff913927cc17e0c

Until we can unbreak TS, we'll stick to this version.
This would have caught the issue with dependabot upgrading oclif command
@Robdel12 Robdel12 merged commit 2ba2698 into master Aug 6, 2019
@delete-merged-branch delete-merged-branch bot deleted the rd/pin-oclif-command branch August 6, 2019 16:20
djones pushed a commit that referenced this pull request Aug 6, 2019
## [0.9.2](v0.9.1...v0.9.2) (2019-08-06)

### Bug Fixes

* Pin `@oclif/command` to `1.5.16` ([#319](#319)) ([2ba2698](2ba2698)), closes [/github.com/oclif/command/compare/v1.5.16...v1.5.17#diff-53649f4ba3d51e10eff913927cc17e0](https://github.com//github.com/oclif/command/compare/v1.5.16...v1.5.17/issues/diff-53649f4ba3d51e10eff913927cc17e0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant