Skip to content

fix: 🐛 use correct version for ng-packagr in v11#4

Merged
NachoVazquez merged 1 commit into
mainfrom
fix-ng-packgr-version-v11.0.x
Oct 30, 2020
Merged

fix: 🐛 use correct version for ng-packagr in v11#4
NachoVazquez merged 1 commit into
mainfrom
fix-ng-packgr-version-v11.0.x

Conversation

@NachoVazquez

Copy link
Copy Markdown
Contributor

PR Checklist

Please check if your PR fulfills the following requirements:

  • [ x ] The commit message follows our guidelines: CONTRIBUTING.md#commit
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ x ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

In v11.0.x ng-packagr is using an unexisiting version

Issue Number: N/A

v11.0.x uses the right version of ng-packgr

Does this PR introduce a breaking change?

[ ] Yes
[ x ] No

Other information

@NachoVazquez NachoVazquez merged commit 1b38e2c into main Oct 30, 2020
@NachoVazquez NachoVazquez deleted the fix-ng-packgr-version-v11.0.x branch October 30, 2020 05:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants