Releases

Marketing version 1.14.1, build 26.

• Adding a webhook with a secret, or importing a repository with a token, no longer makes iOS offer to save the secret as a password.

Marketing version 1.14.0, build 25.

Repository settings

• Build secrets: the names a repository's builds read, set or replaced with a value that is sent once and never shown, on one line or several (for a private key), and removed.
• Deploy keys: keys bound to the repository alone, read-only or read-write, with an optional lifetime, when each was last used and when it expires.
• Mirrors: push and pull mirrors with their username, whether a sync is pending, when one last ran and its error; add one with a token, remove one, or sync them all now.
• Custom domains: pages domain claims, pending, verified or expired. A claim shows the DNS TXT record to create, with copy buttons, and verifies there or later from the list.

Account

• Browser Sessions, in the account menu: the browsers signed in to the web as you. Sign one out, or all of them. The app stays signed in.

Organizations and administration

• Delete organization, at the end of an organization's screen, once its name is typed. An organization that still owns repositories is refused, and the alert says why.
• On a merged or closed merge request, an instance admin can prune its head: its head ref and the commits only it kept go, after a confirmation, and the thread records it.

Marketing version 1.13.1, build 24.

• Math in an org heading, table cell or footnote is set at the size of the text around it, not at body size. Uses krz/org-swift 0.9.0.

Marketing version 1.13.0, build 23.

TeX math

• Issue, merge request and release bodies, comments and READMEs typeset TeX math, as the web renders it as MathML. Markdown takes $…$ and $$…$$, inline or as a block; org takes $…$, $$…$$, \(…\), \[…\] and \begin{…}…\end{…}. Prices such as "$5 and $10" stay prose, by the web's rules.
• Math is tinted like the text around it, follows Dynamic Type, and VoiceOver reads its TeX. A display expression wider than the screen scrolls sideways.
• An expression the app cannot typeset shows its source, as the web does with one its converter refuses.

Typesetting is SwiftMath (MIT); org parsing is krz/org-swift 0.8.0.

Marketing version 1.12.0, build 22.

Instance administration, for accounts that are instance admins.

Accounts

• An account's row opens what the server knows of it: keys, addresses, organizations, tokens and sessions, and its repository, storage and organization limits against what it holds. Edit limits changes them, default restoring the instance's.
• Delete account removes one that anchors nothing, after its username is typed.
• The + button creates an account, with an address, admin and an SSH key, or invites someone by email. Where the instance cannot mail, the invite code is shown to pass on.

The instance

• Statistics: counts, and disk use by repository.
• Audit log: the latest 200 events, narrowed by actor, action and age.
• Runners: the build queue and each key polling for builds, with what it may claim and the build it holds. A row can be removed.
• Inbound mail: whether the reply mailbox answers, and what waits in it.

Repositories and organizations

• Repositories lists every repository with its size and last push, filtered by owner and visibility. Archive, visibility and a symbol index rebuild are a menu away, each confirmed where it changes what others see; delete asks for the path.
• Organization limits shows and sets an organization's caps.

Marketing version 1.11.0, build 21.

API tokens

• API Tokens, in the account menu, lists each token with its scope, when it was last used, when it expires and the token that minted it.
• The + button mints one, read or full and with an optional lifetime, and shows it once with a copy button. The copy stays on this device and leaves the clipboard after two minutes.
• Revoking asks whether to take the tokens and keys it created too, and says what it created either way.

Keys

• Each SSH key says when it was last used, when it expires or that it has, and what added it. A new key can expire in 30 days, 90 days or a year.

Notifications

• Reply by mail, where the instance reads replies to its mail: answering issue and merge request mail posts your reply as a comment. Needs gitbay's reply_available (krz/gitbay#334) to hide the switch where replies are not read; an older server shows it and explains a refusal.
• A switch the server refuses goes back instead of showing the refused value.

Deleting your account

