-
Notifications
You must be signed in to change notification settings - Fork 236
fix: [SDK-4193] suppress unchecked cast warnings in Android bridge #1129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
fadi-george
merged 2 commits into
main
from
fadi/sdk-4193-suppress-unchecked-cast-warnings-in-android-flutter-bridge
Mar 19, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| name: Move Linear tickets to Deployed | ||
|
|
||
| on: | ||
| release: | ||
| types: [published, edited] | ||
|
|
||
| jobs: | ||
| linear-deployed: | ||
| uses: OneSignal/sdk-shared/.github/workflows/linear-deployed.yml@main | ||
| with: | ||
| release_body: ${{ github.event.release.body }} | ||
| secrets: | ||
| LINEAR_GITHUB_API_KEY: ${{ secrets.LINEAR_GITHUB_API_KEY }} | ||
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
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
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
Oops, something went wrong.
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.
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Copilot Autofix
AI 24 days ago
In general, the fix is to add an explicit
permissionsblock that grants only the minimumGITHUB_TOKENscopes required for this workflow. Because this workflow only triggers on releases and passesgithub.event.release.bodyinto a reusable workflow, the calling workflow itself does not appear to need any write permissions. A safe and minimal default is to setcontents: readat the workflow level, which is equivalent to a read‑onlyGITHUB_TOKENfor repo contents. The reusable workflow can still request additional permissions if it truly needs them.Concretely, in
.github/workflows/linear-deployed.yml, add apermissions:block near the top level, alongsidename:andon:(or immediately aftername:). Setcontents: read, which is the typical baseline for workflows that only need to read repository data. No imports or external dependencies are needed, since this is pure YAML configuration. Existing behavior of the workflow will remain the same in normal cases, except that unintended write capabilities viaGITHUB_TOKENwill be removed unless explicitly re‑granted.