Skip to content

Release a revision

Releasing stamps the next revision letter (Rev A, B, C…) on a source file's current checked-in version. This page covers a file's first release (Rev A), which is a direct action from the file row. Every later release runs through an ECO's Release all — see Work with ECOs. For the concepts, see Understand revisions and ECOs.

Prerequisites

  • The file is a source file (part, assembly, or drawing).
  • The file is checked in and on the latest version — clean, pushed, not checked out, with no pending local versions.
  • You are a releaser (named in Settings → Release Control) or a repository Admin/Owner.
  • The file has no prior release and is not under an active ECO. (Once a file has a Rev, or is named on an open ECO, it releases through the ECO's Release all instead.)

Steps

  1. In the Files tab, right-click the file (or open its ⋯ menu).
  2. Choose Release….
  3. If the item is disabled, hover it — the tooltip says why (for example, Check in first, Requires an approved ECO, or Checked out — release after check-in).
  4. GitM records the release and the file's Rev badge updates.

Expected result

  • The file shows a green Rev A badge.
  • The release is recorded in .gitm/revisions.json and pushed, so teammates and GitMCloud see it on their next refresh.
  • Later revisions of this file are released through an ECO's Release all, which stamps every affected file together and closes the ECO — see Work with ECOs.

When can't I release?

The Release item shows… Why What to do
Check in first The file has unsaved or unpublished changes, or isn't on the latest version. Check in first.
Checked out — release after check-in The file (or a teammate) holds the lock. Check it in (which releases the lock), then release.
Release via ECO-nnn The file is named on an active ECO. Release it from the ECO's Release all — see Work with ECOs.
Requires an approved ECO It's past the free first release and isn't on an active ECO. Open an ECO for it.
Releasing requires release permission You're not a releaser and not an Admin/Owner. Ask an admin to add you in Settings → Release Control.
(no Release item) The file isn't a source file. Only parts/assemblies/drawings carry revisions.

Notes

  • Releasing is metadata only — it does not change the file's geometry. It marks an existing, published version as an official revision.
  • The amber Rev B +2 badge means the part is released at Rev B but has 2 newer versions that haven't been released — a cue that the released drawing may be behind the model.