[Breaking] Remove API version constants #1411
Merged
+66
−17
Conversation
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
…SION constants These constants caused unintended breaking changes every quarter when API versions were updated, violating semantic versioning principles. Developers must now explicitly specify API versions in Context.setup, giving them control over when to upgrade and test new versions. See BREAKING_CHANGES_FOR_V15.md for migration guide. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
be1c304 to
3363fd1
Compare
sle-c
approved these changes
Oct 20, 2025
Contributor
sle-c
left a comment
There was a problem hiding this comment.
👍 explicit api version is good imo
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.
Removes
LATEST_SUPPORTED_ADMIN_VERSIONandRELEASE_CANDIDATE_ADMIN_VERSIONconstantsThese constants caused unintended breaking changes every quarter when API versions were updated, violating semantic versioning principles.
Developers must now explicitly specify API versions in Context.setup, giving them control over when to upgrade and test new versions. See BREAKING_CHANGES_FOR_V15.md for migration guide.
Description
Fixes #
Please, include a summary of what the PR is for:
How has this been tested?
Please, describe the tests that you ran to verify your changes.
Checklist: