Skip to content

Add uranusjr to the release manager allowlist in workflows#69494

Merged
uranusjr merged 1 commit into
apache:mainfrom
potiuk:add-uranusjr-release-manager
Jul 7, 2026
Merged

Add uranusjr to the release manager allowlist in workflows#69494
uranusjr merged 1 commit into
apache:mainfrom
potiuk:add-uranusjr-release-manager

Conversation

@potiuk

@potiuk potiuk commented Jul 6, 2026

Copy link
Copy Markdown
Member

Adds @uranusjr to the sender allowlist that gates the manually triggered
release-related workflows: registry build, registry backfill, docs
publishing to S3, and the DockerHub image release.


Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Opus 4.8)

Generated-by: Claude Code (Opus 4.8) following the guidelines

Adds @uranusjr to the sender allowlist that gates the manually
triggered release-related workflows (registry build/backfill,
docs publishing, and the DockerHub image release).

@jason810496 jason810496 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, and yes, TP need the permission to release the Java-SDK API reference and supervisor schema.json .

@uranusjr uranusjr merged commit 03b0ce3 into apache:main Jul 7, 2026
148 checks passed
@github-project-automation github-project-automation Bot moved this from Backlog to Done in Airflow Registry Jul 7, 2026
@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-3-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 03b0ce3 v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants