release: 0.5.2#15
Open
stainless-app[bot] wants to merge 103 commits into
Open
Conversation
Closes #2340 (Finding 2)
Pin all GitHub Actions referenced in generated workflows (both first-party `actions/*` and third-party) to immutable commit SHAs. Updating pinned actions is now a deliberate codegen-side bump rather than implicit on every workflow run.
…t in workflow templates
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 30228104 | Triggered | Generic High Entropy Secret | 293b21b | src/XTwitterScraper.Tests/Models/Webhooks/WebhookCreateResponseTest.cs | View secret |
| 30228104 | Triggered | Generic High Entropy Secret | 293b21b | src/XTwitterScraper.Tests/Models/Webhooks/WebhookCreateResponseTest.cs | View secret |
| 30228104 | Triggered | Generic High Entropy Secret | 293b21b | src/XTwitterScraper.Tests/Models/Webhooks/WebhookCreateResponseTest.cs | View secret |
| 30228104 | Triggered | Generic High Entropy Secret | 293b21b | src/XTwitterScraper.Tests/Models/Webhooks/WebhookCreateResponseTest.cs | View secret |
| 30228104 | Triggered | Generic High Entropy Secret | 293b21b | src/XTwitterScraper.Tests/Models/Webhooks/WebhookCreateResponseTest.cs | View secret |
| 30228105 | Triggered | Username Password | 293b21b | src/XTwitterScraper.Tests/Models/X/Accounts/AccountCreateParamsTest.cs | View secret |
| 30228104 | Triggered | Generic High Entropy Secret | 293b21b | src/XTwitterScraper.Tests/Models/Webhooks/WebhookCreateResponseTest.cs | View secret |
| 30228104 | Triggered | Generic High Entropy Secret | 293b21b | src/XTwitterScraper.Tests/Models/Webhooks/WebhookCreateResponseTest.cs | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated Release PR
0.5.2 (2026-07-23)
Full Changelog: v0.5.1...v0.5.2
Chores
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions
Note
Release version 0.5.2 of the C# SDK
Bumps the version prefix in XTwitterScraper.csproj from
0.5.1to0.5.2and updates the release manifest and changelog accordingly.Macroscope summarized 3d5e4b1.