Conversation
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
stevensJourney
approved these changes
May 15, 2026
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
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.
This enables zizmor as a static analysis tool for GitHub actions, using the same configuration as the Dart SDK.
This mainly involves setting
permissions: {}for most jobs and adding a concurrency limit. Also, the release process has been changed a bit:gh release createis supposed to do that (docs, "If a matching git tag does not yet exist, one will automatically get created from the latest state of the default branch.").gh releasedirectly instead ofncipollo/release-action.While refactoring the release process, I realized we have the option of doing pre-releases! So, this also prepares a beta release for 1.14.0, which we can release without waiting for potential GRDB changes we might want to add as well.