Release Checklist

1. Establish fork identity

Prefer using the Fork action on the upstream LM Studio Hub page so the Hub can display provenance. Use a unique, descriptive kebab-case name such as:

email-imap-smtp

Do not publish under altra/email, and do not leave the local development name as email-fixed.

Set manifest.json:

{
  "type": "plugin",
  "runner": "node",
  "owner": "YOUR_LM_STUDIO_USERNAME_OR_ORG",
  "name": "email-imap-smtp",
  "tags": [
    "lmstudio",
    "lmstudio-plugin",
    "email",
    "imap",
    "smtp",
    "inbox",
    "privacy",
    "tool-use"
  ]
}

Omit revision before the first push. lms push --write-revision writes the server-assigned revision afterward.

2. Regenerate dependencies and verify

Expected baseline after applying this release kit:

Existing account and pagination tests pass.
New date, search-result, and account-regression tests pass.
TypeScript emits no test files into root __tests__.
A second npm test after build remains clean.

Run network integration tests separately:

A failure caused solely by Ethereal/network availability is not equivalent to a unit-test failure, but SMTP code changes should still receive a successful integration run before release.

3. Manual LM Studio acceptance test

Run:

With a test mailbox or non-critical account:

Test at least one smaller tool-calling model in addition to the strongest model. The safety gates must not depend on model quality.

4. Inspect publication contents

Confirm:

No credentials or private email data are present.
node_modules is not committed.
Root JavaScript build output exists before lms push.

5. Commit the release

6. Publish

Review the confirmation instead of adding -y on the first public push.

7. Post-publication verification

Install the public artifact into LM Studio as a normal user would. Confirm that the generated JavaScript files load, settings render, the README is accurate, and the Hub displays the intended owner/name/provenance.

Create a clean clone/install test before announcing the release.

1. Establish fork identity

Prefer using the Fork action on the upstream LM Studio Hub page so the Hub can display provenance. Use a unique, descriptive kebab-case name such as:

email-imap-smtp

Do not publish under altra/email, and do not leave the local development name as email-fixed.

Set manifest.json:

{
  "type": "plugin",
  "runner": "node",
  "owner": "YOUR_LM_STUDIO_USERNAME_OR_ORG",
  "name": "email-imap-smtp",
  "tags": [
    "lmstudio",
    "lmstudio-plugin",
    "email",
    "imap",
    "smtp",
    "inbox",
    "privacy",
    "tool-use"
  ]
}

Omit revision before the first push. lms push --write-revision writes the server-assigned revision afterward.

2. Regenerate dependencies and verify

Expected baseline after applying this release kit:

Existing account and pagination tests pass.

New date, search-result, and account-regression tests pass.

TypeScript emits no test files into root __tests__.

A second npm test after build remains clean.

Run network integration tests separately:

A failure caused solely by Ethereal/network availability is not equivalent to a unit-test failure, but SMTP code changes should still receive a successful integration run before release.