Skip to content

Public channel name endpoint returns unpublished and deleted channels #6402

Open

Description

@rtibbles

🙂 Looking for an issue? Welcome! This issue is open for contribution. If this is the first time you’re requesting an issue, please:

  • Read Contributing guidelines carefully. Pay extra attention to Using generative AI. Pull requests and comments that don’t follow the guidelines won’t be answered.
  • Confirm that you’ve read the guidelines in your comment.

Overview

/api/public/channel/<channel_id> returns the name, description and version of any channel with that id, including unpublished and deleted channels. It needs no login. The v1 channel lookup endpoint returns only published channels that aren't deleted.

Complexity: Low
Target branch: hotfixes

Context

  • get_channel_name_by_id looks the channel up with Channel.objects.filter(pk=channel_id) and no other filter.
  • Reproduced: anonymous requests got 200 with name, description and version for a never-published channel and for a deleted channel.

The Change

  • get_channel_name_by_id should return only channels that are published and not deleted, the same set the v1 lookup returns, and 404 otherwise.

Acceptance Criteria

General

  • /api/public/channel/<id> returns 404 for an unpublished channel and for a deleted channel.
  • Published channels, public or private, return the same response as before.

Testing

  • Regression tests cover an unpublished, a deleted and a published channel.

AI usage

I chose which audit findings belong in #6398 and set the access pattern. Claude Code found and reproduced this gap and drafted this issue.

Activity

  1. added theissue type on Nov 15, 2026
  2. added
    good first issueSelf-contained, straightforward, low-complexity
    help wantedOpen source contributors welcome
    on Nov 15, 2026
  3. learning-equality-bot commented on Nov 15, 2026

    @learning-equality-bot
    Contributor

    Hi! 👋

    This issue is available for contribution and supports self-assignment. Here's how to get started:

    • Comment /assign to assign yourself to this issue
    • You can have up to 2 issues assigned at a time across all community repos
    • Dropping an issue has a 7-day cooldown before the slot opens up
    • Link your pull request to this issue when you submit it

    📖 Read the Contributing guidelines before starting.

    Are you preparing for Google Summer of Code? See our GSoC guidelines.

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

    DEV: backendgood first issueSelf-contained, straightforward, low-complexityhelp wantedOpen source contributors welcome

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions