Skip to content

Determine whether we can remove support for projects/{}/{}/releases endpoints #2833

New issue
New issue
Closed
Closed
Determine whether we can remove support for projects/{}/{}/releases endpoints#2833
Assignees
szokeasaurusrex
Labels
CLIProduct area
@szokeasaurusrex

Description

@szokeasaurusrex
szokeasaurusrex
opened on Oct 9, 2025

The project-tied releases endpoints (/projects/{}/{}/releases) seem to be supported only for compatibility with legacy self-hosted versions:

sentry-cli/src/api/mod.rs

Lines 682 to 696 in 1fd856c

// for single project releases use the legacy endpoint that is project bound.
// This means we can support both old and new servers.
if release.projects.len() == 1 {
let path = format!(
"/projects/{}/{}/releases/",
PathArg(org),
PathArg(&release.projects[0])
);
self.post(&path, release)?
.convert_rnf(ApiErrorKind::ProjectNotFound)
} else {
let path = format!("/organizations/{}/releases/", PathArg(org));
self.post(&path, release)?
.convert_rnf(ApiErrorKind::OrganizationNotFound)
}

We should consider whether we still need this compatibility, and if not, we should deprecate and remove support

Metadata

Metadata

Assignees

Labels

CLIProduct area

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions