Set up Workiva Build, move build steps since Travis which no longer runs #296
Conversation
Security Insights(2) Vulnerable direct dependencies were detectedini < 1.3.6 via package-lock.jsonnode-fetch < 2.6.1 via package-lock.jsonAction Items
Questions or Comments? Reach out on Slack: #support-infosec. |
Public API ChangesNo changes to the public API found for commit c5162bb Showing results for c5162bb
Last edited UTC Jan 13 at 16:42:18 |
| @@ -40,11 +40,7 @@ mixin LifecycleTestHelper on Component { | |||
| 'context': context, | |||
| }); | |||
|
|
|||
| var lifecycleCallback = props == null | |||
There was a problem hiding this comment.
This change was just due to dartfmt
semveraudit-wf
added
semver: Error
semver: Patch
and removed
semver: Patch
semver: Error
labels
greglittlefield-wf
force-pushed
the
workiva-build
branch
from
837dfe7
to
c5162bb
Compare
greglittlefield-wf
requested review from
aaronlademann-wf,
joebingham-wk and
sydneyjodon-wk
| RUN pub run build_runner test --release -- --preset dart2js --exclude-tags=dart-2-7-dart2js-variadic-issues | ||
| RUN pub run build_runner test -- --preset dartdevc | ||
|
|
||
| RUN dart ./tool/run_consumer_tests.dart --orgName Workiva --repoName over_react --testCmd "pub run dart_dev test -P dartdevc" |
There was a problem hiding this comment.
Since Rosie supports this and the repo is now part of the Workiva ecosystem, should we nix this and set up consumer testing using Rosie? If not now, we could cut a ticket for it!
There was a problem hiding this comment.
Yup, totally! I just included it since we had it in the old CI, and would have something in place until we set it up
No description provided.