Skip to content

Release 2.4.3 #4301

Closed
Closed

Description

@github-actions

Release tasks

Backports

To request or track a backport, comment /backport on the PR, comment
/backport <PR> on this issue, or add it to the checklist below. See
RELEASING.md: How to add backports
for details.


To manually control the release flow, see the
RELEASING.md: Manual Editing
section.

Available Commands

Comment commands:

  • /prepare: Determines version, creates tracking issue and preparation PR.
  • /prepare-complete [PR]: Marks preparation task as complete.
  • /create-release-branch: Cuts and pushes the release branch.
  • /create-rc: Tags and publishes a new release candidate (RC).
  • /process-backports: Cherry-picks pending backports.
  • /sync-changelog: Processes sync changelog tasks.
  • /backport <PRs>: Adds PRs to the backports and processes backports.
  • /promote: Promotes the latest RC to final release.

See RELEASING.md for details on how to use them.

Activity

  1. added
    type: releaseused by automation to identify issues and prs releated to releases
    on Oct 22, 2026
  2. rickeylev commented on Oct 22, 2026

    @rickeylev
    Collaborator

    /process-backports

  3. github-actions commented on Oct 22, 2026

    @github-actions
    ContributorAuthor

    Workflow failed for command process-backports (comment).

    See workflow run for logs.

  4. rickeylev commented on Oct 22, 2026

    @rickeylev
    Collaborator

    Had to manually backport. Looks good now though

    /promote

  5. github-actions commented on Oct 22, 2026

    @github-actions
    ContributorAuthor

    New Release Tagged! 🐍🌿

    Version 2.4.3 has been successfully generated and tagged on branch release/2.4.

  6. github-actions commented on Oct 22, 2026

    @github-actions
    ContributorAuthor

    Workflow failed for command promote (comment).

    See workflow run for logs.

  7. rickeylev commented on Oct 22, 2026

    @rickeylev
    Collaborator

    Ah, right. I've been refactoring the release workflows so they aren't entirely working on main yet. Triggering on the release branch worked.

    BCR PR is out and approved, so should merge eminently, or in hours, depending on the github weather.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    type: releaseused by automation to identify issues and prs releated to releases

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions