-
Notifications
You must be signed in to change notification settings - Fork 129
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: fastly/go-fastly
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v7.0.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: fastly/go-fastly
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v7.1.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 9 commits
- 62 files changed
- 6 contributors
Commits on Nov 7, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 067d3ba - Browse repository at this point
Copy the full SHA 067d3baView commit details
Commits on Nov 15, 2022
-
fastly: allow uploading compute package from memory (#384)
This change adds support for uploading compute packages using memory instead of loading them from file paths. In order to preserve backward compatibility, it prioritises the presence of the package path over the in-memory content. It will only proceed to load from memory when the package path isn't present. Signed-off-by: Gorka Lerchundi Osa <glertxundi@gmail.com> Signed-off-by: Gorka Lerchundi Osa <glertxundi@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for d3473c7 - Browse repository at this point
Copy the full SHA d3473c7View commit details
Commits on Nov 16, 2022
-
fastly: fix invalid package uploading test (#385)
It seems like the expected response from Fastly API slightly changed since it was added the test for invalid packages. Now, instead of returning package info with zeroed properties, it properly returns a specific HTTP error (bad request). This PR changes the test to be compliant with the new behaviour. Signed-off-by: Gorka Lerchundi Osa <glertxundi@gmail.com> Signed-off-by: Gorka Lerchundi Osa <glertxundi@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 9ca49d7 - Browse repository at this point
Copy the full SHA 9ca49d7View commit details -
Improve error response handling (#386)
Instead of panic'ing when an error response cannot be decoded from JSON, return a generic error which includes the read portion of the response body. Followup to @dgryski's comment: #367 (comment)
Configuration menu - View commit details
-
Copy full SHA for 400d150 - Browse repository at this point
Copy the full SHA 400d150View commit details
Commits on Nov 30, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 0f714c5 - Browse repository at this point
Copy the full SHA 0f714c5View commit details
Commits on Jan 4, 2023
-
Configuration menu - View commit details
-
Copy full SHA for cf8d92c - Browse repository at this point
Copy the full SHA cf8d92cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0774f09 - Browse repository at this point
Copy the full SHA 0774f09View commit details
Commits on Jan 19, 2023
-
feat(resource): implement Resource API (#390)
* feat(resource): implement Resource API * feat(resource): resource tests * fix(resources): tests now have fixtures generated * fix(resources): validation test checks expected error type * fix(resource): tests weren't correct
Configuration menu - View commit details
-
Copy full SHA for cfc27ee - Browse repository at this point
Copy the full SHA cfc27eeView commit details -
Configuration menu - View commit details
-
Copy full SHA for 83939c2 - Browse repository at this point
Copy the full SHA 83939c2View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v7.0.0...v7.1.0