• Delete account, at the end of the Account screen, mails a link after you type your username. Opening it disables the account; seven days later it is deleted. The screen remembers the request for the link's day and offers to withdraw it.

Marketing version 1.10.0, build 20.

Saved queries

• Saved Queries, from the button at the top left of the Dashboard, lists your issue and merge request queries across repositories. One opens its results; swipe to pin it to the Dashboard or remove it, and hold it to edit. The + button saves a new one.
• Pinned queries show on the Dashboard with their first rows and how many they match, as on the web.
• A query the server cannot parse says why, rather than "Something went wrong". The same goes for a required check's name in settings.

Repository settings

• Transfer repository moves it to another account or an organization, and Delete repository deletes it, each after you type its path. The repository screen and the Dashboard follow, and a refusal is shown where you are.

Marketing version 1.9.0, build 19.

Releases

• The new-release sheet has Summarize changes: it adds a line for each merge request landed since the previous release, after what you have typed. Needs gitbay v1.44.0.

Builds

• Last 200 lines shows only the end of a log, and keeps polling that much of a running build instead of the whole log. Whole log brings the steps back.

Definitions

• Definitions, beside Search in Files, finds where a name is defined from the repository's symbol index, by name or its start, optionally narrowed by kind. A result opens the file at that line with the line marked; a Search in Files match now does the same.
• In a file, names the index defines are underlined with dots and keep their colour. A name defined once opens its line; one defined more often opens Definitions with the search run. This needs gitbay's repo definitions (krz/gitbay#333); against a server without it, files look as before. Markdown, org and text files are not linked.

Marketing version 1.8.0, build 18.

Reactions

• Issues, merge requests and their comments show their reactions, with your own tinted. The face button offers all eight; picking one you gave takes it back.
• Lines the server posted, such as a retarget or a queued merge, take no reactions and offer none.

Review comments and suggested changes

• Tap a line of a merge request's diff to comment on it. On the new side you can suggest a change to that line or a range ending on it; the sheet fills a suggestion block with the lines' current text to edit, and moving the start of the range rebuilds it.
• A thread with a suggestion shows the lines it replaces and proposes. Apply commits it to the source branch. Where the repository requires signed commits, the thread gives the CLI command instead.

Merge when ready

• The actions menu offers Merge when ready with the same strategies as Merge. The gates section shows who queued it and why it has not merged yet, and Cancel queued merge takes it off.

Required checks

• Repository settings list the checks the checks gate waits on by name, under Require green checks. Naming one turns the gate on.

Marketing version 1.7.0, build 17.

Build logs

• The log is split into its steps, as on the web. A failed build opens with the failed step expanded and its reason on the step header.
• "Jump to failure" opens the failed step at its start; "Jump to end" goes to the last line. A search field filters log lines.
• A pending or running build refreshes every 3 seconds until it finishes.
• The header shows how long the build ran.

Repository page

• Files, merge requests, issues and builds in one strip, with open counts and the latest build's status.
• History, branches and tags, milestones, labels, releases, wiki and search in files sit under More, above the README.
• The owner is a link in the header; Settings moved to the actions menu.

Links

• gitbay.org links open in the app from Safari, Messages, Mail and other apps: owners, repositories, issues, merge requests, builds, files, commits, releases and the wiki. Other pages stay in the browser.
• #N, !N and owner/name#N link to the issue or merge request in markdown and org bodies, comments and review threads. Code and verbatim text are left alone.

Sign-in

The token hint links to the instance's Settings → API tokens page first, keeps the CLI command, and says what full scope allows.

Flow

• Creating an issue opens it.
• A merge request's gates and checks sit under its description.
• The Dashboard tab carries the unread notification count; push settings are below the inbox.
• Renaming a repository and removing an SSH key ask for the name or key to be typed first.
• Issue and merge request states are in sentence case throughout.
• iPad: Dashboard and Repositories use a sidebar and detail layout.

Accessibility

