# Can Devin write release notes for a self-hosted app and post the upgrade warning to Mastodon?

> Source: https://tareno.co/agents/devin/mastodon
> Language: en
> Last reviewed: 2026-10-24
> Connect Devin to Tareno to turn finished sessions into release notes for a self-hosted app, with the upgrade warning stated first, as a Mastodon post you approve in Tareno.

## Connection facts

| Field | Value |
| --- | --- |
| Product surface | Devin Desktop (devin) |
| Available connection | Custom MCP connection |
| Connection evidence | documented |
| Methods | mcp |
| Authentication | oauth |
| Setup | [Setup guide](https://tareno.co/docs/mcp) |
| Install or connect | [Open setup](https://tareno.co/docs/mcp) |
| Evidence observed | No dated observation recorded |
| Facts reviewed | 2026-10-27 |

Publication status and a working connection are separate facts. Evidence for one product surface does not establish installation or compatibility in another surface.

Agent: Devin Desktop · Network: Mastodon · Hub: [Devin Desktop and Tareno](https://tareno.co/agents/devin)

## Short answer

**Can Devin summarize a self-hosted app's release and post the upgrade warning on Mastodon?**

Yes, once Tareno is connected as an MCP server. Devin summarizes the finished sessions behind a release, finds changes that need action from administrators, puts the upgrade warning first and saves the post within your server's limit through Tareno. No client test with Devin has been completed, and approval happens in Tareno.

The people who run self-hosted software are the audience that cares most about upgrade warnings and least about feature lists. A release note that opens with what is new and buries the migration is a recipe for broken installations. Mastodon is where many self-hosters and small-server admins are, and a release post there is read by exactly the people who have to act. Devin keeps a record of the sessions that produced a release, so it can find the changes that need administrator action, such as a database migration or a changed environment variable. This page follows the maintainer of a self-hosted photo-library app, with the setup Cognition documents and the rule that the warning comes first.

## Example: a self-hosted photo app announces a release that needs a migration

Imagine a maintainer whose latest release changes the database schema and renames one environment variable. She asks Devin to list the sessions behind the release and to find changes that need administrator action. Devin finds both, and a third: a new minimum version of the database. It drafts a Mastodon post of 430 characters that opens with the three actions, then the headline feature, and links the upgrade guide. It saves the post with `create_drafts` for the project's account after confirming it with `list_accounts`, and she tests the upgrade steps herself before requesting a slot.

## Step by step

1. **Register Tareno.** Use the MCP marketplace within Devin or its command line; both end in an OAuth sign-in. Cognition prefers the streamable HTTP transport.
2. **Decide who signs in.** Cognition lets a connection belong to the organization or to one person. The project's Mastodon account has one owner, so that person authorizes it.
3. **Test before drafting.** Ask Devin to call `list_accounts` first. If your Mastodon account is returned, continue; if not, connect it inside Tareno.
4. **List the sessions behind the release.** Ask Devin for the finished sessions in the release and which of them changed schemas, configuration or minimum versions. These are the changes administrators must act on.
5. **Open with the warning.** Request a post that starts with the actions an administrator must take and the order, then the headline feature. Count against your server's limit, because Mastodon sets limits per server.
6. **Save, test the steps and approve.** Devin saves the post through `create_drafts`. Test the upgrade steps yourself on a copy, then give a day, a time and an IANA time zone and approve the request in the Tareno dashboard.

## Prompts to copy

### Find the actions

```text
List the sessions that went into release 4.2 and, for each, say whether it changed a database schema, a configuration key, an environment variable or a minimum dependency version. For every such change give the exact text an administrator would need to act, and the order of the steps.
```

### Write the warning first

```text
Write a Mastodon release post for Tareno of up to 450 characters that opens with the three actions an administrator must take before upgrading, in order, then states the headline feature, and links the upgrade guide [URL]. Avoid marketing adjectives, and use one hashtag in capitalized words.
```

### Check the steps

```text
Compare the steps in the draft with the upgrade guide and the migration files, and list any difference in names, order or version numbers. If a step in the post is not in the guide, say so, and do not save anything to Tareno until I have tested the steps.
```

### Save the draft

```text
Use Tareno to confirm the Mastodon account [project handle@server] and save the approved text as a draft. Return the draft ID and the text, and do not request a time until I give you the day and the time zone.
```

## Mastodon in Tareno

- Mastodon's documentation says character limits are set per server, with 500 characters as the example, so an upgrade warning with three steps needs a careful count.
- Tareno's configuration for Mastodon gives links an automatic preview, so the upgrade guide link shows its title, and administrators can see where it leads.
- Mastodon's documentation says a scheduled post must be at least 5 minutes ahead, which allows a release post to be queued shortly after the tag is public.
- Tareno does not read posts or replies on Mastodon, so administrators' upgrade questions arrive in the app and are answered there.

Official rules ([Mastodon documentation: statuses and instance configuration](https://docs.joinmastodon.org/methods/statuses/), checked 2026-10-24):

- Character and media limits are set by each server, not by Mastodon itself. The documentation's example server allows 500 characters and 4 attachments, and counts every link as 23 characters.
- A scheduled status must lie at least 5 minutes in the future, and a poll cannot be combined with media attachments.
- Visibility can be public, unlisted, private (followers only) or direct, and a content warning can be set with spoiler text.

## Mistakes to avoid

- Opening with the new feature. Administrators need the warning first.
- Posting steps you have not tested. Run them on a copy.
- Letting the whole organization use one authorization. Tie it to the account owner.
- Forgetting the minimum dependency version. It breaks installations quietly.

## What does not work

- Devin cannot test the upgrade on your users' systems, so the maintainer tests the steps on a copy before approval.
- It cannot read replies on Mastodon through Tareno, because Tareno does not expose posts or replies for Mastodon.
- It cannot send a post to Mastodon itself; every request stops at the approval step in the dashboard.

## Frequently asked questions

### Which Devin features does this workflow rely on?

Only its record of finished sessions and a remote MCP connection. Cognition documents the connection route, while Tareno has no completed client test with Devin, so verify with a read.

### Why open with the upgrade warning?

Because the readers are the people who must act. Administrators scan for what they have to do before they upgrade, and a post that leads with features hides the step that decides whether the upgrade succeeds.

### Who should authorize the Mastodon account?

Its owner. An organization-wide link would let any Devin user draft for the project's account, while a personal one keeps the drafts tied to a person. Approval stays in Tareno in both cases.

### How does Devin know what needs administrator action?

From the sessions behind the release: schema changes, configuration keys, environment variables and version requirements. It lists them with the files involved, and you confirm that the list is complete.

### How do I fit three steps into the limit?

Write each step as a short imperative and link the guide for detail. Mastodon limits are per server, so give Devin your figure and ask for a count that treats each link as your server does.

### Could the release post appear unreviewed?

No. The request waits in Tareno as pending, and Mastodon is contacted only after you approve it in the dashboard. Devin can report that it is waiting and nothing more.

## Tareno tools used

- `list_accounts`
- `create_drafts`

Approval model: Tareno saves drafts directly. Scheduling, publishing, edits to scheduled posts and deletions become pending actions that a person approves in the Tareno dashboard; no agent can approve them.

## Related

- [Devin × Tareno overview](https://tareno.co/agents/devin)
- [Post scheduling](https://tareno.co/features/post-scheduling)
- [Approval workflows](https://tareno.co/features/approval-workflows)
- [Content boards](https://tareno.co/features/content-boards)
- [Remote MCP setup](https://tareno.co/docs/mcp)