-
Notifications
You must be signed in to change notification settings - Fork 1
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: freckle/aws-xray-client
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: aws-xray-client-persistent-v0.1.0.3
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: freckle/aws-xray-client
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 11 commits
- 21 files changed
- 2 contributors
Commits on Feb 25, 2022
-
Set
STACK_YAML
env for release`stack-upload-action` was updated recently to add this env variable. The main `stack.yaml` should be used for release purposes. Since `working-directory` is in each package of the monorepo, `stack` needs to look up a directory for this file. Using a relative path is a bit fragile but there doesn't appear to be a variable used to refer to the project root to avoid it.
Configuration menu - View commit details
-
Copy full SHA for 454ab71 - Browse repository at this point
Copy the full SHA 454ab71View commit details -
🤦♂️ Of course the previous commit fixing the release workflow won't run if it doesn't see the version has increased.
Configuration menu - View commit details
-
Copy full SHA for 98e0670 - Browse repository at this point
Copy the full SHA 98e0670View commit details
Commits on Apr 6, 2022
-
Support back to persistent-2.8
This allows testing back to lts-12.26 / ghc-8.4. We were already doing CPP in this module for another change, so this is pretty low effort once tracked down.
Configuration menu - View commit details
-
Copy full SHA for 213218b - Browse repository at this point
Copy the full SHA 213218bView commit details -
In newer GHCs, the order of these appears to matter and we must derive field types for record types that use them.
Configuration menu - View commit details
-
Copy full SHA for a544f07 - Browse repository at this point
Copy the full SHA a544f07View commit details -
Configuration menu - View commit details
-
Copy full SHA for 965d96c - Browse repository at this point
Copy the full SHA 965d96cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 24e4e1a - Browse repository at this point
Copy the full SHA 24e4e1aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5c23c4c - Browse repository at this point
Copy the full SHA 5c23c4cView commit details -
Configuration menu - View commit details
-
Copy full SHA for c2a0b7f - Browse repository at this point
Copy the full SHA c2a0b7fView commit details -
- Use versioned actions - Don't re-specify default lower bounds - Use oldest LTS so we get lowest lower bounds
Configuration menu - View commit details
-
Copy full SHA for f920cc0 - Browse repository at this point
Copy the full SHA f920cc0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4f17aea - Browse repository at this point
Copy the full SHA 4f17aeaView commit details -
Configuration menu - View commit details
-
Copy full SHA for 70d3f72 - Browse repository at this point
Copy the full SHA 70d3f72View 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 aws-xray-client-persistent-v0.1.0.3...main