Open
Conversation
404 would indicate the resource was not found, but in this case it was
found, it just had no value.
Aligns with the other requests (e.g. `GET /flows/{flowID}/description`
sem-ver: bugfix
j616
approved these changes
Apr 17, 2026
Contributor
There was a problem hiding this comment.
I've put this as bugfix, although I can see at least one implementation that implements the behaviour as described, so I'd appreciate a second opinion on whether it's an API break
We generally consider version bumps from the perspective of the client. With that in mind, I think I'd consider it a feature bump at most. But I think it's a bit moot given the next release will be a minor release anyway
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
2 participants
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.
Details
404 would indicate the resource was not found, but in this case it was found, it just had no value.
Aligns with the other requests (e.g.
GET /flows/{flowID}/descriptionI've put this as bugfix, although I can see at least one implementation that implements the behaviour as described, so I'd appreciate a second opinion on whether it's an API break
Jira Issue (if relevant)
Jira URL: N/A
Related PRs
N/A
Submitter PR Checks
(tick as appropriate)
Reviewer PR Checks
(tick as appropriate)
Info on PRs
The checks above are guidelines. They don't all have to be ticked, but they should all have been considered.