If you are not sure if the website you would like to visit is secure, you can verify it here. Enter the website address of the page and see parts of its content and the thumbnail images on this site. None (if any) dangerous scripts on the referenced page will be executed. Additionally, if the selected site contains subpages, you can verify it (review) in batches containing 5 pages.
favicon.ico: docs.joinmastodon.org/admin/upgrading - Upgrading to a new release - M.

site address: docs.joinmastodon.org/admin/upgrading redirected to: docs.joinmastodon.org/admin/upgrading

site title: Upgrading to a new release - Mastodon documentation

Our opinion (on Wednesday 08 July 2026 19:16:37 UTC):

GREEN status (no comments) - no comments
After content analysis of this website we propose the following hashtags:



Meta tags:

Headings (most frequently used words):

upgrading, to, new, release, sponsored, by, versioning, automatic, update, verification, upgrade, steps,

Text of the page (most frequently used words):
the (36), mastodon (25), your (14), you (13), admin (13), and (12), #release (12), #version (11), api (10), that (9), will (8), new (7), server (7), restart (7), instructions (7), releases (7), can (6), with (6), this (5), page (5), from (5), make (5), upgrade (5), setting (5), instance (5), changes (5), also (4), running (4), all (4), streaming (4), not (4), for (4), upgrading (4), environment (4), update (4), profile (4), account (4), oauth (4), using (4), systemctl (3), users (3), about (3), reload (3), have (3), notes (3), every (3), need (3), minor (3), everything (3), github (3), different (3), git (3), tags (3), code (3), updates (3), security (3), check (3), versions (3), may (3), versioning (3), search (3), preferences (3), apps (3), reports (3), accounts (3), source (2), updated (2), available (2), now (2), load (2), disconnected (2), clients (2), poll (2), rest (2), instead (2), doing (2), which (2), operation (2), downtime (2), called (2), require (2), any (2), there (2), web (2), background (2), after (2), switch (2), root (2), single (2), patch (2), when (2), deploy (2), least (2), one (2), most (2), collection (2), sure (2), execute (2), are (2), directory (2), what (2), steps (2), variable (2), string (2), way (2), https (2), joinmastodon (2), org (2), beta2 (2), current_version (2), automatic (2), verification (2), best (2), compatible (2), add (2), backwards (2), application (2), notificationpolicy (2), filter (2), report (2), quote (2), domainblock (2), notifications (2), trends (2), collections (2), domain_blocks (2), tokens (2), implementing (2), posts (2), machine (2), installing (2), features (2), configuring (2), imprint, view, blog, join, sponsored, last, february, 2026, 简体中文, improve, restarting, leads, increased, attempt, reconnect, avoid, whenever, requires, result, connected, being, increase, zero, phased, such, upgrades, usually, advance, notice, planned, rare, cases, use, but, short, felt, interruption, service, process, sidekiq, workers, exit, executed, back, safely, skip, deploying, level, see, above, old, individually, them, however, should, series, importantly, keep, track, each, overlap, just, once, included, because, include, checkout, fetch, download, assuming, home, live, navigate, begin, user, correspond, before, attempting, look, desired, contain, describing, know, well, specific, changelog, change, url, queries, completely, disable, behavior, empty, although, strongly, recommend, against, unless, keeping, another, occasionally, critical, must, applied, timely, fashion, update_check_url, happens, fetching, minutes, omits, build, metadata, first, query, fork, since, automatically, notify, permission, devops, accompanying, changelogs, reading, those, given, backward, bug, fixes, small, enhancements, functionality, ways, dependency, etc, major, incompatible, aka, breaking, how, works, responds, substantial, underlying, system, requirements, generally, speaking, done, spirit, semver, released, appears, please, note, unreleased, branch, while, possible, recommended, main, webpushsubscription, translation, token, termsofservice, tag, suggestion, statussource, statusedit, status, shallowtag, shallowquote, scheduledstatus, rule, role, relationshipseveranceevent, relationship, reaction, quoteapproval, privacypolicy, previewcardauthor, previewcard, notificationrequest, notificationfallback, notification, mediaattachment, marker, list, identityproof, filterstatus, filterresult, filterkeyword, featuredtag, featureapproval, familiarfollowers, extendeddescription, error, customemoji, conversation, context, collectionwithaccounts, collectionitem, asyncrefresh, appeal, annualreport, announcement, measure, ipblock, emaildomainblock, domainallow, dimension, cohort, canonicalemailblock, accountwarning, entities, markers, lists, conversations, timelines, scheduled_statuses, polls, media, statuses, proofs, oembed, push, custom_emojis, announcements, health, grouped, async_refreshes, emails, annual, retention, measures, ip_blocks, email_domain_blocks, domain_allows, dimensions, canonical_email_blocks, suggestions, mutes, followed_tags, follow_requests, filters, featured_tags, favourites, endorsements, bookmarks, blocks, methods, rate, limits, scopes, guidelines, practices, datetime, formats, bearcaps, microformats, webfinger, activitypub, spec, compliance, design, reference, creating, themes, css, styling, state, management, components, frontend, guide, issues, responsible, disclosure, routes, structure, dev, technical, overview, contributing, libraries, implementations, logging, obtaining, client, app, access, playing, public, data, getting, started, developing, roles, webhooks, database, index, corruption, troubleshooting, errors, moderation, actions, scaling, migrating, backing, cli, sign, captcha, onion, services, object, storage, optional, full, text, preparing, own, official, ios, android, moving, leaving, externally, more, settings, set, promoting, yourself, others, dealing, unwanted, content, quoting, other, network, posting, signing, documentation,


Text of the page (random words):
upgrading to a new release mastodon documentation what is mastodon using mastodon signing up for an account setting up your profile posting to your profile using the network features quoting other posts dealing with unwanted content promoting yourself and others set your preferences more settings using mastodon externally moving or leaving accounts official ios and android apps running your own server running mastodon preparing your machine installing from source configuring your environment configuring full text search installing optional features object storage onion services captcha single sign on setting up your new instance using the admin cli upgrading to a new release backing up your server migrating to a new machine scaling up your server moderation actions troubleshooting errors database index corruption webhooks roles developing mastodon apps getting started with the api playing with public data obtaining client app access logging in with an account libraries and implementations implementing quote posts implementing collections contributing to mastodon technical overview setting up a dev environment code structure routes security issues and responsible disclosure frontend guide components state management css and styling creating themes design tokens reference spec compliance activitypub webfinger security microformats oauth bearcaps rest api datetime formats guidelines and best practices oauth tokens oauth scopes rate limits api methods accounts blocks bookmarks domain_blocks endorsements favourites featured_tags filters follow_requests followed_tags mutes preferences reports suggestions tags admin accounts canonical_email_blocks dimensions domain_allows domain_blocks email_domain_blocks ip_blocks measures reports retention trends annual reports apps emails oauth async_refreshes collections grouped notifications health instance announcements custom_emojis directory trends notifications push oembed profile proofs search statuses media polls scheduled_statuses timelines conversations lists markers streaming api entities account accountwarning admin account admin canonicalemailblock admin cohort admin dimension admin domainallow admin domainblock admin emaildomainblock admin ip admin ipblock admin measure admin report announcement annualreport appeal application asyncrefresh collection collectionitem collectionwithaccounts context conversation customemoji domainblock error extendeddescription familiarfollowers featureapproval featuredtag filter filterkeyword filterresult filterstatus identityproof instance list marker mediaattachment notification notificationfallback notificationpolicy notificationrequest poll preferences previewcard previewcardauthor privacypolicy profile quote quoteapproval reaction relationship relationshipseveranceevent report role rule scheduledstatus search shallowquote shallowtag status statusedit statussource suggestion tag termsofservice token translation v1 filter v1 instance v1 notificationpolicy webpushsubscription upgrading to a new release versioning automatic update verification upgrade steps when a new version of mastodon is released it appears on the github releases page please note that running unreleased code from the main branch while possible is not recommended versioning generally speaking mastodon versioning is done in the spirit of semver that is major versions 4 x to 5 x may make backwards incompatible changes aka breaking changes to how the application works or the api responds or may make substantial changes to underlying system requirements minor versions 4 1 x to 4 2 x will add functionality in backwards compatible ways may make minor dependency changes etc patch versions 4 2 1 to 4 2 2 will make backward compatible bug fixes or add small enhancements all releases will have accompanying release notes and changelogs and reading those is the best way to be sure about the changes in a given release automatic update verification since v4 2 0 mastodon will automatically check for available updates and notify the users of your server that have the devops permission this happens by fetching https api joinmastodon org update check version current_version in the background every 30 minutes current_version omits the build metadata everything after the first if there is one in the version string for instance if your version is 4 3 0 beta2 my fork mastodon will query https api joinmastodon org update check version 4 3 0 beta2 you can change which url mastodon queries by setting the update_check_url environment variable you can also completely disable this behavior by setting this environment variable to an empty string although we strongly recommend against doing that unless you are keeping up with mastodon updates in another way as mastodon occasionally releases critical security updates that must be applied in a timely fashion upgrade steps mastodon releases correspond to git tags before attempting an upgrade look up the desired release on the github releases page the page will contain a changelog describing everything you need to know about what s different as well as specific upgrade instructions to begin switch to the mastodon user su mastodon and navigate to the mastodon root directory cd home mastodon live download the release s code assuming that the version is called v3 1 2 git fetch tags git checkout v3 1 2 now execute the upgrade instructions that are included in that version s release notes on github because different releases require different instructions we do not include any instructions on this page you can safely skip deploying every single patch level see above version release when upgrading from an old version you do not need to individually deploy them all however you should deploy at least one release from every minor version series most importantly keep track of the instructions with each release or collection of releases most instructions overlap you just need to make sure you execute everything at least once after you have executed the instructions from the release notes switch back to root exit restart background workers systemctl restart mastodon sidekiq and reload the web process systemctl reload mastodon web the reload operation is a zero downtime restart also called phased restart as such mastodon upgrades usually do not require any advance notice to users about planned downtime in rare cases you can use the restart operation instead but there will be a short felt interruption of service for your users the streaming api server is also updated and requires a restart doing so will result in all connected clients being disconnected which can increase the load on your server systemctl restart mastodon streaming restarting the streaming api leads to an increased load on your server as disconnected clients attempt to reconnect or poll the rest api instead so avoid it whenever you can that s all you re running the new version of mastodon now last updated february 20 2026 improve this page also available in 简体中文 sponsored by join mastodon blog view source cc by sa 4 0 imprint
Images from subpage: "docs.joinmastodon.org/entities/CustomEmoji/" Verify
Images from subpage: "docs.joinmastodon.org/entities/DomainBlock/" Verify
Images from subpage: "docs.joinmastodon.org/entities/Error/" Verify
Images from subpage: "docs.joinmastodon.org/entities/ExtendedDescription/" Verify
Images from subpage: "docs.joinmastodon.org/entities/FamiliarFollowers/" Verify

Verified site has: 191 subpage(s). Do you want to verify them? Verify pages:

1-5 6-10 11-15 16-20 21-25 26-30 31-35 36-40 41-45 46-50
51-55 56-60 61-65 66-70 71-75 76-80 81-85 86-90 91-95 96-100
101-105 106-110 111-115 116-120 121-125 126-130 131-135 136-140 141-145 146-150
151-155 156-160 161-165 166-170 171-175 176-180 181-185 186-190 191-191


The site also has references to the 2 subdomain(s)

  joinmastodon.org  Verify   blog.joinmastodon.org  Verify


Top 50 hastags from of all verified websites.

Supplementary Information (add-on for SEO geeks)*- See more on header.verify-www.com

Header

HTTP/2 301
server GitHub.com
content-type text/html
location htt????/docs.joinmastodon.org/admin/upgrading/
access-control-allow-origin *
strict-transport-security max-age=31556952
expires Wed, 08 Jul 2026 19:26:37 GMT
cache-control max-age=600
x-proxy-cache MISS
x-github-request-id E1D4:31B2A6:6E2330:6F148D:6A4EA215
accept-ranges bytes
age 0
date Wed, 08 Jul 2026 19:16:37 GMT
via 1.1 varnish
x-served-by cache-rtm-ehrd2290054-RTM
x-cache MISS
x-cache-hits 0
x-timer S1783538197.147619,VS0,VE106
vary Accept-Encoding
x-fastly-request-id cdabe294c17364920994f1537dd4d257add5ea97
content-length 162
HTTP/2 200
server GitHub.com
content-type text/html; charset=utf-8
last-modified Wed, 08 Jul 2026 12:39:28 GMT
access-control-allow-origin *
strict-transport-security max-age=31556952
etag W/ 6a4e4500-6553
expires Wed, 08 Jul 2026 19:26:37 GMT
cache-control max-age=600
content-encoding gzip
x-proxy-cache MISS
x-github-request-id 7106:31B2A6:6E2359:6F14BC:6A4EA214
accept-ranges bytes
date Wed, 08 Jul 2026 19:16:37 GMT
via 1.1 varnish
age 0
x-served-by cache-rtm-ehrd2290054-RTM
x-cache MISS
x-cache-hits 0
x-timer S1783538197.266485,VS0,VE380
vary Accept-Encoding
x-fastly-request-id 45194c8e7b36ad1a13d8c69b6b62d15543c5f16e
content-length 7028

Meta Tags

title="Upgrading to a new release - Mastodon documentation"
charset="utf-8"
name="viewport" content="width=device-width,initial-scale=1"
property="og:type" content="article"
property="og:url" content="htt????/docs.joinmastodon.org/admin/upgrading/"
name="twitter:site" content="@joinmastodon"

Load Info

page size7028
load time (s)0.60709
redirect count1
speed download11578
server IP 185.199.108.153
* all occurrences of the string "http://" have been changed to "htt???/"