Sharing release summaries

Sometimes you want to send a teammate (or someone without a DevUpdate.io account) the analysis of one specific release. Share links do exactly that: they make a single release summary publicly viewable without exposing the rest of your dashboard.

Creating a share link #

1. Open any source in your dashboard and find the release you want to share.
2. On that release's card, click Share.
3. Decide whether the page should name the repository (see below), then click Create link.
4. The dialog shows the public link. Click Copy and send it to anyone.

The link opens a public page with the full summary (breaking changes, security updates, risk score, ecosystem news, and migration notes) exactly as you see it, plus a prompt for the viewer to sign up.

Clicking Share again on the same card, before you reload the page, shows the same link rather than making a new one.

Naming the repository #

The dialog has one option, Show the repository name, and it starts off.

• Off (the default): the page shows the release summary and does not say which repository it is from. It carries no owner/repo and no link to the repository's page on Explore.
• On: the page also shows owner/repo, and links to the repository on Explore if it is public. A private repository is never listed on Explore, so its link goes to Explore's front page instead.

It starts off because a private repository's name is often the part you would not want to pass on: it can name a client, or a product nobody has announced. We cannot always tell a private repository from a public one when you share, so we leave the name out unless you add it. For a public repository, turning it on gives the reader more context.

The option covers the repository name only. The summary is written from the release notes, so if those mention the project by name, the summary can too. Read it before you send a link for a private repository.

A link keeps the choice it was made with.

What the link reveals #

A share link exposes only that one release summary, plus the repository name if you chose to show it. It does not reveal the source's other releases, your watched sources, or any of your account details. Viewers who want a source's full history or ongoing updates are prompted to create their own account.

Expiry and revocation #

• Every share link expires automatically 7 days after you create it.
• You can revoke a link sooner at any time from Settings → Share links. Once revoked or expired, the public page stops working.

Your share links in Settings #

Settings → Share links lists every link of yours that is still active, newest first. Each row shows the repository and release it shares, when you created it, when it expires, and whether its public page names the repository. The list always shows you the repository name, so you can tell your links apart; whether the public page shows it is the choice you made when you created the link.

Click Revoke, then Confirm Revoke, and the link stops working at once: anyone who opens it afterwards gets a "not found" page. Revoking can't be undone, but you can share the same release again with a new link. Expired links drop off the list by themselves.

The share dialog links to this list, both before and after you create a link.

• The link uses an unguessable random token and is not indexed by search engines.

Limits #

Free (Hobbyist) accounts can have up to 5 active share links at once. Once you hit the limit, revoke an existing link in Settings → Share links or let one expire to free a slot. The share dialog says so when it refuses a new link. Professional and Team plans have no limit on active share links.