deprecate m3o

[andreaselia]

Description

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used in the README are located outside the metadata folder if they were not generated with our metadata tool

[raycastbot]

Thank you for the update! 🎉

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 15 business days.

[greptile-apps]

Confidence Score: 4/5

[Medium impact] Replaces two extension commands with deprecation notices.

Remove the obsolete credential requirement and fix the required changelog format before merging.

Findings

1.  Notice requires an API key ▶
2.  Release date is fixed ▶

Fix with agent prompt

### Issue 1
extensions/m3o/src/avatar.tsx:5-9
Both commands now show only a deprecation notice, but `package.json` still requires `apiKey`. Raycast asks users without a saved key to enter one before either command opens, hiding the uninstall guidance behind unnecessary M3O setup. Remove the unused preference so both notices open without credentials.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

### Issue 2
extensions/m3o/CHANGELOG.md:3
The new changelog heading uses `2026-10-12`, but repository rules require `{PR_MERGE_DATE}` for new entries. Replace the fixed date with the placeholder before merging so publication records the actual merge date.

```suggestion
## [Deprecated] - {PR_MERGE_DATE}
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Replaces M3O's avatar and DNS commands with deprecation notices and uninstall guidance.

• The Avatar and DNS commands now show the M3O removal notice.

_{Reviews (1) · Last reviewed commit: "deprecate m3o" · Reviewed by Greptile}

[greptile-apps]

Notice requires an API key

Both commands now show only a deprecation notice, but package.json still requires apiKey. Raycast asks users without a saved key to enter one before either command opens, hiding the uninstall guidance behind unnecessary M3O setup. Remove the unused preference so both notices open without credentials.

Knowledge Base Used: Extension catalog and package model

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/m3o/src/avatar.tsx
Line: 5-9

Comment:
**Notice requires an API key**

Both commands now show only a deprecation notice, but `package.json` still requires `apiKey`. Raycast asks users without a saved key to enter one before either command opens, hiding the uninstall guidance behind unnecessary M3O setup. Remove the unused preference so both notices open without credentials.

**Knowledge Base Used:** [Extension catalog and package model](https://app.greptile.com/raycast/-/custom-context/knowledge-base/raycast/extensions/-/docs/extension-catalog.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Release date is fixed

The new changelog heading uses 2026-10-12, but repository rules require {PR_MERGE_DATE} for new entries. Replace the fixed date with the placeholder before merging so publication records the actual merge date.

Suggested change

	## [Deprecated] - 2026-10-12
	## [Deprecated] - {PR_MERGE_DATE}

Rule Used: What: Changelog entries must use {PR_MERGE_DATE} placeholder in titles, be placed at the top of the file, and maintain descending version order. Why: Standardized placeholders and consistent ordering ensure changelogs are maintainable and merge da... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/m3o/CHANGELOG.md
Line: 3

Comment:
**Release date is fixed**

The new changelog heading uses `2026-10-12`, but repository rules require `{PR_MERGE_DATE}` for new entries. Replace the fixed date with the placeholder before merging so publication records the actual merge date.

```suggestion
## [Deprecated] - {PR_MERGE_DATE}
```

**Rule Used:** What: Changelog entries must use `{PR_MERGE_DATE}` placeholder in titles, be placed at the top of the file, and maintain descending version order.  Why: Standardized placeholders and consistent ordering ensure changelogs are maintainable and merge da... ([source](https://app.greptile.com/raycast/-/custom-context?memory=c2214c11-df56-490a-b1c0-09a385df481a))

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[github-actions]

Published to the Raycast Store:
https://raycast.com/andreaselia/m3o

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.