fix: sbom on docs pipeline

[santosr2]

Pull Request

📋 Description

Type of Change

• 🐛 Bug fix (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
• 🔧 Code refactoring (no functional changes, no api changes)
• ⚡ Performance improvement
• 🧪 Test improvement or new tests
• 🔨 Build or CI/CD changes

🚀 What Changed

🧪 Testing

Test Configuration

• Tests pass locally with pnpm test
• Linting passes with pnpm lint
• Type checking passes with pnpm check
• Build succeeds with pnpm build && pnpm package

Test Cases

• Test case 1:
• Test case 2:
• Test case 3:

📸 Screenshots (if applicable)

🔗 Related Issues

• Fixes #(issue number)
• Closes #(issue number)
• Related to #(issue number)

📚 Documentation

• README.md updated
• action.yml updated (for input/output changes)
• Code comments added/updated
• Examples updated
• No documentation changes needed

⚠️ Breaking Changes

Migration Guide

Before:

# Old configuration

After:

# New configuration

✅ Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

🤝 Reviewer Notes

Areas of Focus

• Security implications
• Performance impact
• Backward compatibility
• Error handling
• Edge cases

Questions for Reviewers

---

📝 Additional Notes

[github-actions]

⚠️ Missing Linked Issue

This PR doesn't appear to be linked to an issue. For better tracking, please:

1. Link this PR to an existing issue using keywords like "fixes #123" or "closes #123"
2. Or create a new issue first if this addresses a new problem

Note: This check is automatically skipped for chore: and docs: PRs.

[github-actions]

🔍 No linked issues found

This PR doesn't appear to reference any issues. Consider:

1. Linking to an existing issue using "fixes #123" or "closes #123"
2. Creating an issue first if this addresses a new problem

Note: This check is automatically skipped for chore: and docs: PRs.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!