Fix/Netlify Analytics API v1 deprecation & switch to v2 #10
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
* for now just changed api version in url nothing else seemingly
|
Thanks @DavidM42. We can test your branch in our blog the next few days and then release version 2 of this action with API V2 |
Closed
NiklasMerz
approved these changes
Nov 17, 2021
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.
Looks like a super simple fix...for now.
I checked in the network tab of the Netlify dashboard and the requests looked exactly like in
v1only with thev1replaced withv2.Local testing of
index.jsexecution with this change seemed to worked, but I'd like to first test the whole workflow of our blog with this.Can you get a feature package version published for us to test in our blog actions workflow with @NiklasMerz ?
If that works, we should merge this soon