Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

set version field to default to v5.0 #80

Merged
merged 3 commits into from
Jan 23, 2023
Merged

Conversation

royalfig
Copy link
Contributor

@royalfig royalfig commented Jan 10, 2023

With the transition to an unversioned API, I removed version: 'canary' from the GhostAdminApi config, as it's optional and was generating warnings in the Action logs. These warnings were causing confusion among users.

Without the version field, the API client will default to the unversioned path.

Ref: https://forum.ghost.org/t/github-actions-error/34731/8 #76 #79

@royalfig royalfig marked this pull request as draft January 19, 2023 15:46
Copy link
Contributor Author

@royalfig royalfig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

default to version v5.0

@royalfig royalfig marked this pull request as ready for review January 19, 2023 19:50
@royalfig royalfig changed the title remove version field in api config set version field to default to v5.0 Jan 19, 2023
@royalfig
Copy link
Contributor Author

The only concern with this PR is this: Is there any risk to defaulting to v5.0?

@daniellockyer daniellockyer requested review from naz and removed request for daniellockyer January 23, 2023 09:16
Copy link

@naz naz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The is no risk defaulting to v5.0, it's a correct expected behavior. In the next version of the SDK we might drop the "canary" altogether, so it's expected for all clients to migrate now 👍

As long as the "themes" API does not have breaking changes the v5.0 is fine to pass. And when there are breaking changes or we start serving back-compatible responses, we will notify the instance owner of a "broken client".

@royalfig royalfig merged commit 3e75100 into main Jan 23, 2023
@royalfig royalfig deleted the update-accept-version branch January 23, 2023 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants