Skip to content

build(deps-dev): bump @trustify-da/trustify-da-api-model to ^2.0.9#556

Merged
a-oren merged 1 commit into
guacsec:mainfrom
a-oren:TC-4726
Jun 15, 2026
Merged

build(deps-dev): bump @trustify-da/trustify-da-api-model to ^2.0.9#556
a-oren merged 1 commit into
guacsec:mainfrom
a-oren:TC-4726

Conversation

@a-oren

@a-oren a-oren commented Jun 14, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Bump @trustify-da/trustify-da-api-model devDependency from ^2.0.8 to ^2.0.9 to pick up the new unknown field in SourceSummary and UNKNOWN value in Severity enum

Test plan

  • npm test passes (463 passing; 19 pre-existing OCI image test failures unrelated to this change)
  • npm run lint passes (0 errors)
  • Verified 2.0.9 contains unknown field in SourceSummary.ts and UNKNOWN in Severity.ts

Implements TC-4726

Summary by Sourcery

Build:

  • Bump @trustify-da/trustify-da-api-model devDependency from ^2.0.8 to ^2.0.9 in package.json and lockfile.

Pick up the new `unknown` field in SourceSummary and `UNKNOWN` value
in Severity enum from the API model package.

Implements TC-4726

Assisted-by: Claude Code
@sourcery-ai

sourcery-ai Bot commented Jun 14, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Dev dependency @trustify-da/trustify-da-api-model is bumped from ^2.0.8 to ^2.0.9 to consume new API model fields (SourceSummary.unknown and Severity.UNKNOWN), with lockfile updated accordingly.

File-Level Changes

Change Details Files
Update API model dev dependency to version ^2.0.9 and sync lockfile.
  • Bump @trustify-da/trustify-da-api-model devDependency in package.json from ^2.0.8 to ^2.0.9.
  • Update package-lock.json to lock @trustify-da/trustify-da-api-model to the new version and its transitive dependencies.
package.json
package-lock.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.75%. Comparing base (9a6adf7) to head (73f5f2a).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #556   +/-   ##
=======================================
  Coverage   90.75%   90.75%           
=======================================
  Files          36       36           
  Lines        7766     7766           
  Branches     1353     1353           
=======================================
  Hits         7048     7048           
  Misses        718      718           
Flag Coverage Δ
unit-tests 90.75% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@a-oren

a-oren commented Jun 14, 2026

Copy link
Copy Markdown
Contributor Author

Verification Report for TC-4726 (commit 73f5f2a)

Check Result Details
Review Feedback N/A No review feedback on this PR
Root-Cause Investigation N/A No sub-tasks created
Scope Containment WARN package-lock.json out-of-scope but expected for dependency bump
Diff Size PASS Minimal 2-line change proportionate to version bump task
Commit Traceability PASS Commit 73f5f2a contains "Implements TC-4726"
Sensitive Patterns PASS No secrets detected
CI Status PASS All 5 CI checks pass
Acceptance Criteria PASS 2/2 criteria met — version ^2.0.9 contains unknown field; tests pass
Test Quality N/A No test files in PR; Eval Quality: N/A
Test Change Classification N/A No test files modified
Verification Commands PASS npm test — 463 passing (19 pre-existing OCI failures on base branch)

Overall: PASS

All checks pass. The WARN on Scope Containment is expected — package-lock.json is always updated alongside package.json dependency changes.


This comment was AI-generated by sdlc-workflow/verify-pr v0.9.2.

@a-oren
a-oren requested review from Strum355 and ruromero June 14, 2026 13:49
@a-oren
a-oren merged commit 4227d87 into guacsec:main Jun 15, 2026
9 checks passed
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.

3 participants