-
Notifications
You must be signed in to change notification settings - Fork 16
chore: bump MPL and reuse release script from MPL #1963
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
Conversation
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
0c2ee4e
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
Changes to the release files or the check-files action requires 2 approvals from CODEOWNERS
Detected changes to the release files or to the check-files action
eb52fca
into
main
Uh oh!
There was an error while loading. Please reload this page.
Issue #, if available:
Description
See test run here https://github.com/aws/aws-database-encryption-sdk-dynamodb/actions/runs/16919400700
Reason for no automatic PR creation?
When a PR is created by a GitHub Actions workflow using the built-in GITHUB_TOKEN, GitHub does not trigger other workflows (such as our PR CI which runs on
pull_request) for security reasons. This is a documented limitation designed to prevent accidental workflow recursion. As a result, automated PRs from the release workflow always remained in a "Waiting for status to be reported" state because the required CI checks never ran.This is well documented here: https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/trigger-a-workflow#triggering-a-workflow-from-a-workflow
As a demo of this behavior, see this PR: aws/aws-encryption-sdk#799
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.