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

Upgrade @bazel dependencies. #1091

Merged
merged 1 commit into from
Oct 2, 2019
Merged

Upgrade @bazel dependencies. #1091

merged 1 commit into from
Oct 2, 2019

Conversation

mprobst
Copy link
Contributor

@mprobst mprobst commented Oct 1, 2019

Just for hygiene.

@mprobst
Copy link
Contributor Author

mprobst commented Oct 1, 2019

I filed bazel-contrib/rules_nodejs#1220 for the non-hermeticity I encountered. I think it doesn't explain the failure I'm seeing here though, as I'd guess on CircleCI things should be hermetic, at least after emptying the cache?

@mprobst mprobst force-pushed the fix-vuln branch 2 times, most recently from 3154073 to 2a194e8 Compare October 2, 2019 07:02
Just for hygiene.
@mprobst mprobst merged commit f8f98a4 into master Oct 2, 2019
@mprobst mprobst deleted the fix-vuln branch October 2, 2019 12:45
@evmar
Copy link
Contributor

evmar commented Oct 3, 2019

This also broke for me after sync. The workaround appears to be bazel clean --expunge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants