feat(releases): look a release up by its version label - #5
Merged
Conversation
haksungjang
force-pushed
the
feat/version-label-supersedes-prior
branch
from
August 4, 2026 02:24
8e301ac to
59e3fe2
Compare
haksungjang
force-pushed
the
feat/release-lookup-by-label
branch
from
August 4, 2026 02:24
70d372f to
65642b3
Compare
GET /v1/projects/{id}/releases takes ?release=4.0 — exact match on the
trimmed label, applied to the count as well as the page. At most one row
comes back, since a label has one live snapshot. An unknown label is an
empty 200, not a 404: that would be indistinguishable from the
existence-hide for a project you cannot see.
haksungjang
force-pushed
the
feat/release-lookup-by-label
branch
from
August 4, 2026 03:44
65642b3 to
0d975c5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GET /v1/projects/{id}/releases?release=4.0— exact match on the trimmed label, applied to the count as well as the page sototaldescribes the filtered set. At most one row comes back, since #4 gives a label one live snapshot. An unknown label is an empty200, not a404: that would be indistinguishable from the existence-hide returned for a project you cannot see.Served by
ix_scans_project_release_labelfrom #4;EXPLAINconfirms the planner takes it.Not here: the detail endpoints still anchor on
?scan_id=only. A permanent per-version URL (/notice?release=4.0) would mean threading a second anchor through nine services, so it is worth deciding separately.