Updating Dependency Version Per-compliance (Feb 17, 2026)

[kylanerace]

• Updates protobuf from 6.33.0 to 6.33.5
• Updates virtualenv from 20.35.4 to 20.36.1
• Updates filelock from 3.20.1 to 3.20.3
• Updates wheel from 0.45.1 to 0.46.2
• Updates pillow from 10.3.0 to 12.1.1
• Bumps ruff from 0.14.3 to 0.15.0
• Bumps nodeenv from 1.9.1 to 1.10.0
• Bumps identify from 2.6.15 to 2.6.16
• Bumps grpcio from 1.76.0 to 1.78.0

Covers:

• Bump filelock from 3.20.1 to 3.20.3 #168
• Bump grpcio from 1.76.0 to 1.78.0 #169
• Bump identify from 2.6.15 to 2.6.16 #170
• Bump nodeenv from 1.9.1 to 1.10.0 #171
• Bump ruff from 0.14.3 to 0.15.0 #172
• Bump pillow from 10.3.0 to 12.1.1 in /assembler_tools/hec-assembler-tools in the pip group across 1 directory #173
• Bump the pip group across 1 directory with 4 updates #174

Proposed changes

Describe the big picture of your changes here to communicate to the maintainers
why we should accept this pull request. If it fixes a bug or resolves a feature
request, be sure to link to that issue.

Types of changes

What types of changes does your code introduce to the Encrypted Computing SDK project?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you are unsure about any of them, do not hesitate to ask. We are
here to help! This is simply a reminder of what we are going to look for before
merging your code.

• I have read the CONTRIBUTING agreement
• Current formatting and unit tests / base functionality passes locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Further comments

N/A