Skip to content

Fix audit errors + split out audit to a separate workflow#397

Merged
zastrowm merged 1 commit intostrands-agents:mainfrom
zastrowm:audit_fix
Jan 13, 2026
Merged

Fix audit errors + split out audit to a separate workflow#397
zastrowm merged 1 commit intostrands-agents:mainfrom
zastrowm:audit_fix

Conversation

@zastrowm
Copy link
Copy Markdown
Member

@zastrowm zastrowm commented Jan 13, 2026

Description

Ran npm audit fix to update dependencies and then split out auditing to a separate workflow

NPM audit is blocking PRs & test statuses because it's done as part of running the tests. Instead do it as a separate workflow, which also cuts down on redundant checks since it's only done once instead of per OS/node-version (which don't matter because npm run audit is OS-independent

Also needed to add an as cast to fix an MCP issue - this is now issue #398

Type of Change

Bug fix

Testing

How have you tested the change?

  • I ran npm run check

Checklist

  • I have read the CONTRIBUTING document
  • I have added any necessary tests that prove my fix is effective or my feature works
  • I have updated the documentation accordingly
  • I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
  • My changes generate no new warnings
  • Any dependent changes have been merged and published

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Ran npm audit fix and split out auditing to a separate workflow

NPM audit is blocking PRs & test statuses because it's done as part of running the tests.  Instead do it as a separate workflow, which also cuts down on redundant checks since it's only done once instead of per OS/node-version
Copy link
Copy Markdown
Member

@Unshure Unshure left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this! Something I have been thinking about - Should we block prs if the audit check fails? I guess we should because if the pr brings in new dependencies, we should check if they pass our audit check.

@zastrowm
Copy link
Copy Markdown
Member Author

Should we block prs if the audit check fails? I guess we should because if the pr brings in new dependencies, we should check if they pass our audit check.

I'd rather keep it optional as I don't want all PRs to start failing because main has a dependency failing npm audit and I'd rather avoid the "override"s becoming a normal response to that

For new dependencies, I think we can use the npm run audit as a signal IMHO

@zastrowm zastrowm added this pull request to the merge queue Jan 13, 2026
Merged via the queue into strands-agents:main with commit d01b7f9 Jan 13, 2026
9 checks passed
@zastrowm zastrowm deleted the audit_fix branch January 13, 2026 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants