Revert "FEA-2609: Implemented Github Actions"

[matthewnitschke-wk]

Reverts #11

[semveraudit-wf]

Public API Changes

Issue: No Semver Audit Report Found for Base Commit

Base commit: c75a44730f3a7fc1cdd7208d5c45a24a72cdbfd0

This means we couldn't find semver audit data for the commit against which to compare the changes in this PR. Fixing this is a two step process. First, we'll need to generate the semver audit data for the base commit. Then we will have to generate the semver audit data for the head commit on this branch. This can be done by rerunning CI and/or manually running the semver audit tool.

Note: It may be sufficient to simply merge master into your branch.

Step 1: Generate Semver Audit Data for the Base Commit:

You can do this either by rerunning CI on the base commit or by manually running the semver audit tool locally on the base commit.

Option 1: Rerunning CI

Locate the build associated with the base commit (c75a447) in Workiva Build and rerun it.

Option 2: Run the Semver Audit Tool Manually

# Navigate to the root of the repo and check out the base commit:
$ git checkout c75a44730f3a7fc1cdd7208d5c45a24a72cdbfd0

# If this is a Dart project, run:
$ pub global run semver_audit report --repo Workiva/contextual_message --head-commit c75a44730f3a7fc1cdd7208d5c45a24a72cdbfd0

# If this is a Go project, run:
$ semver_audit_go report  --repo Workiva/contextual_message --head-commit c75a44730f3a7fc1cdd7208d5c45a24a72cdbfd0

Notes:

• If frugal files are generated during the build process prior to audit, please generate those locally before running the semver_audit command.
• If this is a Dart project, the manual steps above assume you have the Dart 2 SDK installed and activated and the semver_audit tool globally installed. See this Confluence post to install Dart 2. To globally install the semver_audit tool, run the following:

$ pub global activate --hosted-url https://pub.workiva.org semver_audit ^2.0.0

Step 2: Generate Semver Audit Data for this Branch's Head Commit:

You can do this either by rerunning CI on this PR or by manually running the semver audit tool locally against the head commit on this branch.

Option 1: Rerunning CI

This is often the easiest solution. Find the Workiva Build check on this Pull Request and simply rerun it.

Option 2: Run the Semver Audit Tool Manually

# Navigate to the root of the repo and check out the head commit on this branch:
$ git checkout 89718f9ccbe849acf31b216765acd47266e7c8d6

# If this is a Dart project, run:
$ pub global run semver_audit report --repo Workiva/contextual_message --base-commit c75a44730f3a7fc1cdd7208d5c45a24a72cdbfd0 --head-commit 89718f9ccbe849acf31b216765acd47266e7c8d6 --pull 13

# If this is a Go project, run:
$ semver_audit_go report --repo Workiva/contextual_message --base-commit c75a44730f3a7fc1cdd7208d5c45a24a72cdbfd0 --head-commit 89718f9ccbe849acf31b216765acd47266e7c8d6 --pull 13

Still Need Help?

If you are unable to resolve the issue on your own, either tag @Workiva/developer-experience in a PR comment or reach out to us in the #support-frontend-dx Slack channel.

Showing results for 89718f9

Powered by semver-audit-service. Please report any problems by filing an issue.
Reported by the dart semver audit client 2.2.2
Browse public API.

[aviary-wf]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure
• Verify aviary.yaml coverage of security relevant code

---

Questions or Comments? Reach out on Slack: #support-infosec.

[matthewnitschke-wk]

QA +1

🚀 @Workiva/release-management-p 🚢

[rmconsole-wf]

+1 from RM