• Icon-only buttons carry labels, and chip remove buttons have a 44pt target.
• Issue and merge request rows stack at accessibility text sizes.
• A diff line reads as one element: "Added line 13: …".

Fixes

• Long build logs, files and snippets drew nothing. They now render line by line.
• An org body with a line such as "#12 fixed this" froze the app (org-swift 0.7.1).
• A markdown line starting with "#12" rendered as a heading.
• Opening a screen from the repository page could put the next screen underneath it, so Back revealed it.
• Lists with a segmented filter lost their rounded top corners.
• The notifications screen showed its empty message over the push settings, and registered devices looked like notifications.
• The send buttons for comments and replies are larger.
• Adding an SSH key or email address with an expiring token now says it needs a token without an expiry.

Marketing version 1.6.2, build 16. Covers 1.5.0 through 1.6.2, and is the first App Store upload since 1.2.0, so it also carries 1.4.0.

Markup preview

A collapsed Preview row under every markup editor: issue and merge request bodies, comments, new merge requests, release notes, and the file editor for .md, .markdown and .org files. It renders with the same view the threads use, in the format picked. #N stays plain text, as it does in threads.

Admin

For instance admins only, matching the web's /admin and /admin/users:

• Worker queues: webhook deliveries, mail, push, mirrors, builds and dependency checks, with counts and the retrying or failed rows.
• Accounts: filter by all, active, pending, disabled or admins; promote, demote, disable and enable. Demote and disable ask for the username.

Fixes

• Markdown list items keep their continuation lines. An item whose text wrapped onto a second source line broke there and rendered the rest as a paragraph; a single-line item could truncate with "…".
• The build row's branch and commit line stays on one line: the branch truncates in the middle and the short SHA is never split.
• Editors dismiss the keyboard on a downward drag, and expanding a preview dismisses it.

Marketing version 1.4.0, build 13. Covers 1.3.0 and 1.4.0. Neither build was uploaded to the App Store; 1.6.2 carries this work.

Push notifications

• Registers the device with every signed-in account.
• A tap opens the issue, merge request or build it is about.
• A switch and the registered device list on the notifications screen.
• The app badge clears when the inbox is read.

Profile about text

