-
Notifications
You must be signed in to change notification settings - Fork 200
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
Prepare a batch of releases. #558
Conversation
aomarks
commented
Jun 28, 2018
•
edited
Loading
edited
- dom5@3.0.1
- @polymer/tools-common@2.0.1
- polymer-analyzer@3.0.2
- polymer-project-config@4.0.2
- browser-capabilities@1.1.1
- @polymer/esm-amd-loader@1.0.2
- polymer-bundler@4.0.2
- polymer-build@3.0.4
- polyserve@0.27.12
- wct-sauce@2.0.3
- polymer-linter@3.0.1
- polymer-editor-service@2.2.2
- polymer-cli@1.7.7
No updated version of |
Oh good point, I'll add the packages with NPM audit fixes. Was only looking at CHANGELOGs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Awesome thanks! |
All releases done! @TimvdLippe how are we looking with the NPM audit issues now? |
After the NPM packages with the NPM audit fixes were released
Update: Maybe this is also caused by my minimalistic setup (I only use |
@hastebrot @aomarks Audit issues in all other packages are resolved 🎉 However, the |
@TimvdLippe can I ask you to also look at Polymer/polymer-modulizer#452 later if you have time? |
@web-padawan I think we need to import |
@TimvdLippe that's a valid point. I recall some PR to import At least it would be nice to have another modulizer release before importing it here, as there are at least 2 merged but not released fixes. |