Nick Schonning

I think there might be a need for 2 version numbers: 1. The schema of the questions/response value files (4). EX: v0.8.0 we store departments as '001', and v0.9.0 the...

> We saw that on x86 AWS instances running Ubuntu. Node hasn't supported x86 for quite some time https://github.com/nodejs/build/issues/885. I believe there may still be an Alpine x86 still, but...

@dependabot recreate

Yeah, I think it's even OK to keep coping the bindings to the new releases after this, but it's more of marking that we won't look at any issues raised...

https://github.com/sass/node-sass#node-version-support-policy

If you're using 8.0.0, then the it would be downloading the pre-built binary from https://github.com/sass/node-sass/releases/tag/v8.0.0. You might have another dependency that is trying to pull and older version that isn't...

@dependabot ignore this major version

I think the value would be more around adding helper functions around returning specific version info like what browserlist does. This was just a rough conversation starter off the previous...

May be work adding some links to the mobile client issue trackers in https://github.com/mastodon/mastodon/blob/main/.github/ISSUE_TEMPLATE/config.yml

I had tried to include the `AUTHORS.md` file before, but I think that is what stalled me out. Went back to this to add the CI again and unblock it...