v0.3.4 - 2024-02-10
Bug Fixes
<details >
<summary>
(ci) `upload-artifact@v4` migration, `cross` compilation for meta + typegate (<a href="https://github.com/metatypedev/metatype/pull/571">#571</a>)
</summary>
The recent update to upload-artifact@v4
has some breaking changes as described
here.
This PR addresses them. It also fixes the cross-compilation issues with the
meta-cli
job in the release workflow.
Motivation and context
Issue
in release workflow.
Migration notes
No changes required.
Checklist
- [ ] The change come with new or modified tests
- [ ] Hard-to-understand functions have explanatory comments
- [ ] End-user documentation is updated to reflect the change
</details>
<details >
<summary>
(ci) Minor typo in `release.yml/docker` (<a href="https://github.com/metatypedev/metatype/pull/576">#576</a>)
</summary>
Small typo blocking the job that pushes the images to ghcr.io.
Motivation and context
Broken run.
Migration notes
No changes required.
Checklist
- [ ] The change come with new or modified tests
- [ ] Hard-to-understand functions have explanatory comments
- [ ] End-user documentation is updated to reflect the change
</details>
<details >
<summary>
(ci) Missing ts modules from `typegate` image (<a href="https://github.com/metatypedev/metatype/pull/577">#577</a>)
</summary>
Adds a check step to the typegate
's Dockerfile
and converts the
.dockerignore
to be a whitelist.
Motivation and context
The image for 0.3.3 has some files missing.
Migration notes
No changes required
Checklist
- [x] The change come with new or modified tests
- [x] Hard-to-understand functions have explanatory comments
- [ ] End-user documentation is updated to reflect the change
</details>
<details >
<summary>
(typegate) Fix `tmp` dir issue, bump to 0.3.4 (<a href="https://github.com/metatypedev/metatype/pull/583">#583</a>)
</summary>
- Fixes an issue with the prisma migration code being unable to properly
mktmpd
when running in the typegate
images. - Removes
cross
usage for all but the aarch64-unknown-linux-gnu
target in
the meta-cli
release jobs. Deno doesn't like being cross compiled, doesn't
like being built by the cross toolchain in general (even for the native
target). The consequence of all this is that the aarch64-unknown-linux-gnu
target will temporarily lack the full
version builds. - This also bumps the version of the 0.3.4 to get the fix out.
Motivation and context
The main TMP_DIR
was not created properly in the typegate
Dockerfile
.
Migration notes
No changes required
Checklist
- [ ] The change come with new or modified tests
- [ ] Hard-to-understand functions have explanatory comments
- [ ] End-user documentation is updated to reflect the change
</details>
<details >
<summary>
Remove unallowed fields (<a href="https://github.com/metatypedev/metatype/pull/569">#569</a>)
</summary>
Skip fields with policies in findListQueries
.
Motivation and context
Console.
Migration notes
N/A
Checklist
- [x] The change come with new or modified tests
- [x] Hard-to-understand functions have explanatory comments
- [ ] End-user documentation is updated to reflect the change
</details>
<details >
<summary>
Hotfix typo in `release.yml` (<a href="https://github.com/metatypedev/metatype/pull/580">#580</a>)
</summary>
Yes, another one lol. This removes the target
param from the release builder
which will default to the last stage of the Dockerfile, the epoint
stage. I
elected to remove the parameter rather than replacing the value in order to
remove one more place future changes will have to consider. (convention better
than configuration the saying goes (i think)).
Motivation and context
The typegate
images currently have the wrong target and thus the wrong
entrypoint
command.
Migration notes
No changes required
Checklist
- [ ] The change come with new or modified tests
- [ ] Hard-to-understand functions have explanatory comments
- [ ] End-user documentation is updated to reflect the change
</details>
Documentation
<details >
<summary>
(website) Cleanup (<a href="https://github.com/metatypedev/metatype/pull/521">#521</a>)
</summary>
<!--
Pull requests are squash merged using:
- their title as the commit message
- their description as the commit body
Having a good title and description is important for the users to get
readable changelog and understand when they need to update his code and
how.
-->
Describe your change
This mainly shuffles around the existing docs for better structure. Still a lot
to be done. The following pages are also empty as I lack the info regarding
their topics:
Super open to feedback. Bring up any points that you think should be mentioned
on each page and I'll add them.
</details>
<details >
<summary>
Getting started guide for the vscode extension (<a href="https://github.com/metatypedev/metatype/pull/578">#578</a>)
</summary>
Motivation and context
Documentation is missing.
Migration notes
No changes needed.
Checklist
- [ ] The change come with new or modified tests
- [ ] Hard-to-understand functions have explanatory comments
- [x] End-user documentation is updated to reflect the change
</details>
Features
<details >
<summary>
(sdk) Testing framework integration (<a href="https://github.com/metatypedev/metatype/pull/566">#566</a>)
</summary>
Motivation and context
Enable deploying directly from the typegraph instead of always relying on
meta-cli.
Migration notes
N/A
Checklist
- [x] The change come with new or modified tests
- [ ] Hard-to-understand functions have explanatory comments
- [ ] End-user documentation is updated to reflect the change
</details>