Tags from graphula

v2.1.2.0

2025-06-18T17:44:25Z

feat: include insert error messages in GenerationFailure

This adds `*Either` versions of our two insert functions in the frontend
class, which return `Left String` errors, rather than `Nothing`s.

We define the maybe and either versions in terms of each other, making
this a backwards-compatible change, and use `MINIMAL` to ensure one or
the other always gets defined.

Then, we update our own instance to define either variants, with
informative messages for the failing cases.

Lastly, by using those either variants within the main loop, we can
collect (at least the final) `Left` value and report it as part of the
`GenerationFailure`.

The new README test confirms it works and shows what such an exception
will look like now.

Fixes #17.

v2.1.1.0

2025-06-17T18:20:25Z

feat: export EntityKeys

The member and associated type were already exported, so this is
strictly an addition. Now, users can express type signatures using this
class, as well as make their own instances.

Closes #90.

v2.1.0.1

2025-02-21T19:40:27Z

fix: implement semantic-release automation

This involves a few steps that I've kept together for easy reference as
an example:

1. Configure semantic release (`.releaserc.yaml`)

This uses a custom plugin, which I maintain, to upload with `stack
upload` as the main release action.

2. Trigger semantic release in the Release workflow

3. Update `package.yaml` to not have a meaningful version

Except the `2.` prefix is there, so my release plugin can infer it.

4. Update the README with release instructions

5. Update CHANGELOG to point to releases

This is how semantic-release folks recommend doing it. The Releases
(from now own) will have automatically-maintained changelog
information. I may backfill previous releases.

v2.1.0.1-rc-semantic-release.1

2025-02-21T16:33:14Z

fix: implement semantic-release automation

This involves a few steps that I've kept together for easy reference as
an example:

1. Configure semantic release (`.releaserc.yaml`)

This uses a custom plugin, which I maintain, to upload with `stack
upload` as the main release action.

2. Trigger semantic release in the Release workflow

3. Update `package.yaml` to not have a meaningful version

Except the `2.` prefix is there, so my release plugin can infer it.

4. Update the README with release instructions

5. Update CHANGELOG to point to releases

This is how semantic-release folks recommend doing it. The Releases
(from now own) will have automatically-maintained changelog
information. I may backfill previous releases.

v2.1.0.0

2023-12-13T20:32:48Z

v2.0.2.2: Add missing MonadUnliftIO instance to GraphulaLoggedT

2022-10-27T17:24:29Z

Add missing MonadUnliftIO instance to GraphulaLoggedT

This transformer was missed when adding `MonadUnliftIO` instances.
This instance is manually derived to avoid failure on older GHCs.

v2.0.2.1: Fixup stack-nightly

2022-08-15T14:07:46Z

Fixup stack-nightly

- Simplify CI nightly build
- Test newer persistent as a dedicated config
- Update to nightly as of today(ish)

v2.0.1.1

2022-03-30T19:48:04Z

v2.0.1.0

2021-11-02T15:59:17Z

v2.0.0.5

2021-05-17T13:04:26Z