fix: use unversioned api endpoint for tracker resource before 2.38 [LIBS-289] #1144
Conversation
This file contains 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
mediremi
approved these changes
Mar 18, 2022
|
Would love to see this available soon so we can use the tracker endpoint in our app! 🙂 |
dhis2-bot
added a commit
that referenced
this pull request
Mar 22, 2022
## [3.4.1](v3.4.0...v3.4.1) (2022-03-22) ### Bug Fixes * use unversioned api endpoint for tracker resource before 2.38 [LIBS-289] ([#1144](#1144)) ([b696974](b696974))
|
🎉 This PR is included in version 3.4.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
This fixes an issue which prevented the new Tracker endpoint (/api/tracker) from being used with the App Runtime because the tracker endpoint didn't support API versioning. This has been fixed in 2.38 and will be backported to future 2.37 and 2.36 patches, but an app developer shouldn't need to care about that.