Saving a profile or organization profile failed in 1.2.0 against gitbay v1.31.0 and later, which moved the about text into a file (#14). The edit sheet now sets description, website and links only. The about text renders from profile/README.md or .org in <owner>/.gitbay, with Edit About to open the file, or Create About File to create the repository and a starter README on its default branch.

Builds

• Each row leads with the commit subject.
• The list pages thirty at a time, as the web does.

Merge requests

• Labels on the detail screen, added and removed as chips.
• Filter the list by label.

Also

The issue, merge request and build lists keep their loaded pages when you come back from a detail screen.

Marketing version 1.2.0, build 11. On the App Store since 2026-09-19.

New

• Snippets: list, show, create, edit and delete, with per-file set and remove. Reached from the account menu and from a user's profile.
• Organization labels and milestones, managed from the organization screen, which also gains an Issues section.
• SSH key labels: set a label when adding a key, or change it later.
• Build list filters: branch, status and job.
• Close a merge request in favour of another, picked from the open merge requests. A superseded merge request links to its replacement.

Marketing version 1.1.1, build 10. Covers 1.0.6 through 1.1.1.

Repositories

• Fork, watch, mute and bookmark a repository; stop watching or unmute; a bookmarks list.
• Compare two refs.
• Import a repository from a remote, and rename one.
• Settings: dependency checks, default branch, merge-requests-only, protected tags, require code owner review, access grants, and webhooks. The access section shows where each grant comes from.
• Labels: list, colour, and a management screen. Repository label and milestone lists mark the ones inherited from the organization.
• Milestones: create, close and reopen.
• Releases: delete a release, remove an asset. Builds: cancel.

Merge requests and issues

• Filter and search the issue and merge request lists.
• Draft, retarget, review requests and stacks.
• Revisions and range-diff.
• Merge gates, including advisory reviews.
• Issue templates in the compose sheet.
• Choose Markdown or Org for a body; edit opens on the format it was stored in.

Account and organizations

• Notification inbox.
• Search the instance from the Explore tab.
• Edit your profile and an organization's profile; create and rename an organization.
• Email addresses: list, remove, make primary. Activity mail switch and the default watch preference on the account screen.

Also

• Removing a team member, revoking a grant or removing a topic asks first.
• Deployment target is iOS 18.0.
• App Store category is developer tools.

Marketing version 1.0.5, build 6.

Markdown READMEs

A relative link is tappable. [ARCHITECTURE.md](ARCHITECTURE.md) in a .md README rendered styled as a link and did nothing; it now opens the file's page on the instance, the same destination the equivalent link in an Org README reaches.

Covers path, ./path, ../other-repo, and /absolute/path. Issue, merge request, and release bodies have no file to be relative to and are unchanged.

Also

OrgSwift 0.6.0. A link carrying a query string keeps its &.

Marketing version 1.0.4, build 5.

Org READMEs

Blocks inside list items render as blocks: a #+begin_src under a numbered step is a code block, not literal #+begin_src text in the running prose. Tables, quotes, and nested lists inside an item render the same way.

A README's opening badge row renders as badges at their own size rather than as a line of alt text, and instance badges point at the PNG the server serves rather than the SVG.

Markdown READMEs

Tables render, and inline code is set at the size the web uses.

Also

OrgSwift 0.5.0.

Marketing version 1.0.2, build 3.

Merge requests keep time

Reviews and checks show when they last said something, as a date and time rather than "3 days ago". A ci/<job> check also shows how long its build ran, so the timing of a run is readable without opening it; checks posted through status set have no build and show only the time. A merged or closed merge request shows who resolved it and when.

Parity with the server's krz/gitbay v1.2.0. Every field is optional, so the app renders as before against an instance that does not report them.

Also

A README for the repository.

Marketing version 1.0.1, build 2.

Org READMEs render natively

.org READMEs are drawn as SwiftUI views rather than HTML in a WKWebView. Text is selectable, type scales with Dynamic Type, and VoiceOver reads the content. Syntax highlighting in #+begin_src blocks follows the app's light/dark theme, and TODO/DONE keywords use the same colors the forge already gives open and merged things.

This also fixes rendering that was wrong before:

• Emphasis whose body contains a separator — =ssh.mode = "system"= — rendered as two verbatim spans with the value loose between them, because the parser closed at the first = instead of honoring org's rule that a body may not end with whitespace.
• Nested emphasis was flattened: *bold /italic/* rendered bold only.
• Repository-relative links in Org READMEs resolved to raw paths rather than URLs, and footnotes showed their label instead of a number.

Markdown READMEs are unchanged.

Profiles

• Repository rows carry topics, license, and last-commit information.
• Profiles show their About text and links.

Under the hood

org-swift moves to 0.3.0, which adds the OrgSwiftUI product this release renders through.

First App Store submission, sent for review 2026-08-28.

A native iOS client for gitbay. The tag marks the tree that was submitted; anything after it belongs to a later release.

What's in it

• Dashboard — review queue, work assigned to you, open MRs and issues, pinned repositories, recent activity.
• Repositories — file tree and blob view with syntax highlighting, history at a ref and per file, blame, branches and tags, and file editing on a branch.
• Merge requests and issues — lists, detail, comments, milestones, and a unified diff view.
• Builds — build list, job picker, and a detail screen with logs.
• Releases and wiki, read from the same instance.
• Explore, feed, and profiles — repository discovery, activity, and a contribution graph.
• READMEs in Markdown and Org, with repository-relative links and images resolved against the instance.

Auth is a bearer token minted over SSH; the app never asks for a password.